Current Utc Time With Seconds

US, Canada, Mexico Time Zones

Converting UTC to CST. This time zone converter lets you visually and very quickly convert UTC to CST and vice-versa. Simply mouse over the colored hour-tiles and glance at the hours selected by the column. UTC stands for Universal Time. CST is known as Central Standard Time. CST is 5 hours behind UTC. The time zone offset from UTC, measured in seconds. Positive values correspond to time zones east of UTC, negative values to zones west of UTC. (Technically, PostgreSQL does not use UTC because leap seconds are not handled.) timezonehour. The hour component of the time zone offset. The minute component of the time zone offset. A localtime is a chrono::timepoint, but outside of a zonedtime, not associated with any particular timezone. Consequently there is no clock or now function associated with localtime. One can extract the localtime from a zonedtime. This operation will use the timezone to get a UTC offset from the systime in the zonedtime: auto lt.

Atlantic Daylight Time (ADT) • Eastern Daylight Time (EDT) • Central Daylight Time (CDT) • Mountain Daylight Time (MDT) • Pacific Daylight Time (PDT) • Alaska Daylight Time (AKDT) • Hawaii Time • Arizona • Saskatoon • New York • Toronto • Mexico City • San Francisco • Chicago • Houston • Miami • Phoenix • Halifax • Denver • Monterrey • Chihuahua


Europe Time Zones

Greenwich Mean Time (GMT) • British Summer Time (BST) • Western European Summer Time (WEST) • Central European Summer Time (CEST) • Eastern European Summer Time (EEST) • London • Paris • Berlin • Athens • Warsaw • Kiev • Belarus • Moscow • Madrid • Stockholm • Amsterdam • Istanbul


Australia, New Zealand Time Zones

AEST • ACST • AWST •New Zealand Time (NZT) • Queensland • Adelaide • Brisbane • Canberra • Melbourne • Perth • Sydney • Auckland • Fiji • Solomon Islands • Papua New Guinea


Asia Time Zones

India • Pakistan • China • UAE • Japan • Korea • Philippines • Thailand • Hong Kong • Taiwan • Malaysia • Singapore • Jakarta • Bangladesh • Sri Lanka • Nepal • Kuwait • Saudi Arabia • Viet Nam • Oman • Israel • Jordan • Beijing • Bangalore • Kuala Lumpur • Manila • Tokyo • Seoul • Karachi • Dubai


Africa Time Zones

West Africa Time (WAT) • Central Africa Time (CAT) • East Africa Time (EAT) • Egypt • Nigeria • Kenya • Ghana • Morocco • Tanzania • Ethiopia • Uganda • South Africa • Cairo • Algiers • Casablanca • Accra • Lagos • Cape Town • Nairobi

Java


South America Time Zones

Brazil • Argentina • Chile • Peru • Ecuador • Colombia • Venezuela • Panama • Puerto Rico • São Paulo • Manaus • Rio de Janeiro • Buenos Aires • Santiago • Lima • Quito • Bogota • Caracas


Russia Time Zones

Moscow • Novosibirsk • Yekaterinburg • Omsk • St Petersburg • Kazan • Irkutsk • Chita • Vladivostok • Sochi • Almaty • Kyrgyzstan • Uzbekistan • Tajikistan

This page is updated monthly and contains a table of leap seconds, the current difference between the UT1 and UTC time scales, and the current UT1 - UTC difference that is being broadcast by NIST (called the DUT1 correction).

The master clock pulses used by the WWV, WWVH, WWVB, ACTS and Internet Time Service (ITS) time code transmissions are referenced to the UTC(NIST) time scale. Occasionally, 1 s is added to the UTC time scale. This second is called a leap second. Its purpose is to keep the UTC time scale within ±0.9 s of the UT1 astronomical time scale, which changes slightly due to variations in the rotation of the Earth.

See information about why we need leap seconds.

Current time utc +1

Leap Seconds

Coordinated Universal Time (UTC) is based on International Atomic Time (TAI), but it is adjusted by leap seconds to account for the difference between the definition of the second and the rotation of Earth. This correction keeps UTC in conjunction with the apparent position of the Sun and the stars, and it is the standard used for all general timekeeping applications.
The current difference between UTC and TAI is 37 seconds. (TAI is ahead of UTC by this amount)

No leap second was added at the end of December 2020.

No leap second will be introduced at the end of June 2021.

The first leap second was inserted into the UTC time scale on June 30, 1972. Leap seconds are used to keep the difference between UT1 and UTC to within ±0.9 s. The table below lists all leap seconds that have already occurred, or are scheduled to occur.

Current Utc Time With Seconds Calculator

All leap seconds listed in the table are positive leap seconds, which means an extra second is inserted into the UTC time scale. The sequence of events is:

23h 59m 59s - 23h 59m 60s - 00h 00m 00s

