Solar Time vs Clock Time

After reading this you can work out, for any spot on Earth, how many minutes your clock differs from the sun, and explain why the gap is sometimes over three hours.

The sun does not read your government's legislation. It crosses the sky at a rate set by the Earth's rotation, and true noon happens when the sun is highest in your local sky. Clock time is a different thing entirely: it is a political choice, a fixed offset from UTC applied to a whole region so trains and meetings can share a schedule. The two rarely agree.

Take western Spain. A Isla in Galicia sits near 8.9^\circ west, so its solar noon comes late relative to Greenwich. Yet Spain runs on Central European Time (UTC+1), the same clock as Warsaw. In summer, with daylight saving added, the sun reaches its highest point there close to 14:30 on the clock. Your watch says early afternoon while the sun says midday. That two and a half hour illusion is the subject of this tool.

What the tool shows and one hook example

The map draws 24 ideal time bands, each 15 degrees of longitude wide. Those bands are what clocks would follow if time zones matched the sun exactly. Click anywhere and you get two numbers: the solar time (driven only by longitude and the date) and the clock time (the UTC offset actually used at that spot). The difference is the gap.

The most extreme case is the far west of China. Kashgar sits near 76^\circ east, where the sun peaks around solar noon at a longitude that "wants" roughly UTC+5. But all of China uses a single zone, UTC+8. That is three zones east of where Kashgar's sun lives, so the clock runs about three hours ahead of the sun. Government offices there sometimes open at 10:00 clock time, which is closer to 07:00 by the sun.

When to use it, and when not

Use this tool to reason about human schedules against daylight: why sunrise in one city feels absurdly late, whether a "9 to 5" is really an 11 to 7 by the sun, or how far a country has stretched a single zone. It is a good companion when you plan photography, study energy-use patterns tied to daylight, or just want to explain to a friend why Spanish dinner starts at 22:00.

Do not use it for astronomy that needs the sun's altitude or azimuth. Solar time tells you when the sun is highest, not how high. The peak altitude depends on latitude and season, which this tool does not compute. For the day and night boundary across the whole globe, use the Day & Night World Map instead.

Solar time here means mean local solar time adjusted by the equation of time to give apparent solar time, which is what a sundial reads. The tool corrects for both longitude and the seasonal wobble, so its noon matches a real sundial to within a few seconds.

The formula and the intuition behind it

Start with the clean part. The Earth turns 360 degrees in 24 hours, so it turns 15 degrees per hour, or 1 degree every 4 minutes. That single fact drives everything.

\Delta t_{\text{lon}} = 4 \times (\lambda - \lambda_{\text{zone}})

Here \Delta t_{\text{lon}} is the longitude part of the gap in minutes, \lambda is your longitude in degrees (east positive, west negative), and \lambda_{\text{zone}} is the reference meridian of your clock, which is 15^\circ times the UTC offset in hours. A positive result means your clock is ahead of the sun.

Now add the wobble. The Earth's orbit is slightly elliptical and its axis is tilted, so apparent solar time drifts ahead of and behind mean solar time over the year. This is the equation of time, written E, measured in minutes.

\Delta t = 4 \times (\lambda - \lambda_{\text{zone}}) - E + 60 \times D

The term D is 1 when daylight saving is in force at that location and 0 otherwise, adding a full hour to the gap. The equation of time E ranges from about -14 minutes in mid February to about +16 minutes in early November. A common closed form is:

E \approx 9.87 \sin(2B) - 7.53 \cos(B) - 1.5 \sin(B)

where B = \frac{360}{365}(N - 81) in degrees and N is the day of the year (1 to 365). The number 81 anchors the formula near the March equinox.

The equation of time swings from about -14 minutes in February to about +16 minutes in early November, crossing zero four times a year.

A worked example reproducing the demo

Madrid on the default date

The demo uses field defaults, which drop you near Madrid at \lambda = -3.7^\circ (west) on a summer day, day of year N = 172 (about June 21). Spain uses UTC+1 as its base and observes daylight saving in summer, so effectively UTC+2.

  1. Zone reference meridian for UTC+1: \lambda_{\text{zone}} = 15 \times 1 = 15^\circ east. (Use the base offset, not the DST offset; DST is the separate D term.)
  2. Longitude gap: 4 \times (-3.7 - 15) = 4 \times (-18.7) = -74.8 minutes.
  3. Equation of time: with B = \frac{360}{365}(172 - 81) = 89.8^\circ, you get E \approx 9.87 \sin(179.6^\circ) - 7.53 \cos(89.8^\circ) - 1.5 \sin(89.8^\circ) \approx -1.5 minutes.
  4. Daylight saving: D = 1, adding 60 minutes.
  5. Total gap: \Delta t = -74.8 - (-1.5) + 60 = -13.3 minutes.

