After abrupt shutdown (no more battery on laptop), on next reboot my system time was off by one hour.

From system logs
Jul  8 14:15:05 localhost ntpd_intres[2299]: host name not found: pool.ntp.org

And later:
Jul  8 14:18:40 localhost ntpd[2180]: 0.0.0.0 0617 07 panic_stop +3598 s; set clock manually within 1000 s.
Jul  8 14:18:40 localhost systemd[1]: ntpd.service: main process exited, code=exited, status=255
Jul  8 14:18:40 localhost systemd[1]: Unit ntpd.service entered failed state.


# systemctl status ntpd.service 
ntpd.service - Network Time Service
	  Loaded: loaded (/lib/systemd/system/ntpd.service; enabled)
	  Active: failed (Result: exit-code) since Sun, 08 Jul 2012 14:18:40 +0200; 7h ago
	 Process: 2171 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, status=0/SUCCESS)
	Main PID: 2180 (code=exited, status=255)
	  CGroup: name=systemd:/system/ntpd.service

Jul 08 14:15:19 localhost.localdomain ntpd[2180]: Listen normally on 4 wlan0 fe80::3a59:f9ff:fe0d:c97f UDP 123
Jul 08 14:15:19 localhost.localdomain ntpd[2180]: peers refreshed
Jul 08 14:15:19 localhost.localdomain ntpd[2180]: new interface(s) found: waking up resolver
Jul 08 14:15:21 localhost.localdomain ntpd_intres[2299]: DNS pool.ntp.org -> 193.55.167.1
Jul 08 14:15:22 localhost.localdomain ntpd[2180]: Listen normally on 5 wlan0 192.168.0.13 UDP 123
Jul 08 14:15:22 localhost.localdomain ntpd[2180]: peers refreshed
Jul 08 14:15:22 localhost.localdomain ntpd[2180]: new interface(s) found: waking up resolver
Jul 08 14:15:25 localhost.localdomain ntpd[2180]: Listen normally on 6 wlan0 2a01:e35:8a0b:8670:3a59:f9ff:fe0d:c97f UDP 123
Jul 08 14:15:25 localhost.localdomain ntpd[2180]: peers refreshed
Jul 08 14:15:25 localhost.localdomain ntpd[2180]: new interface(s) found: waking up resolver
# systemctl status ntpdate.service 
ntpdate.service - Set time via NTP
	  Loaded: loaded (/lib/systemd/system/ntpdate.service; static)
	  Active: inactive (dead)
	  CGroup: name=systemd:/system/ntpdate.service