UTC-03:30
UTC-03:30 means UTC−03:30 throughout the year.
Convert Philadelphia, United States to UTC-03:30. Compare dates, seasonal differences and meeting hours.
Philadelphia is 30m or 1h 30m behind UTC-03:30 in 2026, depending on the date.
9 AM Philadelphia = 10:30 AM UTC-03:30
Selected date: November 4, 2026. Fixed abbreviations retain their stated UTC offsets.
November 4, 2026 · Date changes are marked.
| Philadelphia | UTC-03:30 |
|---|---|
| 12:00 AM | 1:30 AM |
| 1:00 AM | 2:30 AM |
| 2:00 AM | 3:30 AM |
| 3:00 AM | 4:30 AM |
| 4:00 AM | 5:30 AM |
| 5:00 AM | 6:30 AM |
| 6:00 AM | 7:30 AM |
| 7:00 AM | 8:30 AM |
| 8:00 AM | 9:30 AM |
| 9:00 AM | 10:30 AM |
| 10:00 AM | 11:30 AM |
| 11:00 AM | 12:30 PM |
| Philadelphia | UTC-03:30 |
|---|---|
| 12:00 PM | 1:30 PM |
| 1:00 PM | 2:30 PM |
| 2:00 PM | 3:30 PM |
| 3:00 PM | 4:30 PM |
| 4:00 PM | 5:30 PM |
| 5:00 PM | 6:30 PM |
| 6:00 PM | 7:30 PM |
| 7:00 PM | 8:30 PM |
| 8:00 PM | 9:30 PM |
| 9:00 PM | 10:30 PM |
| 10:00 PM | 11:30 PM |
| 11:00 PM | 12:30 AM +1 day |
These examples start on 2026-11-04 in UTC-03:30.
UTC-03:30 means UTC−03:30 throughout the year.
Keeping 09:00 on the Philadelphia clock produces 2 different destination clock/date answers in 2026. The ranges below use Philadelphia calendar dates, including transition days.
| Dates in Philadelphia · 2026 | UTC-03:30 answer | Source → destination offsets | Explore |
|---|---|---|---|
| Jan 1 – Mar 766 dates | 10:30Same date | UTC−05:00 → UTC−03:30 | |
| Mar 8 – Oct 31238 dates | 09:30Same date | UTC−04:00 → UTC−03:30 | |
| Nov 1 – Dec 3161 dates | 10:30Same date | UTC−05:00 → UTC−03:30 |
Every calendar date is included, not just workdays. Date ranges include both endpoints. Based on IANA 2026e; future rules may change.
Your complete source day: 2026-11-04. Each range shows which destination date to use.
Range starts are included; ends are excluded. 24:00 means midnight at the end of that date. Repeated hours appear separately with their UTC offsets. The strip is proportional to elapsed time.
How UTC-03:30 compares with Philadelphia throughout 2026.
Philadelphia changes its UTC offset in 2026. UTC-03:30 is a fixed offset.
| From (UTC, inclusive) | Until (UTC, exclusive) | UTC-03:30 vs Philadelphia |
|---|---|---|
| 1 Jan 2026, 00:00 UTC | 8 Mar 2026, 07:00 UTC | 1h 30m ahead |
| 8 Mar 2026, 07:00 UTC | 1 Nov 2026, 06:00 UTC | 30m ahead |
| 1 Nov 2026, 06:00 UTC | 1 Jan 2027, 00:00 UTC | 1h 30m ahead |
The most frequent difference has UTC-03:30 30m ahead relative to Philadelphia. Exceptions:
| From (UTC, inclusive) | Until (UTC, exclusive) | Compared with Philadelphia |
|---|---|---|
| 1 Jan 2026, 00:00 UTC | 8 Mar 2026, 07:00 UTC | 1h 30m ahead |
| 1 Nov 2026, 06:00 UTC | 1 Jan 2027, 00:00 UTC | 1h 30m ahead |
Every date calculated with your working windows. 261 selected Philadelphia workdays; public holidays are not applied.
Start a 60-minute meeting in Philadelphia 09:00–14:30.
These starts fit both working windows on every selected Philadelphia workday in 2026, using a 15-minute start grid. The end of each range is the last valid start.
Philadelphia: 09:00–17:00, Mon, Tue, Wed, Thu, Fri. UTC-03:30: 09:00–17:00, Mon, Tue, Wed, Thu, Fri.
Overnight shifts belong to their start weekday. Host workday means the source calendar date. Repeated local times use the first occurrence.
Philadelphia is 30m or 1h 30m behind UTC-03:30 in 2026, depending on the date. Philadelphia changes its UTC offset in 2026. UTC-03:30 is a fixed offset.
The published rules produce 3 periods with 2 different offsets in 2026. See the annual chart for the exact boundaries of each period.
09:00 in Philadelphia on 2026-11-04 is 10:30 in UTC-03:30 on 2026-11-04. This selected time stays on the same date in both places. Other times can cross midnight.
Your selected working windows share 6h 30m on 2026-11-04. The planner above checks the whole meeting duration and shows suitable start times. Edit the windows to match your team.