NTPsec

c-ntpsec-5-day-stats

Report generated: Thu Jul 18 02:22:07 2019 UTC
Start Time: Sat Jul 13 02:21:22 2019 UTC
End Time: Thu Jul 18 02:21:22 2019 UTC
Report published: Wed Jul 17 19:24:32 2019 PDT
Report Period: 5.0 days
Warning: plots clipped

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 -3.032 -1.540 -1.004 0.056 1.071 1.590 11.036 2.075 3.130 0.675 0.045 µs -2.865 16.46
Local Clock Frequency Offset -8.590 -8.527 -8.475 -8.384 -8.291 -8.279 -8.272 0.184 0.248 0.051 -8.382 ppm -4.538e+06 7.514e+08

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 82.000 125.000 143.000 215.000 450.000 641.000 1,724.000 307.000 516.000 106.500 243.119 ns 9.061 50.53

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 15.000 25.000 33.000 83.000 295.000 481.000 5,323.000 262.000 456.000 197.708 120.403 10e-12 15.02 333

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 -3.032 -1.540 -1.004 0.056 1.071 1.590 11.036 2.075 3.130 0.675 0.045 µs -2.865 16.46

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 -8.590 -8.527 -8.475 -8.384 -8.291 -8.279 -8.272 0.184 0.248 0.051 -8.382 ppm -4.538e+06 7.514e+08
Temp ZONE0 57.458 57.996 59.072 60.148 62.300 62.300 62.838 3.228 4.304 0.883 60.309 °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 6.000 7.000 10.000 12.000 12.000 13.000 5.000 6.000 1.482 9.633 nSat 182.6 1094
TDOP 0.490 0.590 0.610 0.800 1.430 1.770 3.030 0.820 1.180 0.264 0.880 21.64 90.5

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

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 162.159.200.1

peer offset 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.159.200.1 -14.955 -5.325 -4.634 -1.989 -1.019 0.324 1.855 3.616 5.649 1.280 -2.229 ms -32.87 183.1

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 164.67.62.194

peer offset 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 164.67.62.194 -5.798 -3.542 -3.110 -2.136 -1.477 -1.228 -0.006 1.632 2.314 0.553 -2.221 ms -141.8 796.8

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 173.11.101.155

peer offset 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 173.11.101.155 -10.693 -7.015 -6.340 -5.415 -4.708 -4.368 -3.887 1.632 2.647 0.538 -5.456 ms -1417 1.622e+04

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 192.168.1.10

peer offset 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.10 -13,154.576 -81.873 -53.617 13.705 74.268 149.038 1,515.401 127.885 230.911 220.084 10.564 µs -60.47 3623

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 192.168.1.11

peer offset 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.11 -714.780 -94.278 -69.390 -8.797 68.692 123.225 295.490 138.082 217.503 44.331 -4.747 µs -6.143 50.17

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 204.123.2.5

peer offset 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 204.123.2.5 -2.259 -2.020 -1.765 -1.246 -0.880 -0.777 -0.588 0.885 1.243 0.273 -1.280 ms -201.7 1255

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) -91.242 -72.854 -69.848 -59.400 -50.025 -46.651 -42.032 19.823 26.203 6.080 -59.540 ms -1290 1.428e+04

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(1)

peer offset SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset SHM(1) -3.033 -1.541 -1.005 0.057 1.072 1.591 11.037 2.077 3.132 0.676 0.045 µs -2.868 16.42

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 162.159.200.1

peer jitter 162.159.200.1 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.159.200.1 0.201 0.414 0.564 1.335 7.045 20.020 118.902 6.482 19.606 6.669 2.724 ms 8.221 104.9

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 164.67.62.194

peer jitter 164.67.62.194 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 164.67.62.194 0.120 0.315 0.501 1.349 8.260 16.174 106.958 7.759 15.860 5.335 2.615 ms 11.43 205.9

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 173.11.101.155

peer jitter 173.11.101.155 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 173.11.101.155 0.360 0.564 0.907 2.023 7.284 24.651 57.775 6.376 24.088 4.631 3.091 ms 6.747 67.9

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 192.168.1.10

peer jitter 192.168.1.10 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.10 0.000 0.029 0.073 0.531 6.477 16.413 80.329 6.404 16.383 5.823 1.796 ms 6.352 66.71

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 192.168.1.11

peer jitter 192.168.1.11 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.11 0.000 0.028 0.068 0.519 6.133 56.456 246.558 6.065 56.428 9.557 2.086 ms 11.75 248

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 204.123.2.5

