NTPsec

time.achjoj.info

Report generated: Thu Nov 19 05:33:02 2026 UTC
Start Time: Wed Nov 18 03:09:02 2026 UTC
End Time: Thu Nov 19 05:33:02 2026 UTC
Report Period: 1.1 days

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 -0.570 -0.516 -0.293 0.122 0.650 1.028 1.274 0.943 1.543 0.300 0.146 ms -1.062 4.178
Local Clock Frequency Offset 18.745 18.746 18.752 18.788 18.792 18.794 18.794 0.040 0.048 0.0129 18.782 ppm 3.081e+09 4.483e+12

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 136.819 141.436 158.375 252.069 368.776 428.582 435.049 210.401 287.146 68.334 258.715 µs 30.32 113

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.343 0.345 0.385 0.664 1.789 2.151 2.299 1.404 1.806 0.462 0.869 ppb 4.273 11.52

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 -0.570 -0.516 -0.293 0.122 0.650 1.028 1.274 0.943 1.543 0.300 0.146 ms -1.062 4.178

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 18.745 18.746 18.752 18.788 18.792 18.794 18.794 0.040 0.048 0.0129 18.782 ppm 3.081e+09 4.483e+12
Temp /dev/sdb 30.000 30.000 30.000 30.000 30.000 30.000 30.000 0.000 0.000 0.000 30.000 °C
Temp LM0 10.000 10.000 11.000 12.000 13.000 14.000 14.000 2.000 4.000 0.737 11.772 °C
Temp LM1 9.000 10.000 10.000 11.000 12.000 13.000 13.000 2.000 3.000 0.718 10.848 °C
Temp LM2 47.000 47.000 47.000 48.000 49.000 49.000 50.000 2.000 2.000 0.601 47.953 °C
Temp LM3 16.500 17.500 17.500 18.000 19.000 19.500 19.500 1.500 2.000 0.504 18.112 °C
Temp LM4 16.500 16.500 17.500 18.000 19.000 19.000 19.500 1.500 2.500 0.554 18.062 °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.



Local GPS

local gps plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
nSats 4.000 5.000 6.000 7.000 10.000 11.000 12.000 4.000 6.000 1.319 7.571 nSat 120.9 646.5
TDOP 0.560 0.620 0.710 1.140 1.890 3.420 4.300 1.180 2.800 0.473 1.231 11.66 54.41

Local GPS. The Time Dilution of Precision (TDOP) is plotted in blue. The number of visible satellites (nSat) is plotted in red.

TDOP is field 3, and nSats is field 4, from the gpsd log file. The gpsd log file is created by the ntploggps program.

TDOP is a dimensionless error factor. Smaller numbers are better. TDOP ranges from 1 (ideal), 2 to 5 (good), to greater than 20 (poor). Some GNSS receivers report TDOP less than one which is theoretically impossible.



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 150.254.190.51

peer offset 150.254.190.51 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 150.254.190.51 -0.290 -0.290 0.954 1.520 2.155 2.297 2.297 1.202 2.587 0.449 1.542 ms 20.6 65.93

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 153.19.250.123

peer offset 153.19.250.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 153.19.250.123 -0.919 -0.919 -0.531 0.180 0.747 1.310 1.310 1.279 2.229 0.452 0.147 ms -2.304 5.91

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 193.110.137.171

peer offset 193.110.137.171 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 193.110.137.171 -0.959 -0.959 -0.374 0.268 0.836 3.332 3.332 1.210 4.291 0.569 0.263 ms 0.637 11.43

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 194.146.251.100

peer offset 194.146.251.100 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.146.251.100 -1.822 -1.822 -0.521 0.087 1.339 2.911 2.911 1.861 4.733 0.649 0.202 ms -1.302 7.91

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 194.146.251.101

peer offset 194.146.251.101 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.146.251.101 -1.083 -1.083 -0.717 0.085 1.005 2.471 2.471 1.722 3.554 0.535 0.120 ms -1.602 8.026

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 194.29.130.252

