NTPsec

time.achjoj.info

Report generated: Sun Nov 22 17:33:02 2026 UTC
Start Time: Sat Nov 21 15:09:01 2026 UTC
End Time: Sun Nov 22 17:33:01 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.777 -1.519 -0.413 0.516 1.160 1.376 1.459 1.572 2.896 0.535 0.420 ms -1.795 6.813
Local Clock Frequency Offset 18.147 18.150 18.265 18.450 18.553 18.615 18.636 0.289 0.465 0.091 18.439 ppm 8.155e+06 1.641e+09

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 0.477 144.598 168.464 254.365 518.651 624.815 628.377 350.187 480.217 98.795 279.363 µs 13.18 48.96

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.000 0.000 1.362 10.237 73.777 97.314 104.016 72.415 97.314 24.108 20.195 ppb 0.9153 3.373

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.777 -1.519 -0.413 0.516 1.160 1.376 1.459 1.572 2.896 0.535 0.420 ms -1.795 6.813

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.147 18.150 18.265 18.450 18.553 18.615 18.636 0.289 0.465 0.091 18.439 ppm 8.155e+06 1.641e+09
Temp /dev/sdb 29.000 29.000 29.000 29.000 30.000 30.000 30.000 1.000 1.000 0.322 29.117 °C
Temp LM0 8.000 8.000 9.000 11.000 17.000 18.000 18.000 8.000 10.000 2.105 10.962 °C
Temp LM1 8.000 8.000 8.000 10.000 17.000 17.000 18.000 9.000 9.000 2.179 10.232 °C
Temp LM2 46.000 46.000 46.000 47.000 50.000 50.000 51.000 4.000 4.000 1.164 46.978 °C
Temp LM3 16.000 16.000 16.500 17.500 21.000 21.500 21.500 4.500 5.500 1.229 17.821 °C
Temp LM4 16.000 16.000 16.500 17.500 21.000 21.500 21.500 4.500 5.500 1.260 17.803 °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 8.000 10.000 11.000 11.000 4.000 6.000 1.283 7.581 nSat 133.1 731.7
TDOP 0.620 0.660 0.740 1.120 2.020 3.280 5.140 1.280 2.620 0.488 1.231 11.3 59.12

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 -398.556 -398.556 -1.399 0.565 1.514 3.081 3.081 2.913 401.637 61.546 -9.303 ms -11.14 77.11

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 -397.495 -397.495 -1.264 0.369 1.031 1.258 1.258 2.294 398.754 44.477 -4.726 ms -13.39 124.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 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.854 -1.854 -1.271 0.487 1.504 2.403 2.403 2.774 4.257 0.750 0.499 ms -1.687 6.415

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 -399.422 -399.422 -2.629 0.370 1.320 2.254 2.254 3.949 401.675 85.677 -19.047 ms -9.682 50.23

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 -399.351 -399.351 -1.211 0.391 1.316 2.160 2.160 2.527 401.511 86.779 -19.493 ms -9.64 49.53

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 -398.909 -398.909 -2.961 0.646 1.676 2.291 2.291 4.637 401.200 73.906 -13.664 ms -10.22 60.13

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 -399.400 -399.400 -3.018 0.161 1.043 4.073 4.073 4.061 403.473 63.103 -10.170 ms -11.05 74.78

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 -399.675 -399.675 -2.859 0.243 0.984 3.096 3.096 3.843 402.772 74.875 -14.471 ms -10.21 59.49

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) -394.315 0.944 3.790 10.708 18.388 20.242 23.307 14.597 19.298 8.289 11.208 ms -32.2 1506

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.000 0.000 0.244 0.920 2.333 4.181 4.181 2.089 4.181 0.762 1.137 ms 3.169 11.45

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.000 0.000 0.288 0.965 2.043 2.279 2.279 1.755 2.279 0.580 1.112 ms 3.597 7.814

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.000 0.000 0.251 0.876 6.892 7.297 7.297 6.640 7.297 1.600 1.379 ms 2.207 8.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 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.000 0.000 0.276 0.899 2.245 4.928 4.928 1.969 4.928 0.724 0.987 ms 3.617 17.01

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.000 0.000 0.159 0.962 2.469 3.183 3.183 2.311 3.183 0.711 1.034 ms 2.108 5.31

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.000 0.000 0.345 0.802 2.410 3.120 3.120 2.065 3.120 0.618 0.999 ms 3.516 10.89

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.000 0.000 0.307 0.724 2.804 6.741 6.741 2.497 6.741 1.037 1.114 ms 2.945 14.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 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.000 0.000 0.374 0.827 2.103 2.528 2.528 1.729 2.528 0.543 0.985 ms 3.987 11.25

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.000 0.533 0.790 2.029 4.872 6.415 351.928 4.082 5.883 7.403 2.548 ms 30.93 1173

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.147 18.150 18.265 18.450 18.553 18.615 18.636 0.289 0.465 0.091 18.439 ppm 8.155e+06 1.641e+09
Local Clock Time Offset -1.777 -1.519 -0.413 0.516 1.160 1.376 1.459 1.572 2.896 0.535 0.420 ms -1.795 6.813
Local RMS Frequency Jitter 0.000 0.000 1.362 10.237 73.777 97.314 104.016 72.415 97.314 24.108 20.195 ppb 0.9153 3.373
Local RMS Time Jitter 0.477 144.598 168.464 254.365 518.651 624.815 628.377 350.187 480.217 98.795 279.363 µs 13.18 48.96
Server Jitter 150.254.190.51 0.000 0.000 0.244 0.920 2.333 4.181 4.181 2.089 4.181 0.762 1.137 ms 3.169 11.45
Server Jitter 153.19.250.123 0.000 0.000 0.288 0.965 2.043 2.279 2.279 1.755 2.279 0.580 1.112 ms 3.597 7.814
Server Jitter 193.110.137.171 0.000 0.000 0.251 0.876 6.892 7.297 7.297 6.640 7.297 1.600 1.379 ms 2.207 8.142
Server Jitter 194.146.251.100 0.000 0.000 0.276 0.899 2.245 4.928 4.928 1.969 4.928 0.724 0.987 ms 3.617 17.01
Server Jitter 194.146.251.101 0.000 0.000 0.159 0.962 2.469 3.183 3.183 2.311 3.183 0.711 1.034 ms 2.108 5.31
Server Jitter 194.29.130.252 0.000 0.000 0.345 0.802 2.410 3.120 3.120 2.065 3.120 0.618 0.999 ms 3.516 10.89
Server Jitter 195.187.245.55 0.000 0.000 0.307 0.724 2.804 6.741 6.741 2.497 6.741 1.037 1.114 ms 2.945 14.1
Server Jitter 213.135.57.60 0.000 0.000 0.374 0.827 2.103 2.528 2.528 1.729 2.528 0.543 0.985 ms 3.987 11.25
Server Jitter SHM(0) 0.000 0.533 0.790 2.029 4.872 6.415 351.928 4.082 5.883 7.403 2.548 ms 30.93 1173
Server Offset 150.254.190.51 -398.556 -398.556 -1.399 0.565 1.514 3.081 3.081 2.913 401.637 61.546 -9.303 ms -11.14 77.11
Server Offset 153.19.250.123 -397.495 -397.495 -1.264 0.369 1.031 1.258 1.258 2.294 398.754 44.477 -4.726 ms -13.39 124.4
Server Offset 193.110.137.171 -1.854 -1.854 -1.271 0.487 1.504 2.403 2.403 2.774 4.257 0.750 0.499 ms -1.687 6.415
Server Offset 194.146.251.100 -399.422 -399.422 -2.629 0.370 1.320 2.254 2.254 3.949 401.675 85.677 -19.047 ms -9.682 50.23
Server Offset 194.146.251.101 -399.351 -399.351 -1.211 0.391 1.316 2.160 2.160 2.527 401.511 86.779 -19.493 ms -9.64 49.53
Server Offset 194.29.130.252 -398.909 -398.909 -2.961 0.646 1.676 2.291 2.291 4.637 401.200 73.906 -13.664 ms -10.22 60.13
Server Offset 195.187.245.55 -399.400 -399.400 -3.018 0.161 1.043 4.073 4.073 4.061 403.473 63.103 -10.170 ms -11.05 74.78
Server Offset 213.135.57.60 -399.675 -399.675 -2.859 0.243 0.984 3.096 3.096 3.843 402.772 74.875 -14.471 ms -10.21 59.49
Server Offset SHM(0) -394.315 0.944 3.790 10.708 18.388 20.242 23.307 14.597 19.298 8.289 11.208 ms -32.2 1506
TDOP 0.620 0.660 0.740 1.120 2.020 3.280 5.140 1.280 2.620 0.488 1.231 11.3 59.12
Temp /dev/sdb 29.000 29.000 29.000 29.000 30.000 30.000 30.000 1.000 1.000 0.322 29.117 °C
Temp LM0 8.000 8.000 9.000 11.000 17.000 18.000 18.000 8.000 10.000 2.105 10.962 °C
Temp LM1 8.000 8.000 8.000 10.000 17.000 17.000 18.000 9.000 9.000 2.179 10.232 °C
Temp LM2 46.000 46.000 46.000 47.000 50.000 50.000 51.000 4.000 4.000 1.164 46.978 °C
Temp LM3 16.000 16.000 16.500 17.500 21.000 21.500 21.500 4.500 5.500 1.229 17.821 °C
Temp LM4 16.000 16.000 16.500 17.500 21.000 21.500 21.500 4.500 5.500 1.260 17.803 °C
nSats 4.000 5.000 6.000 8.000 10.000 11.000 11.000 4.000 6.000 1.283 7.581 nSat 133.1 731.7
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!