Time difference between Beijing and General Pico

General Pico is 11 hours behind Beijing.

Asia/Shanghai America/Argentina/Salta same day

Local time in both cities

Beijing · China
12:57
Monday, 21 September 2026
Asia/Shanghai · UTC+08:00
General Pico · Argentina
01:57
Monday, 21 September 2026
America/Argentina/Salta · UTC-03:00

General Pico is 11 hours behind Beijing.

same day

Time zones

BeijingAsia/Shanghai · UTC+08:00
General PicoAmerica/Argentina/Salta · UTC-03:00

Beijing does not observe daylight saving and stays on UTC+08:00 all year.

General Pico does not observe daylight saving and stays on UTC-03:00 all year.

Hour-by-hour conversion

Calculated for 2026-09-21 local time in Beijing. The two places start and end daylight saving on different dates, so another day can give a different result.

Beijing (source) General Pico (target)
00:00 13:00 prev day
01:00 14:00 prev day
02:00 15:00 prev day
03:00 16:00 prev day
04:00 17:00 prev day
05:00 18:00 prev day
06:00 19:00 prev day
07:00 20:00 prev day
08:00 21:00 prev day
09:00 22:00 prev day
10:00 23:00 prev day
11:00 00:00
12:00 01:00
13:00 02:00
14:00 03:00
15:00 04:00
16:00 05:00
17:00 06:00
18:00 07:00
19:00 08:00
20:00 09:00
21:00 10:00
22:00 11:00
23:00 12:00

FAQ

How many hours apart are Beijing and General Pico 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. Beijing uses Asia/Shanghai and General Pico uses America/Argentina/Salta; 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 Beijing; the right column is the local time in General Pico 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.

Both cities