Leap Seconds Inserted into the UTC Time Scale

DateMJDDateMJDDateMJDDateMJD
2016-12-31577531998-12-31511781989-12-31478911979-12-3144238
2015-06-30572031997-06-30506291987-12-31471601978-12-3143873
2012-06-30561081995-12-31500821985-06-30462461977-12-3143508
2008-12-31548311994-06-30495331983-06-30455151976-12-3143143
2005-12-31537351993-06-30491681982-06-30451501975-12-3142777
1992-06-30488031981-06-30447851974-12-3142412
1990-12-31482561973-12-3142047
1972-12-3141682
1972-06-3041498

Current UT1-UTC values

This table lists the most recent differences between UT1 and UTC. This information is obtained from the United States Naval Observatory (USNO).

Weekly UT1-UTC Values

DateMJDUT1-UTC(±5 ms)UTC(USNO,MC) - UTC(NIST) (±20 ns)
2021-02-2559270-169.34 ms-2.8 ns
2021-02-1859263-171.96 ms-2.0 ns
2021-02-1159246-169.26 ms-1.8 ns
2021-02-0459249-168.85 ms-1.5 ns
2021-01-2859242-167.30 ms-1.9 ns
2021-01-2159235-171.05 ms-3.1 ns
2021-01-1459228-172.88 ms-3.8 ns
2021-01-0759221-174.85 ms-4.2 ns

DUT1 corrections

Leap seconds ensure that UT1 - UTC will always be held within ±0.9 s. The current value of UT1 - UTC is called the DUT1 correction and is obtained from the Bureau International des Poids et Mesures (BIPM). DUT1 corrections are broadcast by WWV, WWVH, WWVB and ACTS, and are printed below. These corrections may be added to received UTC time signals in order to obtain UT1.

The resolution of the DUT1 correction is 0.1 s, and represents an average value for an extended range of dates. Therefore, it will not agree exactly with the weekly UT1-UTC(NIST) values shown in the earlier table, which have 1 ms resolution and are updated weekly.

Current Utc Time 12

DUT1 (UT1-UTC) corrections broadcast by NIST

Current Utc Time With Seconds Per

Start DateTimeDUT1 Correction
2019-05-020000 UTC-0.2 s
2019-01-170000 UTC-0.1 s
2018-09-210000 UTC+0.0 s
2018-03-150000 UTC+0.1 s
2017-11-300000 UTC+0.2 s
2017-06-290000 UTC+0.3 s
2017-03-300000 UTC+0.4 s
2017-01-260000 UTC+0.5 s
2017-01-010000 UTC+0.6 s
2016-11-170000 UTC-0.4 s
2016-09-010000 UTC-0.3 s
2016-05-190000 UTC-0.2 s
2016-03-240000 UTC-0.1 s
2016-01-310000 UTC 0.0 s
2015-11-260000 UTC+0.1 s
2015-09-110000 UTC+0.2 s
2015-07-010000 UTC+0.3 s
2015-05-280000 UTC- 0.7 s
2015-03-190000 UTC- 0.6 s
2014-12-250000 UTC- 0.5 s
2014-09-250000 UTC- 0.4 s
2014-05-080000 UTC- 0.3 s
2014-02-200000 UTC- 0.2 s
2013-11-210000 UTC- 0.1 s
2013-08-220000 UTC+ 0.0 s
2013-04-110000 UTC+ 0.1 s
2013-01-310000 UTC+ 0.2 s
2012-10-250000 UTC+ 0.3 s
2012-07-010000 UTC+ 0.4 s
2012-05-100000 UTC- 0.6 s
2012-02-090000 UTC- 0.5 s
2011-11-040000 UTC- 0.4 s
2011-05-120000 UTC- 0.3 s
2011-01-060000 UTC- 0.2 s
2010-06-030000 UTC- 0.1 s
2010-03-110000 UTC+0.0 s
2009-11-120000 UTC+0.1 s
2009-06-110000 UTC+0.2 s
2009-03-120000 UTC+0.3 s
2008-11-200000 UTC- 0.6 s
2008-08-070000 UTC- 0.5 s
2008-03-130000 UTC- 0.4 s
2007-11-290000 UTC- 0.3 s
2007-06-140000 UTC- 0.2 s
2007-03-150000 UTC- 0.1 s
2006-12-220000 UTC+0.0 s
2006-09-280000 UTC+0.1 s
2006-04-270000 UTC+0.2 s
2006-01-010000 UTC+0.3 s
2005-03-170000 UTC- 0.6 s
2004-04-290000 UTC- 0.5 s
2003-04-030000 UTC- 0.4 s
2002-10-240000 UTC- 0.3 s
2002-02-140000 UTC- 0.2 s
2001-10-040000 UTC- 0.1 s
2001-03-010000 UTC+0.0 s