Skip to main content
WizTools123
Free Online Tools

Tool Categories


Date & Time Tools New Tool

Free Online Daylight Saving Time Checker and Clock Change Finder

Find the exact moment the clocks change in any time zone, in any year, with the offsets on either side and the hour that is skipped or repeated. The page also checks whether a particular date and time actually exists in that place, which is the question behind a surprising number of bugs.

Free Forever Nothing Uploaded The Exact Minute Missing Hour Named
Free Online Daylight Saving Time Checker and Clock Change Finder
Share this tool
Advertisement Slot (Top Banner) Google AdSense Unit • Responsive Banner
☀️ Daylight Saving and Clock Changes The exact moment · the lost hour · and whether a time is real

Every date is worked out in your browser. Nothing you type is sent anywhere.

☀️ Which question?

The rules change from time to time, so a year in the past is answered with the rules that applied then, not with today.
Try one of these
The clocks change
—
Clocks go forward—
Clocks go back—
The hour that never happens—
The hour that happens twice—
Right now there—

Each change, with the offsets on either side.

What happens The exact moment there Offsets, and what it means
Year Clocks go forward Clocks go back
Buy Us A Coffee

Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.

Buy Us A Coffee
Sponsored Content (Below Tool) Google AdSense Placement

How to Use DST Checker

Step by step, start to finish.

1

From the full list of time zones your browser already carries. Nothing is downloaded, and no rule is written into this page, so a country that has changed or abandoned its clock changes is answered correctly rather than from a table that went stale.

2

A year gives both changes with the exact minute they happen, the offsets on either side and which hour is lost or repeated. A single date and time answers a narrower question: does that time exist in that place at all.

3

In spring an hour never happens, so a time inside it is not a real moment. In autumn an hour happens twice, so a time inside it is two moments. Both are named outright, because these are the two cases that quietly break schedules, bookings and logs.

Key Features

What this tool does, and what it does not do.

The exact moment

Not the rule, but the minute the clocks move, found from the zone data itself.

The missing hour named

The local times that never happen in spring, which is where stored times go wrong.

The repeated hour named

The local times that happen twice in autumn, with both instants in UTC.

Test a single time

Whether one date and time exists in that place, happens twice, or is ordinary.

The coming years

The next several years of changes in one table, so a schedule can be planned around them.

Nothing is uploaded

It runs in this tab and keeps working offline.

About DST Checker

Daylight saving time moves the clock forward in spring and back in autumn so that the long evenings fall where people are awake. The idea is simple and the consequences are not, because moving a clock does not move time: it changes the relationship between a local time and the actual instant it names. Twice a year, for one hour, that relationship breaks down completely, and almost every awkward bug involving dates lives in those two hours.

Going forward is the cleaner of the two and the stranger. If the clocks jump from one in the morning to two, then every local time in that hour never occurs. A meeting at half past one on that date is not a time at all. Anything already stored at such a time has to be moved, and different pieces of software move it differently, which is how a single appointment ends up at two different instants in two different systems.

Going back is messier. The same local hour comes round a second time, so half past one names two instants roughly an hour apart. A log sorted by local time comes out in the wrong order, a job that runs at a fixed local time runs twice, and a daily total for that date covers twenty five hours. None of this announces itself: the figures are simply wrong once a year, in one direction, for one day.

The rules themselves are set country by country and change more often than people expect. Europe moves on the last Sunday of March and October, North America on the second Sunday of March and the first of November, the southern hemisphere runs the opposite way round, and a long list of countries have abandoned the practice, some of them recently. Rather than carry a table of rules that would quietly go out of date, this page reads the actual offsets out of the time zone data your own browser already holds, and finds the change by looking for the minute at which the offset moves.

Frequently Asked Questions

Common questions about this tool.

Pick the place and the year and both changes are shown with the exact minute, the offsets on either side and the hour that is lost or repeated.

The hour between the old and the new time, named for the place you choose. In most of Europe it is one in the morning to two, in North America two to three.

It is not a real moment, so something has to be chosen for it. Different systems choose differently, which is why a local time without a zone is a weak thing to store.

The hour that is repeated when the clocks go back. A time inside it names two instants about an hour apart, and both are shown here in UTC.

No. India, Pakistan, China, Japan, most of Africa and parts of the United States such as Arizona keep one offset all year, and several countries have stopped in recent years.

No. Lord Howe Island moves by half an hour, and historical changes have been other amounts. This page reads the real offsets rather than assuming.

No. The zone data comes from your own browser, so nothing is sent anywhere and it keeps working offline.
Advertisement Slot (Bottom Banner) Google AdSense Unit • Responsive Banner