NTPsec

b-ntpsec-5-day-stats

Report generated: Thu Jul 18 02:19:10 2019 UTC
Start Time: Sat Jul 13 02:18:22 2019 UTC
End Time: Thu Jul 18 02:18:22 2019 UTC
Report published: Wed Jul 17 19:21:21 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 -4.744 -0.982 -0.742 -0.007 0.781 1.098 4.194 1.523 2.080 0.475 0.001 µs -3.721 10.56
Local Clock Frequency Offset -6.242 -6.239 -6.179 -5.969 -5.794 -5.784 -5.782 0.385 0.455 0.110 -5.986 ppm -1.691e+05 9.356e+06

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 97.000 131.000 154.000 237.000 449.000 658.000 3,127.000 295.000 527.000 115.643 262.220 ns 11.86 137.4

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 23.000 34.000 41.000 93.000 244.000 611.000 10,663.000 203.000 577.000 226.543 123.199 10e-12 24.65 876.1

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 -4.744 -0.982 -0.742 -0.007 0.781 1.098 4.194 1.523 2.080 0.475 0.001 µs -3.721 10.56

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 -6.242 -6.239 -6.179 -5.969 -5.794 -5.784 -5.782 0.385 0.455 0.110 -5.986 ppm -1.691e+05 9.356e+06
Temp ZONE0 56.382 56.920 57.458 60.686 62.300 63.376 63.914 4.842 6.456 1.441 60.586 °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 9.000 12.000 12.000 12.000 5.000 6.000 1.562 9.309 nSat 136.8 752.5
TDOP 0.510 0.560 0.610 0.860 1.510 1.860 2.980 0.900 1.300 0.300 0.931 17.56 71.48

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

peer offset 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 162.213.2.253 -2.376 -2.176 -1.853 -1.183 -0.756 -0.589 -0.441 1.097 1.587 0.326 -1.222 ms -121.8 657.9

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 169.229.128.134

peer offset 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 169.229.128.134 -4.624 -2.482 -2.239 -1.595 -1.232 -1.048 -0.809 1.007 1.434 0.316 -1.650 ms -260 1762

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 -174.844 -10.876 15.724 99.748 184.155 212.966 291.659 168.431 223.842 56.251 103.437 µs 2.932 6.718

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

peer offset 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 192.168.1.12 -60,753.622 28.375 82.437 146.399 223.110 273.312 1,350.531 140.673 244.937 774.941 144.934 µs -81.2 6406

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 216.218.192.202

peer offset 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 216.218.192.202 -7.720 -2.493 -2.143 -1.542 -1.199 -1.078 -0.839 0.944 1.415 0.344 -1.602 ms -203.1 1404

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 76.14.161.109

peer offset 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Offset 76.14.161.109 -7.902 -7.146 -6.256 -4.915 -3.717 -2.448 -1.219 2.539 4.698 0.812 -4.937 ms -376.1 2814

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) -507.190 -430.829 -416.330 -368.014 -319.733 -300.241 -247.114 96.598 130.588 29.573 -368.695 ms -2483 3.398e+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) -4.745 -0.985 -0.743 -0.008 0.782 1.099 4.195 1.525 2.084 0.477 0.001 µs -3.738 10.64

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

peer jitter 162.213.2.253 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 162.213.2.253 0.000 0.147 0.241 0.676 9.013 12.612 106.154 8.773 12.466 7.710 2.803 ms 8.942 121.8

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 169.229.128.134

peer jitter 169.229.128.134 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 169.229.128.134 0.000 0.170 0.231 0.627 8.843 12.041 115.869 8.611 11.870 5.312 2.528 ms 11.89 255.4

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.017 0.038 0.162 8.637 9.099 181.101 8.599 9.081 4.269 1.322 ms 15.15 529.7

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

peer jitter 192.168.1.12 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 192.168.1.12 0.000 0.020 0.049 0.528 8.728 56.814 294.533 8.679 56.794 10.740 2.814 ms 10.47 235.2

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 216.218.192.202

peer jitter 216.218.192.202 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 216.218.192.202 0.000 0.156 0.223 0.576 8.945 13.927 159.935 8.722 13.771 5.928 2.539 ms 13.57 341.3

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 76.14.161.109

peer jitter 76.14.161.109 plot