peer jitter 204.123.2.5 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 204.123.2.5 0.169 0.308 0.438 1.249 8.044 19.473 57.617 7.606 19.165 4.998 2.572 ms 6.237 65.86

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.116 0.413 0.581 1.406 3.919 6.724 21.977 3.338 6.311 1.228 1.755 ms 3.828 18.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 SHM(1)

peer jitter SHM(1) plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter SHM(1) 0.031 0.084 0.122 0.309 0.752 1.063 4.436 0.630 0.979 0.229 0.361 µs 5.595 54.39

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 -8.590 -8.527 -8.475 -8.384 -8.291 -8.279 -8.272 0.184 0.248 0.051 -8.382 ppm -4.538e+06 7.514e+08
Local Clock Time Offset -3.032 -1.540 -1.004 0.056 1.071 1.590 11.036 2.075 3.130 0.675 0.045 µs -2.865 16.46
Local RMS Frequency Jitter 15.000 25.000 33.000 83.000 295.000 481.000 5,323.000 262.000 456.000 197.708 120.403 10e-12 15.02 333
Local RMS Time Jitter 82.000 125.000 143.000 215.000 450.000 641.000 1,724.000 307.000 516.000 106.500 243.119 ns 9.061 50.53
Server Jitter 162.159.200.1 0.201 0.414 0.564 1.335 7.045 20.020 118.902 6.482 19.606 6.669 2.724 ms 8.221 104.9
Server Jitter 164.67.62.194 0.120 0.315 0.501 1.349 8.260 16.174 106.958 7.759 15.860 5.335 2.615 ms 11.43 205.9
Server Jitter 173.11.101.155 0.360 0.564 0.907 2.023 7.284 24.651 57.775 6.376 24.088 4.631 3.091 ms 6.747 67.9
Server Jitter 192.168.1.10 0.000 0.029 0.073 0.531 6.477 16.413 80.329 6.404 16.383 5.823 1.796 ms 6.352 66.71
Server Jitter 192.168.1.11 0.000 0.028 0.068 0.519 6.133 56.456 246.558 6.065 56.428 9.557 2.086 ms 11.75 248
Server Jitter 204.123.2.5 0.169 0.308 0.438 1.249 8.044 19.473 57.617 7.606 19.165 4.998 2.572 ms 6.237 65.86
Server Jitter SHM(0) 0.116 0.413 0.581 1.406 3.919 6.724 21.977 3.338 6.311 1.228 1.755 ms 3.828 18.49
Server Jitter SHM(1) 0.031 0.084 0.122 0.309 0.752 1.063 4.436 0.630 0.979 0.229 0.361 µs 5.595 54.39
Server Offset 162.159.200.1 -14.955 -5.325 -4.634 -1.989 -1.019 0.324 1.855 3.616 5.649 1.280 -2.229 ms -32.87 183.1
Server Offset 164.67.62.194 -5.798 -3.542 -3.110 -2.136 -1.477 -1.228 -0.006 1.632 2.314 0.553 -2.221 ms -141.8 796.8
Server Offset 173.11.101.155 -10.693 -7.015 -6.340 -5.415 -4.708 -4.368 -3.887 1.632 2.647 0.538 -5.456 ms -1417 1.622e+04
Server Offset 192.168.1.10 -13,154.576 -81.873 -53.617 13.705 74.268 149.038 1,515.401 127.885 230.911 220.084 10.564 µs -60.47 3623
Server Offset 192.168.1.11 -714.780 -94.278 -69.390 -8.797 68.692 123.225 295.490 138.082 217.503 44.331 -4.747 µs -6.143 50.17
Server Offset 204.123.2.5 -2.259 -2.020 -1.765 -1.246 -0.880 -0.777 -0.588 0.885 1.243 0.273 -1.280 ms -201.7 1255
Server Offset SHM(0) -91.242 -72.854 -69.848 -59.400 -50.025 -46.651 -42.032 19.823 26.203 6.080 -59.540 ms -1290 1.428e+04
Server Offset SHM(1) -3.033 -1.541 -1.005 0.057 1.072 1.591 11.037 2.077 3.132 0.676 0.045 µs -2.868 16.42
TDOP 0.490 0.590 0.610 0.800 1.430 1.770 3.030 0.820 1.180 0.264 0.880 21.64 90.5
Temp ZONE0 57.458 57.996 59.072 60.148 62.300 62.300 62.838 3.228 4.304 0.883 60.309 °C
nSats 5.000 6.000 7.000 10.000 12.000 12.000 13.000 5.000 6.000 1.482 9.633 nSat 182.6 1094
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!