Madrid has two occurrences of 02:30 on 25 October 2026: the first is 00:30 UTC, and the second is 01:30 UTC.
Two instants with the same written clock time
When the clock goes back, it repeats a stretch already elapsed. The first 02:30 in Madrid uses UTC+02:00; the second uses UTC+01:00. Those similar clock readings represent appointments one real hour apart.
How the converter handles it
Choose Madrid, 25 October 2026 and 02:30. A selector lets you choose the first or second occurrence. The result and event file use that selected instant. The repeated hour in London and the Canary Islands is 01:00, not Madrid’s 02:00.
The opposite happens in spring
Moving forwards skips local clock readings. Madrid has no 02:30 on 29 March 2026. The tool flags the missing time and asks you to choose another; it does not silently shift an appointment into a different hour.
What to write for a night-time appointment
State the city, date and UTC offset, or share a calendar event that represents a specific instant. If an external service cannot select occurrences, confirm the UTC time with the organiser.
Try the two occurrences of 02:30 →
Common questions
Are both occurrences the same moment?
No. Madrid’s two occurrences of 02:30 on 25 October 2026 are one real hour apart.
What does the converter select by default?
The first occurrence. Select the second before copying or downloading if that is the intended instant.
Sources and calculation
Tables are calculated using named IANA zones with Intl. Read the method, scope and limitations.