A 24-minute offset doesn’t match any standard timezone difference, so this is almost certainly a sync failure rather than a timezone misconfiguration. The PLC is likely running on its internal clock which has drifted.
Two additional things worth checking:
Network Connectivity – Make sure the PLC can reach the NTP server. If a firewall is blocking this traffic, the NTP client will silently fail to synchronize, and the PLC will continue running on its internal clock, which can drift significantly over time.
Logger – In Automation Studio, go to Online → Logger and look for entries related to time changes. If NTP is synchronizing successfully, you will see log entries confirming it. If there are no such entries, it means synchronization is not occurring — which would explain the 24-minute drift.
Are the PLC and NTP server in the same network? If not, is the Ethernet parameters-Default gateway set? This has solved a time synchronization issue in the past for our customer.
last but not least, the stratum of a NTP server has to have a minimum accurancy setting so that the PLC accepts time synchronisation with this server.
Please see the following post for more details, including a link to the stratum information: