Time difference between Point Pedro and Taipei
Taipei is 2 hours 30 minutes ahead of Point Pedro.
Local time in both cities
Point Pedro · Sri Lanka
23:30
Sri LankaTaipei · China
02:00
ChinaTaipei is 2 hours 30 minutes ahead of Point Pedro.
already the next day
Time zones
| Point Pedro | Asia/Colombo · UTC+05:30 |
|---|---|
| Taipei | Asia/Taipei · UTC+08:00 |
Point Pedro does not observe daylight saving and stays on UTC+05:30 all year.
Taipei does not observe daylight saving and stays on UTC+08:00 all year.
Hour-by-hour conversion
Calculated for 2026-09-21 local time in Point Pedro. The two places start and end daylight saving on different dates, so another day can give a different result.
| Point Pedro (source) | Taipei (target) |
|---|---|
| 00:00 | 02:30 |
| 01:00 | 03:30 |
| 02:00 | 04:30 |
| 03:00 | 05:30 |
| 04:00 | 06:30 |
| 05:00 | 07:30 |
| 06:00 | 08:30 |
| 07:00 | 09:30 |
| 08:00 | 10:30 |
| 09:00 | 11:30 |
| 10:00 | 12:30 |
| 11:00 | 13:30 |
| 12:00 | 14:30 |
| 13:00 | 15:30 |
| 14:00 | 16:30 |
| 15:00 | 17:30 |
| 16:00 | 18:30 |
| 17:00 | 19:30 |
| 18:00 | 20:30 |
| 19:00 | 21:30 |
| 20:00 | 22:30 |
| 21:00 | 23:30 |
| 22:00 | 00:30 next day |
| 23:00 | 01:30 next day |
Other common differences from Point Pedro
FAQ
- How many hours apart are Point Pedro and Taipei right now?
- The answer at the top of the page is calculated for the current moment and states which side is ahead. The gap changes during the year, because the two places usually start and end daylight saving on different dates.
- Is this difference the same all year?
- Not necessarily. Point Pedro uses Asia/Colombo and Taipei uses Asia/Taipei; if either observes daylight saving, the gap shifts during the year. Use “Convert a specific date and time” below to calculate it for a given day.
- How do I read the conversion table?
- The left column lists each whole hour in Point Pedro; the right column is the local time in Taipei at that same instant, with date rollovers marked. On the day clocks jump forward, some hours do not exist locally — the table says so instead of showing a plausible but wrong value.