System Time is more than an hour in the future with chrony

I’ve set up chrony like this a few days ago:

  networking.timeServers = ["nts.netnod.se" "ntppool1.time.nl" "ntppool2.time.nl" "ntp3.ipv6.fau.de" "ptbtime1.ptb.de" "ptbtime2.ptb.de" "ptbtime3.ptb.de" "ptbtime4.ptb.de" "paris.time.system76.com"];
  services.chrony = {
    enable = true;
    enableNTS = true;
    extraFlags = ["-r" "-s"];
    extraConfig = ''
      rtcfile /var/lib/chrony/rtc
      rtcautotrim 1
    '';
  };

By now, my system time is more than an hour in the future and i could see the offset increasing, then decreasing and now increasing againg throughout the day. chrony even tells me the exact offset when running chronyc tracking but it doesn’t correct it and instead runs the system time on insane speeds, even though it shows excellent synchronization of the ntp servers if i understand the output correctly:

chronyc -N 'sources -v'

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current best, '+' = combined, '-' = not combined,
| /             'x' = may be in error, '~' = too variable, '?' = unusable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^+ nts.netnod.se                 1   9   377    72   +267us[ +267us] +/-   13ms
^+ ntppool1.time.nl              1   9   377   172  -1315us[-1313us] +/-   12ms
^+ ntppool2.time.nl              1   9   377    17  -2148us[-2148us] +/-   12ms
^+ ntp3.ipv6.fau.de              1   9   377    75   +281us[ +281us] +/- 7632us
^+ ptbtime1.ptb.de               1  10   377   787  -1028us[-1251us] +/- 8704us
^+ ptbtime2.ptb.de               1   8   377    18    +71us[  +71us] +/- 8407us
^* ptbtime3.ptb.de               1   8   377   146   -285us[ -283us] +/- 9219us
^+ ptbtime4.ptb.de               1   9   377   235   -761us[ -757us] +/-   12ms
^+ paris.time.system76.com       2   9   377    18   -971us[ -971us] +/-   20ms

doas chronyc -N 'selectdata -v'

  . State: N - noselect, s - unsynchronised, M - missing samples,
 /         d/D - large distance, ~ - jittery, w/W - waits for others,
|          S - stale, O - orphan, T - not trusted, P - not preferred,
|          U - waits for update,, x - falseticker, + - combined, * - best.
|   Effective options   ---------.  (N - noselect, P - prefer
|   Configured options  ----.     \  T - trust, R - require)
|   Auth. enabled (Y/N) -.   \     \     Offset interval --.
|                        |    |     |                       |
S Name/IP Address        Auth COpts EOpts Last Score     Interval  Leap
=======================================================================
+ nts.netnod.se             Y ----- -----   54   1.0   -13ms   +13ms  N
+ ntppool1.time.nl          Y ----- -----  154   1.0   -13ms   +10ms  N
+ ntppool2.time.nl          Y ----- -----    0   1.0   -13ms +9451us  N
+ ntp3.ipv6.fau.de          Y ----- -----   57   5.2 -7386us +7917us  N
+ ptbtime1.ptb.de           Y ----- -----  770   1.0 -9768us +8368us  N
+ ptbtime2.ptb.de           Y ----- -----    1   2.1 -8126us +8464us  N
* ptbtime3.ptb.de           Y ----- -----  128   1.0 -8646us +8436us  N
+ ptbtime4.ptb.de           Y ----- -----  217   1.0   -12ms   +13ms  N
+ paris.time.system76.com   Y ----- -----    0   1.0   -19ms   +18ms  N

chronyc tracking


Reference ID    : CD2EB2A9 (ptbtime3.ptb.de)
Stratum         : 2
Ref time (UTC)  : Thu Oct 26 15:40:50 2023
System time     : 4171.440429688 seconds fast of NTP time
Last offset     : +0.000002116 seconds
RMS offset      : 0.000175739 seconds
Frequency       : 16.229 ppm slow
Residual freq   : -0.005 ppm
Skew            : 0.128 ppm
Root delay      : 0.016128374 seconds
Root dispersion : 0.000859459 seconds
Update interval : 258.3 seconds
Leap status     : Normal

chronyc rtcdata

RTC ref time (UTC) : Thu Oct 26 15:41:49 2023
Number of samples  : 11
Number of runs     : 4
Sample span period :  43m
RTC is fast by     :    -0.124112 seconds
RTC gains time at  :    -5.512 ppm

What am i doing wrong?