NTPsec

NTP0: x86 SBC, NTPSec, NTP-disciplined (stratum 2)
One Day - July 31, 2026 05:00 UTC

Report generated: Fri Jul 31 05:02:58 2026 UTC
Start Time: Thu Jul 30 05:02:58 2026 UTC
End Time: Fri Jul 31 05:02:58 2026 UTC
Report Period: 1.0 days

Return to It's About Time

Section Time Frame NTP Server
Local Clock Time/Frequency Offsets One Hour NTP0: x86 SBC, NTPSec, NTP-disciplined (stratum 2)
Local RMS Time Jitter Three Hour NTP1: RPi4B, Uputronics M8, NTPSec
Local RMS Frequency Jitter Six Hour NTP2: CM4, Bollar ZED-F9T, NTPSec
Local Clock Time Offset Histogram Twelve Hour NTP3: CM5, TimeHat LEA-M8T, NTPSec
Local Temperatures One Day NTP4: SecureSync, Rubidium, NTP (Classic)
Local Frequency/Temp Two Day NTP5: RPi3B+, Uputronics MAX-M8Q, NTPSec
Local GPS Three Day NTP6: CM4, TimeBeat OTC Mini, PTP
Server Offsets Seven Day NTP7: LeoNTP, Standalone GNSS, Firmware
Server Jitters Fourteen Day (Updated Daily)
Summary One Month (Updated Daily)
NTPQ Stats
GNSS Performance

NTP0 runs on a low-power x86 single board computer with no GNSS or PPS hardware; it is disciplined over the network by NTP only (stratum 2, from the GNSS fleet). It processes and renders the NTPViz reports and lets us observe the effects of CPU load on NTP jitter.

If graphs don't match report time above, force refresh the browser. The images have been cached.


Local Clock Time/Frequency Offsets

local offset plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Time Offset -87.565 -56.002 -40.985 1.481 45.097 70.911 123.176 86.082 126.913 25.552 1.368 µs 0.2321 3.657
Local Clock Frequency Offset -4.680 -3.316 -2.634 -1.315 -0.413 0.133 4.703 2.221 3.449 0.702 -1.393 ppm -0.3024 5.272

The time and frequency offsets between the ntpd calculated time and the local system clock. Showing frequency offset (red, in parts per million, scale on right) and the time offset (blue, in μs, scale on left). Quick changes in time offset will lead to larger frequency offsets.

These are fields 3 (time) and 4 (frequency) from the loopstats log file.



Local RMS Time Jitter

local jitter plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Time Jitter 13.349 17.924 21.636 34.079 50.500 59.418 84.561 28.864 41.494 8.832 34.791 µs 0.6069 3.81

The RMS Jitter of the local clock offset. In other words, how fast the local clock offset is changing.

Lower is better. An ideal system would be a horizontal line at 0μs.

RMS jitter is field 5 in the loopstats log file.



Local RMS Frequency Jitter

local stability plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local RMS Frequency Jitter 0.200 0.296 0.356 0.571 0.884 1.046 1.453 0.528 0.750 0.164 0.589 ppm 0.679 3.709

The RMS Frequency Jitter (aka wander) of the local clock's frequency. In other words, how fast the local clock changes frequency.

Lower is better. An ideal clock would be a horizontal line at 0ppm.

RMS Frequency Jitter is field 6 in the loopstats log file.



Local Clock Time Offset Histogram

local offset histogram plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Offset -87.565 -56.002 -40.985 1.481 45.097 70.911 123.176 86.082 126.913 25.552 1.368 µs 0.2321 3.657

The clock offsets of the local clock as a histogram.

The Local Clock Offset is field 3 from the loopstats log file.



Local Temperatures

local temps plot

Local temperatures. These will be site-specific depending upon what temperature sensors you collect data from. Temperature changes affect the local clock crystal frequency and stability. The math of how temperature changes frequency is complex, and also depends on crystal aging. So there is no easy way to correct for it in software. This is the single most important component of frequency drift.

The Local Temperatures are from field 3 from the tempstats log file.



Local Frequency/Temp

local freq temps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -4.680 -3.316 -2.634 -1.315 -0.413 0.133 4.703 2.221 3.449 0.702 -1.393 ppm -0.3024 5.272
Temp ZONE0 48.000 48.000 52.000 58.000 58.000 58.000 58.000 6.000 10.000 2.097 57.004 °C
Temp ZONE1 48.000 49.000 52.000 58.000 59.000 59.000 60.000 7.000 10.000 2.207 57.534 °C

The frequency offsets and temperatures. Showing frequency offset (red, in parts per million, scale on right) and the temperatures.

These are field 4 (frequency) from the loopstats log file, and field 3 from the tempstats log file.



Server Offsets

peer offsets plot

The offset of all refclocks and servers. This can be useful to see if offset changes are happening in a single clock or all clocks together.

Clock Offset is field 5 in the peerstats log file.



Server Offset 10.0.50.10

