06.1 / NAVIGATION
GPS TIME vs UTC
GPS Time runs continuously; UTC has occasionally inserted leap seconds. Receivers convert between them internally, so modern navigation systems need current leap-second information.
EARTH ROTATION · ATOMIC TIME · UTC · NTP
You asked what time it is. The answer is more complicated than it looks.
PRECISION TIME CONSOLE / 01 NOW
LOCAL OSC · DEVICE CLOCK
TIMEZONE — · UTC OFFSET —
This display uses the time reported by your device. Time Observer does not measure your device’s actual offset from UTC. Scientific reference values are authoritative World Observer snapshots, not a claim about this browser’s synchronization.
02 / FOLLOW THE SECOND
This is a conceptual chain of definition, realization and distribution—not one literal “second packet” travelling to your browser.
STAGE 01
The SI second is defined using a specified cesium-133 hyperfine transition.
03 / EARTH IS NOT A CLOCK
Atomic time is regular. UT1 tracks Earth’s rotational angle, which varies with atmosphere, oceans, mass redistribution and long-term rotational change.
VISUAL SCALE: EXAGGERATED FOR CLARITY — the traces are not geometrically proportional.
REAL OFFSET: DATA UNAVAILABLE
SCIENTIFIC REFERENCE DATA UNAVAILABLE
Earth-orientation services publish predictions because navigation, astronomy and timing systems need values beyond the latest observation.
04 / TIME MACHINE
UTC already differed from TAI by 10 seconds when the modern leap-second system began in 1972. Subsequent increases represent positive leap-second adjustments.
05 / NTP JOURNEY
Stratum is distance from a reference clock, not a simple quality or accuracy score.
EDUCATIONAL SIMULATION
EDUCATIONAL SIMULATION · NO NETWORK REQUEST · DOES NOT MEASURE YOUR CLOCK.
delay = (T4 − T1) − (T3 − T2) · offset = ((T2 − T1) + (T3 − T4)) / 2
06 / COMPACT FIELD GUIDES
Six short exhibits connect the reference timescale to navigation, networks and everyday infrastructure.
06.1 / NAVIGATION
GPS Time runs continuously; UTC has occasionally inserted leap seconds. Receivers convert between them internally, so modern navigation systems need current leap-second information.
06.2 / SYNCHRONIZATION PATH
This is one typical example only. Configurations, providers and actual synchronization paths vary.
06.3 / PROTOCOLS
Both synchronize clocks, but they target different environments and precision needs.
06.4 / HISTORY
Travel, communication and computing outgrew town-by-town solar time. A worldwide shared reference lets distant systems agree on when events happen.
06.5 / CIVIL TIME
Atomic clocks are extremely stable; Earth’s rotation is not perfectly constant. Modern civil time therefore considers both.
UTC uses the atomic second and has historically used leap seconds to remain close to observed Earth rotation.
06.6 / APPLICATIONS
Accurate shared timestamps establish order, coordinate systems and make records trustworthy.
07 / SOURCE / METHOD
Earth rotation and UT1−UTC.
International atomic time and UTC coordination context.
National metrology, realization and distribution context.
The NTP protocol specification.
Published World Observer snapshot provenance will appear when data is available.