NTPsec

NTP0: x86 SBC, NTPSec, NTP-disciplined (stratum 2)
Six Hour - September 15, 2026 09:00 UTC

Report generated: Tue Sep 15 09:01:21 2026 UTC
Start Time: Tue Sep 15 03:01:21 2026 UTC
End Time: Tue Sep 15 09:01:21 2026 UTC
Report Period: 0.2 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 -67.262 -49.657 -31.966 1.114 32.520 55.894 102.117 64.486 105.551 19.794 0.784 µs 0.1137 4.185
Local Clock Frequency Offset -4.328 -3.028 -2.316 -1.283 -0.545 -0.122 0.410 1.771 2.906 0.563 -1.335 ppm -0.7575 5.033

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 6.666 9.853 13.305 22.622 42.554 51.856 69.898 29.249 42.003 9.317 24.901 µs 0.9103 3.684

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 114.434 185.130 226.697 383.522 765.143 894.244 1,122.797 538.446 709.114 167.615 427.182 ppb 0.9203 3.353

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 -67.262 -49.657 -31.966 1.114 32.520 55.894 102.117 64.486 105.551 19.794 0.784 µs 0.1137 4.185

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.328 -3.028 -2.316 -1.283 -0.545 -0.122 0.410 1.771 2.906 0.563 -1.335 ppm -0.7575 5.033
Temp ZONE0 54.000 54.000 54.000 57.000 63.000 63.000 63.000 9.000 9.000 3.764 57.944 °C
Temp ZONE1 54.000 54.000 55.000 58.000 64.000 65.000 65.000 9.000 11.000 3.699 59.549 °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 -67.263 -49.658 -31.967 1.115 32.521 55.895 102.118 64.488 105.553 19.794 0.784 µs 0.1137 4.184

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 0.673 13.208 18.741 36.761 75.215 101.917 152.705 56.474 88.709 17.821 39.761 µs 1.558 6.797

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 -26.151 -15.258 -10.195 9.194 44.919 67.902 102.527 55.114 83.160 16.807 11.450 µs 1.308 5.859

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 -3.480 6.733 17.875 38.141 77.539 104.443 135.602 59.664 97.710 18.163 40.349 µs 1.339 6.287

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 -23.961 -11.351 -3.820 14.560 50.399 75.519 112.557 54.219 86.870 17.135 17.215 µs 1.323 6.027

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 -2.292 11.371 21.068 49.900 91.539 122.879 180.679 70.471 111.508 22.158 52.436 µs 0.8114 4.339

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.738 4.552 11.703 34.018 61.379 75.285 513.331 49.676 70.733 24.580 36.051 µs 11.79 222.1

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 0.526 1.409 2.016 7.636 29.362 49.468 75.190 27.346 48.059 9.659 10.770 µs 2.187 9.487

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 1.257 3.549 5.461 14.635 36.619 50.137 93.641 31.158 46.588 10.105 17.052 µs 1.596 7.188

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 2.705 5.650 11.309 22.517 45.161 64.942 104.258 33.852 59.292 11.196 24.793 µs 1.595 7.68

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.632 4.881 7.374 17.723 39.739 59.713 107.536 32.365 54.832 10.947 20.097 µs 1.847 9.35

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 1.645 4.813 7.284 19.451 47.698 62.626 95.707 40.414 57.813 12.779 22.492 µs 1.227 4.83

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.328 -3.028 -2.316 -1.283 -0.545 -0.122 0.410 1.771 2.906 0.563 -1.335 ppm -0.7575 5.033
Local Clock Time Offset -67.262 -49.657 -31.966 1.114 32.520 55.894 102.117 64.486 105.551 19.794 0.784 µs 0.1137 4.185
Local RMS Frequency Jitter 114.434 185.130 226.697 383.522 765.143 894.244 1,122.797 538.446 709.114 167.615 427.182 ppb 0.9203 3.353
Local RMS Time Jitter 6.666 9.853 13.305 22.622 42.554 51.856 69.898 29.249 42.003 9.317 24.901 µs 0.9103 3.684
Server Jitter 10.0.50.10 1.738 4.552 11.703 34.018 61.379 75.285 513.331 49.676 70.733 24.580 36.051 µs 11.79 222.1
Server Jitter 10.0.50.100 0.526 1.409 2.016 7.636 29.362 49.468 75.190 27.346 48.059 9.659 10.770 µs 2.187 9.487
Server Jitter 10.0.50.20 1.257 3.549 5.461 14.635 36.619 50.137 93.641 31.158 46.588 10.105 17.052 µs 1.596 7.188
Server Jitter 10.0.50.30 2.705 5.650 11.309 22.517 45.161 64.942 104.258 33.852 59.292 11.196 24.793 µs 1.595 7.68
Server Jitter 10.0.50.40 2.632 4.881 7.374 17.723 39.739 59.713 107.536 32.365 54.832 10.947 20.097 µs 1.847 9.35
Server Jitter 10.0.50.50 1.645 4.813 7.284 19.451 47.698 62.626 95.707 40.414 57.813 12.779 22.492 µs 1.227 4.83
Server Offset 10.0.50.10 -67.263 -49.658 -31.967 1.115 32.521 55.895 102.118 64.488 105.553 19.794 0.784 µs 0.1137 4.184
Server Offset 10.0.50.100 0.673 13.208 18.741 36.761 75.215 101.917 152.705 56.474 88.709 17.821 39.761 µs 1.558 6.797
Server Offset 10.0.50.20 -26.151 -15.258 -10.195 9.194 44.919 67.902 102.527 55.114 83.160 16.807 11.450 µs 1.308 5.859
Server Offset 10.0.50.30 -3.480 6.733 17.875 38.141 77.539 104.443 135.602 59.664 97.710 18.163 40.349 µs 1.339 6.287
Server Offset 10.0.50.40 -23.961 -11.351 -3.820 14.560 50.399 75.519 112.557 54.219 86.870 17.135 17.215 µs 1.323 6.027
Server Offset 10.0.50.50 -2.292 11.371 21.068 49.900 91.539 122.879 180.679 70.471 111.508 22.158 52.436 µs 0.8114 4.339
Temp ZONE0 54.000 54.000 54.000 57.000 63.000 63.000 63.000 9.000 9.000 3.764 57.944 °C
Temp ZONE1 54.000 54.000 55.000 58.000 64.000 65.000 65.000 9.000 11.000 3.699 59.549 °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!