peer offset 10.0.50.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.50.10 -87.566 -56.003 -40.986 1.482 45.098 70.912 123.177 86.084 126.915 25.553 1.368 µs 0.232 3.656

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 10.0.50.100

peer offset 10.0.50.100 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.50.100 -310.154 -254.717 -82.337 39.796 190.737 236.150 317.954 273.074 490.867 80.539 35.731 µs -0.5049 6.153

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 10.0.50.20

peer offset 10.0.50.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.50.20 -347.796 -306.332 -128.965 -4.973 144.141 186.947 262.748 273.106 493.279 79.639 -10.023 µs -0.5474 6.337

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 10.0.50.30

peer offset 10.0.50.30 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.50.30 -318.225 -273.742 -93.802 22.651 169.987 216.036 278.848 263.789 489.778 78.698 18.149 µs -0.5337 6.379

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 10.0.50.40

peer offset 10.0.50.40 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.50.40 -340.530 -303.231 -120.921 0.285 149.541 192.976 272.179 270.462 496.207 80.299 -4.857 µs -0.574 6.375

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Offset 10.0.50.50

peer offset 10.0.50.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 10.0.50.50 -306.122 -244.563 -70.815 51.716 199.868 244.876 328.369 270.683 489.439 79.868 47.712 µs -0.5874 6.308

The offset of a server in seconds. This is useful to see how the measured offset is behaving.

The chart also plots offset±rtt, where rtt is the round trip time to the server. NTP can not really know the offset of a remote chimer, NTP computes it by subtracting rtt/2 from the offset. Plotting the offset±rtt reverses this calculation to more easily see the effects of rtt changes.

Closer to 0s is better. An ideal system would be a horizontal line at 0s. Typical 90% ranges may be: local LAN server 80µs; 90% ranges for WAN server may be 4ms and much larger.

Clock Offset is field 5 in the peerstats log file. The Round Trip Time (rtt) is field 6 in the peerstats log file.



Server Jitters

peer jitters plot

The RMS Jitter of all refclocks and servers. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 10.0.50.10

peer jitter 10.0.50.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.50.10 1.706 6.175 11.897 38.144 71.449 95.417 663.740 59.552 89.242 22.935 39.705 µs 6.281 109

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 10.0.50.100

peer jitter 10.0.50.100 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.50.100 1.297 3.830 6.955 18.772 40.894 57.245 442.400 33.939 53.415 12.970 20.959 µs 10.64 317.3

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 10.0.50.20

peer jitter 10.0.50.20 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.50.20 2.218 5.260 7.955 18.371 44.795 61.886 403.021 36.840 56.626 13.942 21.476 µs 8.651 207

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 10.0.50.30

peer jitter 10.0.50.30 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.50.30 3.057 7.016 9.987 21.417 43.698 57.930 395.015 33.711 50.914 11.331 23.351 µs 4.732 123.3

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 10.0.50.40

peer jitter 10.0.50.40 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.50.40 2.683 6.176 8.824 20.059 44.538 61.797 408.464 35.714 55.621 13.116 22.548 µs 7.41 186.9

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Server Jitter 10.0.50.50

peer jitter 10.0.50.50 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 10.0.50.50 4.685 9.991 13.435 25.985 51.330 68.074 361.094 37.895 58.083 13.497 28.528 µs 5.571 113.3

The RMS Jitter of a server. Jitter is the current estimated dispersion, in other words the variation in offset between samples.

Closer to 0s is better. An ideal system would be a horizontal line at 0s.

RMS Jitter is field 8 in the peerstats log file.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset -4.680 -3.316 -2.634 -1.315 -0.413 0.133 4.703 2.221 3.449 0.702 -1.393 ppm -0.3024 5.272
Local Clock Time Offset -87.565 -56.002 -40.985 1.481 45.097 70.911 123.176 86.082 126.913 25.552 1.368 µs 0.2321 3.657
Local RMS Frequency Jitter 0.200 0.296 0.356 0.571 0.884 1.046 1.453 0.528 0.750 0.164 0.589 ppm 0.679 3.709
Local RMS Time Jitter 13.349 17.924 21.636 34.079 50.500 59.418 84.561 28.864 41.494 8.832 34.791 µs 0.6069 3.81
Server Jitter 10.0.50.10 1.706 6.175 11.897 38.144 71.449 95.417 663.740 59.552 89.242 22.935 39.705 µs 6.281 109
Server Jitter 10.0.50.100 1.297 3.830 6.955 18.772 40.894 57.245 442.400 33.939 53.415 12.970 20.959 µs 10.64 317.3
Server Jitter 10.0.50.20 2.218 5.260 7.955 18.371 44.795 61.886 403.021 36.840 56.626 13.942 21.476 µs 8.651 207
Server Jitter 10.0.50.30 3.057 7.016 9.987 21.417 43.698 57.930 395.015 33.711 50.914 11.331 23.351 µs 4.732 123.3
Server Jitter 10.0.50.40 2.683 6.176 8.824 20.059 44.538 61.797 408.464 35.714 55.621 13.116 22.548 µs 7.41 186.9
Server Jitter 10.0.50.50 4.685 9.991 13.435 25.985 51.330 68.074 361.094 37.895 58.083 13.497 28.528 µs 5.571 113.3
Server Offset 10.0.50.10 -87.566 -56.003 -40.986 1.482 45.098 70.912 123.177 86.084 126.915 25.553 1.368 µs 0.232 3.656
Server Offset 10.0.50.100 -310.154 -254.717 -82.337 39.796 190.737 236.150 317.954 273.074 490.867 80.539 35.731 µs -0.5049 6.153
Server Offset 10.0.50.20 -347.796 -306.332 -128.965 -4.973 144.141 186.947 262.748 273.106 493.279 79.639 -10.023 µs -0.5474 6.337
Server Offset 10.0.50.30 -318.225 -273.742 -93.802 22.651 169.987 216.036 278.848 263.789 489.778 78.698 18.149 µs -0.5337 6.379
Server Offset 10.0.50.40 -340.530 -303.231 -120.921 0.285 149.541 192.976 272.179 270.462 496.207 80.299 -4.857 µs -0.574 6.375
Server Offset 10.0.50.50 -306.122 -244.563 -70.815 51.716 199.868 244.876 328.369 270.683 489.439 79.868 47.712 µs -0.5874 6.308
Temp ZONE0 48.000 48.000 52.000 58.000 58.000 58.000 58.000 6.000 10.000 2.097 57.004 °C
Temp ZONE1 48.000 49.000 52.000 58.000 59.000 59.000 60.000 7.000 10.000 2.207 57.534 °C
Summary as CSV file