The negative sign means the clock is about 13 minutes behind the sun at Madrid in June. That surprises people who expect Spain to always run ahead. The reason is that Madrid sits west inside its zone, and that -74.8 minute longitude penalty nearly cancels the +60 minute DST boost. Move to Galicia at -8.9^\circ and the longitude term becomes 4 \times (-23.9) = -95.6, so the clock there runs about 34 minutes behind the sun in summer, and well over 90 minutes ahead in winter once you undo DST and compare against the wrong zone.

Reading and interpreting the gap

A positive gap means your clock is ahead of the sun: solar noon lands after 12:00, sunrise and sunset feel late. A negative gap means the clock lags the sun: noon comes early. The size tells you how far your region stretched or shifted its zone.

Typical clock-ahead-of-sun gaps at solar noon (winter, no DST)
PlaceLongitudeZoneZone meridianGap (min)
Kashgar, China76.0 EUTC+8120 E+176
Vigo, Spain8.7 WUTC+115 E+95
Nome, Alaska165.4 WUTC-9135 W+122
Greenwich0.0UTC+000

Check Kashgar: 4 \times (120 - 76) = 176 minutes, so the clock runs almost three hours ahead of the sun. Nome: 4 \times (135 - 165.4) = -121.6, so the clock is about two hours behind the sun, meaning very early solar noon. Greenwich on its own reference meridian shows a gap of zero longitude, with only the small equation of time term left over.

Without JavaScript: pick a longitude and a UTC offset, and compute the gap as 4 times (longitude minus 15 times the offset) minutes, then add 60 if daylight saving applies. Positive means the clock is ahead of the sun.

Common mistakes

The gap looks simple, but four errors show up again and again.

Do not use the DST offset as the zone reference meridian. Spain in summer is UTC+2 on the wall, but its zone is UTC+1. Feed 15 degrees, not 30, into the longitude term, then add the DST hour separately. Mixing these double-counts the DST shift.

Second, sign confusion. West longitude is negative and pushes solar noon later, so the clock runs behind the sun in the western part of a zone. Getting the sign backward flips your whole interpretation.

Third, forgetting the equation of time. On its own it is small, at most 16 minutes, but it is why a sundial and a clock disagree even on the exact reference meridian. If your computed solar noon is off by ten to fifteen minutes and you cannot explain it, you probably dropped the E term.

Fourth, assuming every country picked a sensible zone. Many did not. China spans about 60 degrees of longitude on one clock. India uses a half-hour offset (UTC+5:30) precisely so its single zone splits the difference across the subcontinent. Always read the actual offset in use, not the one the longitude suggests.

Related tools

If you want to feed exact coordinates or convert between formats before clicking the map, the Coordinate Converter handles decimal degrees, DMS and more. To see the daylight boundary itself sweep across the globe, use the Day & Night World Map. Curious where you land on the far side of the Earth, and what solar time it is there? The Antipode Finder takes any click and shows the opposite point. And if you have your own point data to plot, the GeoJSON & CSV Map Viewer puts a file straight on a map.

Frequently asked questions

Why is solar noon not at 12:00 on my clock?

Because your longitude almost never equals your zone's reference meridian, and daylight saving may add an hour. Every degree you sit west of that meridian delays solar noon by 4 minutes. The equation of time adds up to 16 minutes either way.

Does latitude affect solar time?

No. Solar time depends only on longitude and the date. Latitude changes how high the sun climbs and how long the day is, but the moment of solar noon is set purely by where you are east to west.

What is the biggest clock-vs-sun gap on Earth?

The far west of China, near Kashgar, runs about three hours ahead of the sun because the whole country uses UTC+8. Western Spain and parts of France also exceed 90 minutes ahead in summer once DST is included.

Why does the equation of time exist at all?

Two causes. The Earth's orbit is elliptical, so it moves faster near the sun in January and slower in July, and the axis tilts 23.4 degrees. Together they make apparent solar days slightly longer or shorter than 24 clock hours, and the small daily differences accumulate into a swing of about 31 minutes across the year.

Is the tool computing anything on a server?

No. Everything runs in your browser. The map, the longitude math and the equation of time are all local, so nothing about where you click leaves your device.