ntp.vanhaarst.net

A GPS-disciplined stratum-1 NTP server in Wageningen, the Netherlands.

Serving time — stratum 1, locked to PPS

Use it

Point your client at ntp.vanhaarst.net. It answers NTPv4 over both IPv4 and IPv6.

chrony — /etc/chrony/chrony.conf

server ntp.vanhaarst.net iburst

ntpd — /etc/ntp.conf

server ntp.vanhaarst.net iburst

systemd-timesyncd — /etc/systemd/timesyncd.conf

[Time]
NTP=ntp.vanhaarst.net

macOS

sudo sntp -sS ntp.vanhaarst.net

Windows

w32tm /config /manualpeerlist:"ntp.vanhaarst.net" /syncfromflags:manual /update

One server is one opinion. For anything that matters, give your client three or four sources so it can outvote a liar: a public pool plus this one is a good mix.

The clock right now

Stratum1 1 means it is disciplined by a local reference, not by another server over the network.
Reference PPS (refid 50505300) PPS is the receiver's pulse-per-second output, the signal that makes stratum 1 worth having.
Current offset-284 ns How far the system clock sat from the reference at the last update.
RMS offset+1.1 µs The long-run average of that error, which is the honest figure to quote.
Root dispersion+13.4 µs The server's own estimate of its maximum error, and what it advertises to clients.
Root delay+1 ns Round-trip delay to the reference. Near zero because the reference is attached, not remote.
Frequency6.677 ppm How fast the oscillator runs on its own. A constant value here is a healthy crystal.
Skew0.018 ppm Uncertainty in that frequency estimate.
Update interval16 s How often chronyd currently corrects the clock.

The reference

PPS offset-456 ns The pulse itself. This is the number that sets the server's accuracy.
NMEA offset-40.08 ms The serial time message, tens of milliseconds out by nature. It only has to name the right second; the pulse does the rest.
GNSS fix3D fixA 3D fix is needed for the position solution the timing depends on.
Satellites 19 used of 33 seen Across every constellation the receiver tracks.
ConstellationUsedSeen
GPS811
Galileo610
GLONASS59
SBAS03

What it serves

Requests answered 2,560,448 Since chronyd last started.
Requests dropped 0 Rate limiting and malformed packets.
Current rate 1.3 /s Averaged over the last five minutes.
Clients, last 5m197 Distinct addresses that asked. This is demand.
Clients, last 15m452
Clients, last 1h1,258
Clients, last 6h5,101
Clients, last 24h16,091
Countries164 Resolved from client addresses by a local GeoIP database.
Client log131,072 entries Every address chronyd has ever answered, until clientloglimit evicts the oldest. A saturation indicator, not a client count.
Uptime17d 0hOf the host, not of chronyd.

The machine

Raspberry Pi with a Uputronics GPS/RTC HAT (u-blox MAX-M8Q).

The receiver's pulse-per-second output drives the clock; the NMEA sentences over the serial line only label the second. chronyd disciplines the system clock from the pulse and cross-checks it against public servers, which is why stratum 1 here means an attached reference rather than a claim about the network.