NTPsec

time.achjoj.info

Report generated: Tue Nov 17 17:33:02 2026 UTC
Start Time: Mon Nov 16 15:09:02 2026 UTC
End Time: Tue Nov 17 17: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 -1.515 -1.396 -0.806 0.218 0.939 1.503 1.636 1.744 2.899 0.508 0.164 ms -2.853 9.105
Local Clock Frequency Offset 17.607 17.878 18.175 18.700 21.007 21.634 21.890 2.832 3.757 0.855 18.971 ppm 9590 2.047e+05

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 129.612 138.561 169.277 301.701 482.223 541.941 607.948 312.946 403.380 96.257 311.606 µs 18.28 60.94

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.676 0.692 0.825 17.374 542.540 716.270 818.240 541.715 715.578 204.946 154.701 ppb 0.3418 2.264

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 -1.515 -1.396 -0.806 0.218 0.939 1.503 1.636 1.744 2.899 0.508 0.164 ms -2.853 9.105

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 17.607 17.878 18.175 18.700 21.007 21.634 21.890 2.832 3.757 0.855 18.971 ppm 9590 2.047e+05
Temp /dev/sdb 29.000 29.000 29.000 30.000 30.000 30.000 30.000 1.000 1.000 0.449 29.719 °C
Temp LM0 9.000 10.000 10.000 11.000 13.000 14.000 15.000 3.000 4.000 0.979 11.429 °C
Temp LM1 9.000 9.000 9.000 11.000 12.000 14.000 14.000 3.000 5.000 1.005 10.685 °C
Temp LM2 47.000 47.000 47.000 47.000 49.000 49.000 50.000 2.000 2.000 0.681 47.464 °C
Temp LM3 16.500 16.500 17.500 18.000 19.500 19.500 20.500 2.000 3.000 0.686 18.144 °C
Temp LM4 16.500 16.500 17.500 18.000 19.500 19.500 20.500 2.000 3.000 0.689 18.079 °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 5.000 5.000 5.000 8.000 10.000 11.000 11.000 5.000 6.000 1.333 7.640 nSat 120.4 642
TDOP 0.620 0.650 0.740 1.120 2.190 3.160 6.200 1.450 2.510 0.561 1.250 9.553 60.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.496 -0.496 0.223 1.556 2.514 3.241 3.241 2.291 3.737 0.700 1.523 ms 4.816 11.96

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 -1.939 -1.939 -0.943 0.451 1.643 2.806 2.806 2.585 4.745 0.761 0.418 ms -1.576 5.848

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 -1.618 -1.618 -1.204 0.208 1.265 1.927 1.927 2.469 3.545 0.623 0.173 ms -2.771 8.789

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.995 -1.995 -1.354 0.237 1.099 2.318 2.318 2.453 4.314 0.733 0.170 ms -3.073 9.641

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 -2.214 -2.214 -0.902 0.300 1.185 3.992 3.992 2.087 6.206 0.801 0.312 ms -1.214 8.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 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 -1.644 -1.644 -0.769 0.396 1.360 2.864 2.864 2.129 4.507 0.726 0.389 ms -1.397 5.306

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 -1.959 -1.959 -1.044 0.023 1.058 2.470 2.470 2.103 4.429 0.721 0.011 ms -3.633 10.4

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 -1.645 -1.645 -0.971 0.194 1.397 3.625 3.625 2.368 5.270 0.759 0.246 ms -1.396 7.424

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.093 -0.622 3.094 10.166 18.063 19.710 22.040 14.969 20.332 4.508 10.620 ms 6.49 16.83

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.323 0.323 0.486 1.241 3.831 6.532 6.532 3.344 6.210 1.010 1.411 ms 3.685 15.6

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.244 0.244 0.395 1.201 3.800 17.795 17.795 3.405 17.551 2.093 1.652 ms 5.36 40.49

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.224 0.224 0.288 1.009 2.185 2.418 2.418 1.897 2.193 0.579 1.062 ms 3.51 8.214

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.215 0.215 0.331 1.195 2.150 2.648 2.648 1.819 2.433 0.602 1.148 ms 3.745 8.864

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.239 0.239 0.406 1.206 3.210 17.406 17.406 2.804 17.167 2.659 1.800 ms 4.017 23.53

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.481 0.481 0.556 1.038 17.325 18.500 18.500 16.769 18.019 4.480 2.548 ms 1.598 6.142

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.264 0.264 0.437 1.138 2.742 3.944 3.944 2.305 3.681 0.717 1.292 ms 4.044 11.99

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.251 0.251 0.322 1.296 18.411 18.540 18.540 18.089 18.289 4.873 2.838 ms 1.433 5.297

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.250 0.552 0.822 2.014 4.729 6.318 9.206 3.907 5.765 1.239 2.287 ms 4.423 14.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.



