Cologne
Germany · DE
22:54:14
Timezone
Europe/Berlin
Offset
GMT+2
Local date
Sat, May 30, 2026
Unix seconds
1780174454
Compare
Quick answer
Frankfurt: 0h (Cologne). Confirm local times, UTC offsets, work-hour status, and date relation on this page. For meetings, start with the shared work window and then open the planner or calendar builder with the same cities and date.
Germany · DE
22:54:14
Timezone
Europe/Berlin
Offset
GMT+2
Local date
Sat, May 30, 2026
Unix seconds
1780174454
Germany · DE
22:54:14
Timezone
Europe/Berlin
Offset
GMT+2
Local date
Sat, May 30, 2026
Unix seconds
1780174454
| City | Local time | UTC offset | Work-hour status | Date relation |
|---|---|---|---|---|
| Cologne | 22:54:14 | GMT+2 | Off hours | same day |
| Frankfurt | 22:54:14 | GMT+2 | Off hours | same day |
Time difference
Frankfurt 0h
Date relation
same day
Next shared work window
from May 31, 07:24 AM, about 540 min
Workday rule
09:00–18:00 local time
Frankfurt: 0h (Cologne). Check UTC offsets and date relation so midnight crossings are not missed.
Next shared work window: from May 31, 07:24 AM, about 540 min. If it is inconvenient, compare fair alternatives in the meeting planner.
Plan meetingAt least one city observes daylight saving time, so future dates can have a different offset than today. Build the final invite after choosing the exact date.
Build calendar linkThe live clocks show local time, offset, date relation, and overlap first. Then hand the same pair to the planner, board, or invite builder.
Offsets are current GMT differences; timezones are named rules that can shift with DST. For future meetings, keep the city timezone and selected instant together.
Same/next/previous day is calculated from each city’s local date, so it catches midnight crossings that a simple hour difference can hide.
DST can change this pair’s offset on another date. Use the meeting planner or calendar builder with a fixed time before sharing.
Workflow handoff
Keep the same cities and selected instant as you move from comparison to planning, board review, and invite creation.
Offset and date relation: Frankfurt ⇄ Cologne, 0h. Date relation.
Open timezone boardShared work window: from May 31, 07:24 AM, about 540 min. Work-hour status.
Open timezone boardCarry both cities into the planner: Cologne / Frankfurt. Date relation.
Plan meetingGoogle Calendar, Outlook, and ICS with named IANA time zones.
Build calendar linkShare this pair with the same context: Cologne / Frankfurt.
Open timezone boardFrankfurt: 0h (Cologne). Current offset and date relation: same day.
Next shared work window: from May 31, 07:24 AM, about 540 min. Use the shared work window first. If it does not fit, compare another instant in the meeting planner.
Cologne ↔ Frankfurt: 0h. has daylight-saving risk on at least one side. Keep both IANA time zones and re-check transition weeks. Europe/Berlin / Europe/Berlin.
Verify the offset and date relation, open the same cities in the meeting planner, then publish Google Calendar, Outlook, and ICS links.