@Mickkie - I have a Mutant HD51 also and have had ongoing time issues since the implementation of the "fake" HWclock coding back in December last year. Prior to that, I had been using my local NTP server for time setting without an issue. I don't use my Mutant much for timer recording (it's located in a bedroom), but I do have it set to wake from deep standby every afternoon at 5pm to run Autoboquetsmaker and CrossEPG and then shut down again. The time setting changes caused all sorts of issues where the box thought the system time was in the past (due to the fake hwclock setting) and didn't seem to set the correct time from NTP quickly enough, even though the server is on the LAN. @birdman and I thought it was due to my WiFi connection being slow and did all sorts of tweaks to the code and I tested various scenarios at the time. I never did resolve it satisfactorily, except by disabling the fake hwclock. The result is that the logs often are timestamped 1/1/1970, but at least the box gets the correct time after about 25-30 seconds and the various timer checks wait until the date/time is updated from 1/1/1970, so recordings and other power timers work as expected.
Maybe the default setting on a new image flash is to use the fake hwclock? I don't know at this stage as I have disabled it and I generally just run software updates rather than fresh image flashes.
As @ccs has indicated, there is no actual real-time clock in the Mutant. Similar to most of the boxes, the front panel is just given a countdown timer to the next wake-up event, so it just "ticks" away so many seconds and restarts. I found the Mutant front panel timer to be very accurate, though. It will wake up on time even days later. My MBTwin used to run fast (like @birdman's) but I got a firmware update which fixed the tick speed, but unfortunately messed up the display and caused other issues, because it was for another, slightly different, front panel.