Summary


Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Local Clock Frequency Offset 17.607 17.878 18.175 18.700 21.007 21.634 21.890 2.832 3.757 0.855 18.971 ppm 9590 2.047e+05
Local Clock Time Offset -1.515 -1.396 -0.806 0.218 0.939 1.503 1.636 1.744 2.899 0.508 0.164 ms -2.853 9.105
Local RMS Frequency Jitter 0.676 0.692 0.825 17.374 542.540 716.270 818.240 541.715 715.578 204.946 154.701 ppb 0.3418 2.264
Local RMS Time Jitter 129.612 138.561 169.277 301.701 482.223 541.941 607.948 312.946 403.380 96.257 311.606 µs 18.28 60.94
Server Jitter 150.254.190.51 0.323 0.323 0.486 1.241 3.831 6.532 6.532 3.344 6.210 1.010 1.411 ms 3.685 15.6
Server Jitter 153.19.250.123 0.244 0.244 0.395 1.201 3.800 17.795 17.795 3.405 17.551 2.093 1.652 ms 5.36 40.49
Server Jitter 193.110.137.171 0.224 0.224 0.288 1.009 2.185 2.418 2.418 1.897 2.193 0.579 1.062 ms 3.51 8.214
Server Jitter 194.146.251.100 0.215 0.215 0.331 1.195 2.150 2.648 2.648 1.819 2.433 0.602 1.148 ms 3.745 8.864
Server Jitter 194.146.251.101 0.239 0.239 0.406 1.206 3.210 17.406 17.406 2.804 17.167 2.659 1.800 ms 4.017 23.53
Server Jitter 194.29.130.252 0.481 0.481 0.556 1.038 17.325 18.500 18.500 16.769 18.019 4.480 2.548 ms 1.598 6.142
Server Jitter 195.187.245.55 0.264 0.264 0.437 1.138 2.742 3.944 3.944 2.305 3.681 0.717 1.292 ms 4.044 11.99
Server Jitter 213.135.57.60 0.251 0.251 0.322 1.296 18.411 18.540 18.540 18.089 18.289 4.873 2.838 ms 1.433 5.297
Server Jitter SHM(0) 0.250 0.552 0.822 2.014 4.729 6.318 9.206 3.907 5.765 1.239 2.287 ms 4.423 14.21
Server Offset 150.254.190.51 -0.496 -0.496 0.223 1.556 2.514 3.241 3.241 2.291 3.737 0.700 1.523 ms 4.816 11.96
Server Offset 153.19.250.123 -1.939 -1.939 -0.943 0.451 1.643 2.806 2.806 2.585 4.745 0.761 0.418 ms -1.576 5.848
Server Offset 193.110.137.171 -1.618 -1.618 -1.204 0.208 1.265 1.927 1.927 2.469 3.545 0.623 0.173 ms -2.771 8.789
Server Offset 194.146.251.100 -1.995 -1.995 -1.354 0.237 1.099 2.318 2.318 2.453 4.314 0.733 0.170 ms -3.073 9.641
Server Offset 194.146.251.101 -2.214 -2.214 -0.902 0.300 1.185 3.992 3.992 2.087 6.206 0.801 0.312 ms -1.214 8.656
Server Offset 194.29.130.252 -1.644 -1.644 -0.769 0.396 1.360 2.864 2.864 2.129 4.507 0.726 0.389 ms -1.397 5.306
Server Offset 195.187.245.55 -1.959 -1.959 -1.044 0.023 1.058 2.470 2.470 2.103 4.429 0.721 0.011 ms -3.633 10.4
Server Offset 213.135.57.60 -1.645 -1.645 -0.971 0.194 1.397 3.625 3.625 2.368 5.270 0.759 0.246 ms -1.396 7.424
Server Offset SHM(0) -5.093 -0.622 3.094 10.166 18.063 19.710 22.040 14.969 20.332 4.508 10.620 ms 6.49 16.83
TDOP 0.620 0.650 0.740 1.120 2.190 3.160 6.200 1.450 2.510 0.561 1.250 9.553 60.41
Temp /dev/sdb 29.000 29.000 29.000 30.000 30.000 30.000 30.000 1.000 1.000 0.449 29.719 °C
Temp LM0 9.000 10.000 10.000 11.000 13.000 14.000 15.000 3.000 4.000 0.979 11.429 °C
Temp LM1 9.000 9.000 9.000 11.000 12.000 14.000 14.000 3.000 5.000 1.005 10.685 °C
Temp LM2 47.000 47.000 47.000 47.000 49.000 49.000 50.000 2.000 2.000 0.681 47.464 °C
Temp LM3 16.500 16.500 17.500 18.000 19.500 19.500 20.500 2.000 3.000 0.686 18.144 °C
Temp LM4 16.500 16.500 17.500 18.000 19.500 19.500 20.500 2.000 3.000 0.689 18.079 °C
nSats 5.000 5.000 5.000 8.000 10.000 11.000 11.000 5.000 6.000 1.333 7.640 nSat 120.4 642
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!