tick

Report generated: Tue Oct 14 10:15:13 2025 UTC
Start Time: Tue Oct 7 10:15:11 2025 UTC
End Time: Tue Oct 14 10:15:11 2025 UTC
Report Period: 7.0 days

Local Clock Time/Frequency Offsets

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Local Clock Time Offset	-6.795	-2.028	-1.284	0.036	1.309	1.897	4.568	2.593	3.925	0.808	0.022	µs	-4.119	12.31
Local Clock Frequency Offset	-36.925	-36.912	-36.875	-36.777	-36.666	-36.657	-36.639	0.209	0.256	0.066	-36.771	ppm	-1.726e+08	9.607e+10

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

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Local RMS Time Jitter	175.000	287.000	330.000	465.000	679.000	877.000	3,038.000	349.000	590.000	138.182	484.354	ns	27.66	170.1

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

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Local RMS Frequency Jitter	55.000	73.000	87.000	151.000	376.000	814.000	2,551.000	289.000	741.000	139.841	187.728	10e-12	6.195	54.33

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

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Local Clock Offset	-6.795	-2.028	-1.284	0.036	1.309	1.897	4.568	2.593	3.925	0.808	0.022	µs	-4.119	12.31

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 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

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Local Clock Frequency Offset	-36.925	-36.912	-36.875	-36.777	-36.666	-36.657	-36.639	0.209	0.256	0.066	-36.771	ppm	-1.726e+08	9.607e+10
Temp ZONE0	52.996	52.996	52.996	54.072	55.148	55.686	56.224	2.152	2.690	0.651	54.256	°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

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
nSats	0.000	8.000	8.000	10.000	11.000	12.000	12.000	3.000	4.000	1.057	9.625	nSat	556.8	4715
TDOP	0.470	0.540	0.590	0.820	1.170	1.330	3.090	0.580	0.790	0.178	0.848		65.5	306.7

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. TDOP ranges from 1 to greater than 20. 1 denotes the highest possible confidence level. 2 to 5 is good. Greater than 20 means there will be significant inaccuracy and error.

Server Offsets

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

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Server Offset PPS(0)	-6.796	-2.029	-1.285	0.037	1.310	1.898	4.569	2.595	3.927	0.808	0.022	µs	-4.118	12.3

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)

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Server Offset SHM(0)	-12.721	135.589	139.931	153.579	165.286	168.883	176.579	25.355	33.294	7.606	153.256	ms	7080	1.367e+05

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

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

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

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Server Jitter PPS(0)	0.060	0.173	0.235	0.490	1.030	1.410	6.011	0.795	1.237	0.271	0.543	µs	6.751	43.93

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)

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Server Jitter SHM(0)	0.677	2.977	4.046	7.487	13.871	17.230	172.142	9.825	14.253	3.068	8.034	ms	10.7	67.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.

Summary

	Percentiles......							Ranges......					Skew-	Kurt-
Name	Min	1%	5%	50%	95%	99%	Max	90%	98%	StdDev	Mean	Units	ness	osis
Local Clock Frequency Offset	-36.925	-36.912	-36.875	-36.777	-36.666	-36.657	-36.639	0.209	0.256	0.066	-36.771	ppm	-1.726e+08	9.607e+10
Local Clock Time Offset	-6.795	-2.028	-1.284	0.036	1.309	1.897	4.568	2.593	3.925	0.808	0.022	µs	-4.119	12.31
Local RMS Frequency Jitter	55.000	73.000	87.000	151.000	376.000	814.000	2,551.000	289.000	741.000	139.841	187.728	10e-12	6.195	54.33
Local RMS Time Jitter	175.000	287.000	330.000	465.000	679.000	877.000	3,038.000	349.000	590.000	138.182	484.354	ns	27.66	170.1
Server Jitter PPS(0)	0.060	0.173	0.235	0.490	1.030	1.410	6.011	0.795	1.237	0.271	0.543	µs	6.751	43.93
Server Jitter SHM(0)	0.677	2.977	4.046	7.487	13.871	17.230	172.142	9.825	14.253	3.068	8.034	ms	10.7	67.01
Server Offset PPS(0)	-6.796	-2.029	-1.285	0.037	1.310	1.898	4.569	2.595	3.927	0.808	0.022	µs	-4.118	12.3
Server Offset SHM(0)	-12.721	135.589	139.931	153.579	165.286	168.883	176.579	25.355	33.294	7.606	153.256	ms	7080	1.367e+05
TDOP	0.470	0.540	0.590	0.820	1.170	1.330	3.090	0.580	0.790	0.178	0.848		65.5	306.7
Temp ZONE0	52.996	52.996	52.996	54.072	55.148	55.686	56.224	2.152	2.690	0.651	54.256	°C
nSats	0.000	8.000	8.000	10.000	11.000	12.000	12.000	3.000	4.000	1.057	9.625	nSat	556.8	4715

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 = (∑x_i) / N". Where x_i 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: "σ = √[ ∑(x_i-mu)^2 / N ]". Where x_i 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