peer offset 194.29.130.252 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 194.29.130.252 -0.670 -0.670 -0.174 0.260 1.096 1.736 1.736 1.270 2.406 0.408 0.331 ms 0.1537 3.93

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 195.187.245.55

peer offset 195.187.245.55 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 195.187.245.55 -808.180 -808.180 -505.608 -23.378 485.444 570.523 570.523 991.052 1,378.703 309.458 5.477 µs -4.056 9.719

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 213.135.57.60

peer offset 213.135.57.60 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 213.135.57.60 -921.761 -921.761 -559.158 -62.123 681.089 814.820 814.820 1,240.247 1,736.581 407.145 -26.187 µs -4.144 9.197

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 SHM(0)

peer offset SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(0) -5.380 -0.261 3.167 10.202 17.749 19.250 22.816 14.582 19.511 4.406 10.717 ms 7.141 18.75

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 150.254.190.51

peer jitter 150.254.190.51 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 150.254.190.51 0.176 0.176 0.299 0.837 3.845 4.015 4.015 3.546 3.839 0.978 1.185 ms 2.304 6.601

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 153.19.250.123

peer jitter 153.19.250.123 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 153.19.250.123 0.273 0.273 0.323 0.877 1.898 2.397 2.397 1.575 2.124 0.538 1.022 ms 3.884 9.315

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 193.110.137.171

peer jitter 193.110.137.171 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 193.110.137.171 0.109 0.109 0.376 0.729 2.117 2.561 2.561 1.741 2.451 0.560 0.924 ms 3.493 9.908

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 194.146.251.100

peer jitter 194.146.251.100 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.146.251.100 0.201 0.201 0.275 0.808 2.241 3.115 3.115 1.967 2.914 0.675 1.055 ms 2.757 6.906

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 194.146.251.101

peer jitter 194.146.251.101 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.146.251.101 0.147 0.147 0.256 0.749 1.700 1.772 1.772 1.445 1.626 0.438 0.838 ms 4.106 10.21

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 194.29.130.252

peer jitter 194.29.130.252 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 194.29.130.252 0.168 0.168 0.229 0.725 3.001 3.076 3.076 2.772 2.908 0.793 1.023 ms 2.236 5.914

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 195.187.245.55

peer jitter 195.187.245.55 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 195.187.245.55 0.275 0.275 0.283 0.734 1.948 2.329 2.329 1.665 2.054 0.556 0.930 ms 3.008 7.055

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 213.135.57.60

peer jitter 213.135.57.60 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 213.135.57.60 0.310 0.310 0.349 0.754 2.053 2.423 2.423 1.704 2.114 0.519 0.870 ms 3.709 10.91

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 SHM(0)

