Explore · time zones
Tehran to Buenos Aires converter
Iran Time (Tehran) → Argentina Time (Buenos Aires)
Quick answer
Buenos Aires is 6 hours 30 minutes behind Tehran all year. Neither zone changes its offset relative to the other.
9:00 AM UTC+3:30 in Tehran is 2:30 AM UTC−3 in Buenos Aires, the same day. Buenos Aires is 6 h 30 min behind Tehran.
| Format | Result | Copy |
|---|---|---|
| Buenos AiresWednesday, January 14, 2026 · the same day | 2: | |
| ISO 8601UTC | 2026- | |
| Unix seconds | 1768368600 | |
| RFC 2822UTC | Wed, |
Conversions use Tehran (Asia/Tehran) and Buenos Aires (America/Argentina/Buenos_Aires). Other cities reached through search aliases may have different historical rules.
Current time in Tehran and Buenos Aires
Hour by hour: Tehran (UTC+3:30) → Buenos Aires (UTC−3)
Both sides are inside 9:00–17:00 from 3:30 PM to 5:00 PM UTC+3:30 in Tehran (1 hour 30 minutes).
| Tehran | Buenos Aires | Day |
|---|---|---|
| 12:00 AM | 5:30 PM | previous day |
| 1:00 AM | 6:30 PM | previous day |
| 2:00 AM | 7:30 PM | previous day |
| 3:00 AM | 8:30 PM | previous day |
| 4:00 AM | 9:30 PM | previous day |
| 5:00 AM | 10:30 PM | previous day |
| 6:00 AM | 11:30 PM | previous day |
| 7:00 AM | 12:30 AM | same day |
| 8:00 AM | 1:30 AM | same day |
| 9:00 AM | 2:30 AM | same day |
| 10:00 AM | 3:30 AM | same day |
| 11:00 AM | 4:30 AM | same day |
| 12:00 PM | 5:30 AM | same day |
| 1:00 PM | 6:30 AM | same day |
| 2:00 PM | 7:30 AM | same day |
| 3:00 PM | 8:30 AM | same day |
| 4:00 PM | 9:30 AM | same day |
| 5:00 PM | 10:30 AM | same day |
| 6:00 PM | 11:30 AM | same day |
| 7:00 PM | 12:30 PM | same day |
| 8:00 PM | 1:30 PM | same day |
| 9:00 PM | 2:30 PM | same day |
| 10:00 PM | 3:30 PM | same day |
| 11:00 PM | 4:30 PM | same day |
Worked examples
| When | Tehran | Buenos Aires | ISO 8601 (UTC) | Unix |
|---|---|---|---|---|
| a winter weekday | 5:30 PM UTC+3:30, January 14, 2026 | 11:00 AM UTC−3, January 14, 2026 | 2026-01-14T14:00:00.000Z | 1768399200 |
| a summer weekday | 5:30 PM UTC+3:30, July 15, 2026 | 11:00 AM UTC−3, July 15, 2026 | 2026-07-15T14:00:00.000Z | 1784124000 |
| New Year | 3:30 AM UTC+3:30, January 1, 2027 | 9:00 PM UTC−3, December 31, 2026 | 2027-01-01T00:00:00.000Z | 1798761600 |
The ISO 8601 and Unix columns are the same instant written without a zone — how APIs and databases should store it. Need this for a whole column? Convert a CSV file.
Tehran — Iran Time
- IANA identifier
- Asia/Tehran
- UTC offset
- UTC+3:30
- Daylight saving
- Not observed
- On this clock today
- Tehran, Iran
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use Asia/Tehran; a listed place's past or future rules may differ.
Iran abolished daylight saving time in 2022 and stays on UTC+3:30.
Buenos Aires — Argentina Time
- IANA identifier
- America/Argentina/Buenos_Aires
- UTC offset
- UTC−3
- Daylight saving
- Not observed
- On this clock today
- Buenos Aires, Argentina
Places that share this clock as of 2026-11-13 (tzdata 2026f). Conversions for any date use America/Argentina/Buenos_Aires; a listed place's past or future rules may differ.
Related conversions
File workspace
Converting a whole column of timestamps?
The free converter handles one value at a time across 82 formats and 92 zones. The file workspace converts an entire CSV column between any two formats and zones, previews the first rows, and leaves unreadable cells exactly as they were.
Offsets and change dates on this page are computed from IANA time zone database 2026f for 2026–2027; the live tool uses the same data.