In «Details» it is stated that this is fixed. After upgrading to v1.4.2.22 (2019-04-02, 16:43:16), the problem is still present.
It seems that the timestamp is equal to last startup time of RV320. See attached screenshot. Startup time = 10:00:10. Login time (at top) was 10:31, same as current time.
Latest version where I did not experience this problem was v1.3.2.02 (2016-09-23, 15:17:06).