Percentiles...... Ranges...... Skew- Kurt-
Name Min1%5%50%95% 99%Max   90%98%StdDev  MeanUnits nessosis
Server Jitter 76.14.161.109 0.000 0.553 1.047 5.008 32.607 49.798 84.302 31.560 49.245 11.055 9.760 ms 1.775 8.031

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 4.590 6.163 11.595 22.994 30.233 80.344 16.831 25.643 5.402 12.738 ms 7.997 28.83

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.000 88.000 117.000 232.000 519.000 789.000 5,351.000 402.000 701.000 155.243 266.293 ns 8.397 129.4

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 -6.242 -6.239 -6.179 -5.969 -5.794 -5.784 -5.782 0.385 0.455 0.110 -5.986 ppm -1.691e+05 9.356e+06
Local Clock Time Offset -4.744 -0.982 -0.742 -0.007 0.781 1.098 4.194 1.523 2.080 0.475 0.001 µs -3.721 10.56
Local RMS Frequency Jitter 23.000 34.000 41.000 93.000 244.000 611.000 10,663.000 203.000 577.000 226.543 123.199 10e-12 24.65 876.1
Local RMS Time Jitter 97.000 131.000 154.000 237.000 449.000 658.000 3,127.000 295.000 527.000 115.643 262.220 ns 11.86 137.4
Server Jitter 162.213.2.253 0.000 0.147 0.241 0.676 9.013 12.612 106.154 8.773 12.466 7.710 2.803 ms 8.942 121.8
Server Jitter 169.229.128.134 0.000 0.170 0.231 0.627 8.843 12.041 115.869 8.611 11.870 5.312 2.528 ms 11.89 255.4
Server Jitter 192.168.1.10 0.000 0.017 0.038 0.162 8.637 9.099 181.101 8.599 9.081 4.269 1.322 ms 15.15 529.7
Server Jitter 192.168.1.12 0.000 0.020 0.049 0.528 8.728 56.814 294.533 8.679 56.794 10.740 2.814 ms 10.47 235.2
Server Jitter 216.218.192.202 0.000 0.156 0.223 0.576 8.945 13.927 159.935 8.722 13.771 5.928 2.539 ms 13.57 341.3
Server Jitter 76.14.161.109 0.000 0.553 1.047 5.008 32.607 49.798 84.302 31.560 49.245 11.055 9.760 ms 1.775 8.031
Server Jitter SHM(0) 0.000 4.590 6.163 11.595 22.994 30.233 80.344 16.831 25.643 5.402 12.738 ms 7.997 28.83
Server Jitter SHM(1) 0.000 88.000 117.000 232.000 519.000 789.000 5,351.000 402.000 701.000 155.243 266.293 ns 8.397 129.4
Server Offset 162.213.2.253 -2.376 -2.176 -1.853 -1.183 -0.756 -0.589 -0.441 1.097 1.587 0.326 -1.222 ms -121.8 657.9
Server Offset 169.229.128.134 -4.624 -2.482 -2.239 -1.595 -1.232 -1.048 -0.809 1.007 1.434 0.316 -1.650 ms -260 1762
Server Offset 192.168.1.10 -174.844 -10.876 15.724 99.748 184.155 212.966 291.659 168.431 223.842 56.251 103.437 µs 2.932 6.718
Server Offset 192.168.1.12 -60,753.622 28.375 82.437 146.399 223.110 273.312 1,350.531 140.673 244.937 774.941 144.934 µs -81.2 6406
Server Offset 216.218.192.202 -7.720 -2.493 -2.143 -1.542 -1.199 -1.078 -0.839 0.944 1.415 0.344 -1.602 ms -203.1 1404
Server Offset 76.14.161.109 -7.902 -7.146 -6.256 -4.915 -3.717 -2.448 -1.219 2.539 4.698 0.812 -4.937 ms -376.1 2814
Server Offset SHM(0) -507.190 -430.829 -416.330 -368.014 -319.733 -300.241 -247.114 96.598 130.588 29.573 -368.695 ms -2483 3.398e+04
Server Offset SHM(1) -4.745 -0.985 -0.743 -0.008 0.782 1.099 4.195 1.525 2.084 0.477 0.001 µs -3.738 10.64
TDOP 0.510 0.560 0.610 0.860 1.510 1.860 2.980 0.900 1.300 0.300 0.931 17.56 71.48
Temp ZONE0 56.382 56.920 57.458 60.686 62.300 63.376 63.914 4.842 6.456 1.441 60.586 °C
nSats 5.000 6.000 7.000 9.000 12.000 12.000 12.000 5.000 6.000 1.562 9.309 nSat 136.8 752.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!