Just re-checked the time and the bug is still there. When you do a "Sync browser time" it's correct (or at least almost correct, see above) but at some point it appears to have done an NTP sync and it's now 13 hours behind the actual time. Given that we're at GMT+13 it looks like it's ignoring the time zone and using straight UTC without the local time zone offset for the time.
So it looks like there are still time-handling bugs in the v3 firmware, just different to the ones in the v2 firmware.
So it looks like there are still time-handling bugs in the v3 firmware, just different to the ones in the v2 firmware.