Our production NTP servers share the same mast-mounted Tallysman Accutenna® TW3972 Triple Band GNSS Antenna + L-band Correction Services antenna using a Tallysman TW164 1-to-4 Port Smart Power GNSS Signal Splitter. No external NTP servers are contacted and all servers, with the exception of NTP6, the LeoNTP 1200, poll each other. Internal NTP clients poll NTP4 or NTP6.

The LeoNTP 1200 is a black-box appliance that doesn't support timing reporting. Its status can be checked by viwing the Server Jitter & Offset from any of the other servers. It can be found at NTP7 or leontp.bollar.com (10.0.50.100). The LeoNTP link above will take you to the Server Jitter between the LeoNTP and the currently selected server.

NTPQ Stats

NTPQ Statistics are not not available for this NTP server.'

GNSS Performance

GNSS Performance is not available for this NTP server.'

Glossary:

frequency offset:
The difference between the ntpd calculated frequency and the local system clock frequency (usually in parts per million, ppm)
jitter, dispersion:
The short term change in a value. NTP measures Local Time Jitter, Refclock Jitter, and Server Jitter in seconds. Local Frequency Jitter is in ppm or ppb.
ms, millisecond:
One thousandth of a second = 0.001 seconds, 1e-3 seconds
mu, mean:
The arithmetic mean: the sum of all the values divided by the number of values. The formula for mu is: "mu = (∑xi) / N". Where xi denotes the data points and N is the number of data points.
ns, nanosecond:
One billionth of a second, also one thousandth of a microsecond, 0.000000001 seconds and 1e-9 seconds.
percentile:
The value below which a given percentage of values fall.
ppb, parts per billion:
Ratio between two values. These following are all the same: 1 ppb, one in one billion, 1/1,000,000,000, 0.000,000,001, 1e-9 and 0.000,000,1%
ppm, parts per million:
Ratio between two values. These following are all the same: 1 ppm, one in one million, 1/1,000,000, 0.000,001, and 0.000,1%
‰, parts per thousand:
Ratio between two values. These following are all the same: 1 ‰. one in one thousand, 1/1,000, 0.001, and 0.1%
refclock:
Reference clock, a local GPS module or other local source of time.
remote clock:
Any clock reached over the network, LAN or WAN. Also called a peer or server.
time offset:
The difference between the ntpd calculated time and the local system clock's time. Also called phase offset.
σ, sigma:
Sigma denotes the standard deviation (SD) and is centered on the arithmetic mean of the data set. The SD is simply the square root of the variance of the data set. Two sigma is simply twice the standard deviation. Three sigma is three times sigma. Smaller is better.
The formula for sigma is: "σ = √[ ∑(xi-mu)^2 / N ]". Where xi denotes the data points and N is the number of data points.
Skewness, Skew:
The skewness of a random variable X is the third standardized moment and is a dimension-less ratio. ntpviz uses the FIsher-Pearson moment of skewness. There are other different ways to calculate Skewness Wikipedia describes Skewness best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
Kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses standard Kurtosis. There are other different ways to calculate Kurtosis.
A normal distribution has a Kurtosis of three. NIST describes a kurtosis over three as "heavy tailed" and one under three as "light tailed".
upstream clock:
Any server or reference clock used as a source of time.
µs, us, microsecond:
One millionth of a second, also one thousandth of a millisecond, 0.000,001 seconds, and 1e-6 seconds.



This page autogenerated by ntpviz, part of the NTPsec project
html 5    Valid CSS!