A stopped clock is right twice a day, but a running clock set to the wrong time is always wrong.
If the clock is running faster than regular time, it will at point catch up to regular time and thus be correct for a split second. If the clock is slower than regular time, regular time will catch up to the clock and the clock will be right for a split second.
Somehow this thing manages to accumulate an error of ~15 minutes in a month.
Could be right within 15 min accuracy in the appropriate timezone. And such a mechanism can be corrected for in the postprocessing step.