peer jitter SHM(0) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(0) 0.145 0.496 0.761 2.018 4.780 6.305 8.564 4.019 5.810 1.262 2.293 ms 4.137 12.62

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 18.745 18.746 18.752 18.788 18.792 18.794 18.794 0.040 0.048 0.0129 18.782 ppm 3.081e+09 4.483e+12
Local Clock Time Offset -0.570 -0.516 -0.293 0.122 0.650 1.028 1.274 0.943 1.543 0.300 0.146 ms -1.062 4.178
Local RMS Frequency Jitter 0.343 0.345 0.385 0.664 1.789 2.151 2.299 1.404 1.806 0.462 0.869 ppb 4.273 11.52
Local RMS Time Jitter 136.819 141.436 158.375 252.069 368.776 428.582 435.049 210.401 287.146 68.334 258.715 µs 30.32 113
Server Jitter 150.254.190.51 0.176 0.176 0.299 0.837 3.845 4.015 4.015 3.546 3.839 0.978 1.185 ms 2.304 6.601
Server Jitter 153.19.250.123 0.273 0.273 0.323 0.877 1.898 2.397 2.397 1.575 2.124 0.538 1.022 ms 3.884 9.315
Server Jitter 193.110.137.171 0.109 0.109 0.376 0.729 2.117 2.561 2.561 1.741 2.451 0.560 0.924 ms 3.493 9.908
Server Jitter 194.146.251.100 0.201 0.201 0.275 0.808 2.241 3.115 3.115 1.967 2.914 0.675 1.055 ms 2.757 6.906
Server Jitter 194.146.251.101 0.147 0.147 0.256 0.749 1.700 1.772 1.772 1.445 1.626 0.438 0.838 ms 4.106 10.21
Server Jitter 194.29.130.252 0.168 0.168 0.229 0.725 3.001 3.076 3.076 2.772 2.908 0.793 1.023 ms 2.236 5.914
Server Jitter 195.187.245.55 0.275 0.275 0.283 0.734 1.948 2.329 2.329 1.665 2.054 0.556 0.930 ms 3.008 7.055
Server Jitter 213.135.57.60 0.310 0.310 0.349 0.754 2.053 2.423 2.423 1.704 2.114 0.519 0.870 ms 3.709 10.91
Server Jitter SHM(0) 0.145 0.496 0.761 2.018 4.780 6.305 8.564 4.019 5.810 1.262 2.293 ms 4.137 12.62
Server Offset 150.254.190.51 -0.290 -0.290 0.954 1.520 2.155 2.297 2.297 1.202 2.587 0.449 1.542 ms 20.6 65.93
Server Offset 153.19.250.123 -0.919 -0.919 -0.531 0.180 0.747 1.310 1.310 1.279 2.229 0.452 0.147 ms -2.304 5.91
Server Offset 193.110.137.171 -0.959 -0.959 -0.374 0.268 0.836 3.332 3.332 1.210 4.291 0.569 0.263 ms 0.637 11.43
Server Offset 194.146.251.100 -1.822 -1.822 -0.521 0.087 1.339 2.911 2.911 1.861 4.733 0.649 0.202 ms -1.302 7.91
Server Offset 194.146.251.101 -1.083 -1.083 -0.717 0.085 1.005 2.471 2.471 1.722 3.554 0.535 0.120 ms -1.602 8.026
Server Offset 194.29.130.252 -0.670 -0.670 -0.174 0.260 1.096 1.736 1.736 1.270 2.406 0.408 0.331 ms 0.1537 3.93
Server Offset 195.187.245.55 -808.180 -808.180 -505.608 -23.378 485.444 570.523 570.523 991.052 1,378.703 309.458 5.477 µs -4.056 9.719
Server Offset 213.135.57.60 -921.761 -921.761 -559.158 -62.123 681.089 814.820 814.820 1,240.247 1,736.581 407.145 -26.187 µs -4.144 9.197
Server Offset SHM(0) -5.380 -0.261 3.167 10.202 17.749 19.250 22.816 14.582 19.511 4.406 10.717 ms 7.141 18.75
TDOP 0.560 0.620 0.710 1.140 1.890 3.420 4.300 1.180 2.800 0.473 1.231 11.66 54.41
Temp /dev/sdb 30.000 30.000 30.000 30.000 30.000 30.000 30.000 0.000 0.000 0.000 30.000 °C
Temp LM0 10.000 10.000 11.000 12.000 13.000 14.000 14.000 2.000 4.000 0.737 11.772 °C
Temp LM1 9.000 10.000 10.000 11.000 12.000 13.000 13.000 2.000 3.000 0.718 10.848 °C
Temp LM2 47.000 47.000 47.000 48.000 49.000 49.000 50.000 2.000 2.000 0.601 47.953 °C
Temp LM3 16.500 17.500 17.500 18.000 19.000 19.500 19.500 1.500 2.000 0.504 18.112 °C
Temp LM4 16.500 16.500 17.500 18.000 19.000 19.000 19.500 1.500 2.500 0.554 18.062 °C
nSats 4.000 5.000 6.000 7.000 10.000 11.000 12.000 4.000 6.000 1.319 7.571 nSat 120.9 646.5
Summary as CSV file

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.
kurtosis, Kurt:
The kurtosis of a random variable X is the fourth standardized moment and is a dimension-less ratio. ntpviz uses the Pearson's moment coefficient of 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".
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 Pearson's moment coefficient of skewness. Wikipedia describes it best: "The qualitative interpretation of the skew is complicated and unintuitive."
A normal distribution has a skewness of zero.
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!