Leap second

A leap second is a one-second adjustment that is occasionally applied to Coordinated Universal Time (UTC) in order to keep its time of day close to the mean solar time, or UT1. Without such a correction, time reckoned by Earth's rotation drifts away from atomic time because of irregularities in the Earth's rate of rotation. Since this system of correction was implemented in 1972, 25 such leap seconds have been inserted. The most recent one happened on June 30, 2012 at 23:59:60 UTC.^[1] A leap second will again be inserted at the end of June 30, 2015 at 23:59:60 UTC.^[2]

The UTC time standard, which is widely used for international timekeeping and as the reference for civil time in most countries, uses the international system (SI) definition of the second, based on atomic clocks. Like most time standards, UTC defines a grouping of seconds into minutes, hours, days, months, and years. However, the duration of one mean solar day is slightly longer than 24 hours (86400 SI seconds). Therefore, if the UTC day were defined as precisely 86400 SI seconds, the UTC time-of-day would slowly drift apart from that of solar-based standards, such as Greenwich Mean Time (GMT) and its successor UT1. The purpose of a leap second is to compensate for this drift, by occasionally scheduling some UTC days with 86401 or 86399 SI seconds.

Specifically, a positive leap second is inserted between second 23:59:59 of a chosen UTC calendar date (the last day of a month, usually June 30 or December 31) and second 00:00:00 of the following date. This extra second is displayed on UTC clocks as 23:59:60. On clocks that display local time tied to UTC, the leap second may be inserted at the end of some other hour (or half-hour or quarter-hour), depending on the local time zone.

A negative leap second would suppress second 23:59:59 of the last day of a chosen month, so that second 23:59:58 of that date would be followed immediately by second 00:00:00 of the following date. However, since the UTC standard was established, negative leap seconds have never been needed.

Because the Earth's rotation speed varies in response to climatic and geological events, UTC leap seconds are irregularly spaced and unpredictable. Insertion of each UTC leap second is usually decided about six months in advance by the International Earth Rotation and Reference Systems Service (IERS), when needed to ensure that the difference between the UTC and UT1 readings will never exceed 0.9 second. Between their adoption in 1972 and June 2012, 25 leap seconds have been scheduled, all positive; this will become 26 leap seconds at 23:59:60 UTC on June 30, 2015.^[2][3]

History

About 140 AD, Ptolemy, the Alexandrian astronomer, sexagesimally subdivided both the mean solar day and the true solar day to at least six places after the sexagesimal point, and he used simple fractions of both the equinoctial hour and the seasonal hour, none of which resemble the modern second.^[4] Muslim scholars, including al-Biruni in 1000, subdivided the mean solar day into 24 equinoctial hours, each of which was subdivided sexagesimally, that is into the units of minute, second, third, fourth and fifth, creating the modern second as ¹⁄₆₀ of ¹⁄₆₀ of ¹⁄₂₄ = ¹⁄₈₆₄₀₀ of the mean solar day in the process.^[5] With this definition, the second was proposed in 1874 as the base unit of time in the CGS system of units.^[6] Soon afterwards Simon Newcomb and others discovered that Earth's rotation period varied irregularly,^[7] so in 1952, the International Astronomical Union (IAU) defined the second as a fraction of the sidereal year. Because the tropical year was considered more fundamental than the sidereal year, in 1955, the IAU redefined the second as the fraction ¹⁄_{31,556,925.9747} of the 1900.0 mean tropical year, which was adopted in 1956 by the International Committee for Weights and Measures and in 1960 by the General Conference on Weights and Measures, becoming a part of the International System of Units (SI).^[8]

Eventually, this definition too was found to be inadequate for precise time measurements, so in 1967, the SI second was again redefined as 9,192,631,770 periods of the radiation emitted by a caesium-133 atom in the transition between the two hyperfine levels of its ground state.^[9] That value agreed to 1 part in 10¹⁰ with the astronomical (ephemeris) second then in use.^[10] It was also close to ¹⁄₈₆₄₀₀ of the mean solar day as averaged between 1750 and 1892.

However, for the past several centuries, the length of the mean solar day has been increasing by about 1.4–1.7 ms per century, depending on the averaging time.^[11][12][13] By 1961, the mean solar day was already a millisecond or two longer than 86,400 SI seconds.^[14] Therefore, time standards that change the date after precisely 86,400 SI seconds, such as the International Atomic Time (TAI), will get increasingly ahead of time standards tied to the mean solar day, such as Greenwich Mean Time (GMT).

When the Coordinated Universal Time standard was instituted in 1961, based on atomic clocks, it was felt necessary to maintain agreement with the GMT time of day, which, until then, had been the reference for broadcast time services. Thus, from 1961 to 1971, the rate of (some) atomic clocks was constantly slowed to remain synchronised with GMT. During that period, therefore, the "seconds" of broadcast services were actually slightly longer than the SI second and closer to the GMT seconds.

In 1972, the leap-second system was introduced so that the broadcast UTC seconds could be made exactly equal to the standard SI second, while still maintaining the UTC time of day and changes of UTC date synchronized with those of UT1 (the solar time standard that superseded GMT).^[9] By then, the UTC clock was already 10 seconds behind TAI, which had been synchronized with UT1 in 1958, but had been counting true SI seconds since then. After 1972, both clocks have been ticking in SI seconds, so the difference between their readouts at any time is 10 seconds plus the total number of leap seconds that have been applied to UTC (35 seconds in July 2012).

Insertion of leap seconds

Announced leap seconds to date

Year	Jun 30	Dec 31
1972	+1	+1
1973	0	+1
1974	0	+1
1975	0	+1
1976	0	+1
1977	0	+1
1978	0	+1
1979	0	+1
1980	0	0
1981	+1	0
1982	+1	0
1983	+1	0
1984	0	0
1985	+1	0
1986	0	0
1987	0	+1
1988	0	0
1989	0	+1
1990	0	+1
1991	0	0
1992	+1	0
1993	+1	0
1994	+1	0
1995	0	+1
1996	0	0
1997	+1	0
1998	0	+1
1999	0	0
2000	0	0
2001	0	0
2002	0	0
2003	0	0
2004	0	0
2005	0	+1
2006	0	0
2007	0	0
2008	0	+1
2009	0	0
2010	0	0
2011	0	0
2012	+1	0
2013	0	0
2014	0	0
2015	+1
Year	Jun 30	Dec 31
Total	11	15
	26
Current TAI − UTC
35 (until June 2015)

The scheduling of leap seconds was initially delegated to the Bureau International de l'Heure (BIH), but passed to the International Earth Rotation and Reference Systems Service (IERS) on January 1, 1988. IERS usually decides to apply a leap second whenever the difference between UTC and UT1 approaches 0.6 s, in order to keep the difference between UTC and UT1 from exceeding 0.9 s.

The UTC standard allows leap seconds to be applied at the end of any UTC month, with first preference to June and December and second preference to March and September. As of July 2015, all of them have been inserted either at the end of June 30 or December 31. IERS publishes announcements every six months, whether leap seconds are to occur or not, in its "Bulletin C". Such announcements are typically published well in advance of each possible leap second date – usually in early January for June 30 and in early July for December 31.^[15][16] Some time signal broadcasts give voice announcements of an impending leap second.

Between 1972 and 2012, a leap second has been inserted about every 18 months, on the average. However, the spacing is quite irregular and apparently increasing: there were no leap seconds in the seven-year interval between January 1, 1999 and December 31, 2005, but there were 9 leap seconds in the 8 years 1972–1979.

Unlike leap days, UTC leap seconds occur simultaneously worldwide; for example, the leap second on December 31, 2005 23:59:60 UTC was December 31, 2005 18:59:60 (6:59:60 p.m.) in U.S. Eastern Standard Time and January 1, 2006 08:59:60 (a.m.) in Japan Standard Time.

Not all clocks implement leap seconds in the same manner as UTC. Leap seconds in Unix time are commonly implemented by repeating the last second of the day. Network Time Protocol freezes time during the leap second. Other experimental schemes warp time in the vicinity of a leap second.^[17]

Slowing rotation of the Earth

Leap seconds are irregularly spaced because the Earth's rotation speed changes irregularly. Indeed, the Earth's rotation is quite unpredictable in the long term, which explains why leap seconds are announced only six months in advance.

A mathematical model of the variations in the length of the solar day was developed by F. R. Stephenson and L. V. Morrison,^[13] based on records of eclipses for the period 700 BC to 1623 AD, telescopic observations of occultations for the period 1623 until 1967 and atomic clocks thereafter. The model shows a steady increase of the mean solar day by 1.70 ms (± 0.05 ms) per century, plus a periodic shift of about 4 ms amplitude and period of about 1,500 yr.^[13] Over the last few centuries, the periodic component reduced the rate of lengthening of the mean solar day to about 1.4 ms per century.^[18]

The main reason for the slowing down of the Earth's rotation is tidal friction, which alone would lengthen the day by 2.3 ms/century.^[13] Other contributing factors are the movement of the Earth's crust relative to its core, changes in mantle convection, and any other events or processes that cause a significant redistribution of mass. These processes change the Earth's moment of inertia, affecting the rate of rotation due to conservation of angular momentum, sometimes increasing earth's rotational speed (decreasing the solar day and opposing tidal friction). For example, glacial rebound shortens the solar day by 0.6 ms/century and the 2004 Indian Ocean earthquake is thought to have shortened it by 2.68 microseconds.^[19]

Proposal to abolish leap seconds

The irregularity and unpredictability of UTC leap seconds is problematic for several areas, especially computing. For example, to compute the elapsed time in seconds between two given UTC past dates requires consulting a table of leap seconds, which needs to be updated whenever a new leap second is announced. Moreover, it is not possible to compute accurate time intervals for UTC dates that are more than about six months in the future.

On July 5, 2005, the Head of the Earth Orientation Center of the IERS sent a notice to IERS Bulletins C and D subscribers, soliciting comments on a U.S. proposal before the ITU-R Study Group 7's WP7-A to eliminate leap seconds from the UTC broadcast standard before 2008 (the ITU-R is responsible for the definition of UTC). The Wall Street Journal noted that the proposal was considered by a U.S. official to be a "private matter internal to the ITU", as of July 2005.^[20] It was expected to be considered in November 2005, but the discussion has since been postponed.^[21] Under the proposal, leap seconds would be technically replaced by leap hours as an attempt to satisfy the legal requirements of several ITU-R member nations that civil time be astronomically tied to the Sun.

A number of objections to the proposal have been raised. Dr. P. Kenneth Seidelmann, editor of the Explanatory Supplement to the Astronomical Almanac, wrote a letter^[22] lamenting the lack of consistent public information about the proposal and adequate justification. Steve Allen of the University of California, Santa Cruz cited what he claimed to be the large impact on astronomers in a Science News article.^[23] He has an extensive online site^[24] devoted to the issues and the history of leap seconds, including a set of references about the proposal and arguments against it.^[25]

At the 2014 General Assembly of the International Union of Radio Scientists (URSI), Dr. Demetrios Matsakis, the US Naval Observatory's Chief Scientist for Time Services, presented the reasoning in favor of the redefinition and rebuttals to the arguments made against it.^[26] He stressed the practical inability of software programmers to allow for the fact that leap seconds make time appear to go backwards, particularly when most of them do not even know that leap seconds exist. The possibility of leap seconds being a hazard to navigation was presented, as well as the observed effects on commerce.

The United States formulated its position on this matter based upon the advice of the National Telecommunications and Information Administration^[27] and the Federal Communications Commission (FCC), which solicited comments from the general public.^[28] This position is in favor of the redefinition.^[29] The FCC has posted its received comments, which can be found using their search engine for proceeding 04-286 and limiting the "received period" to those between January 27 and February 18, 2014 inclusive.^[30]

In 2011, Chunhao Han of the Beijing Global Information Center of Application and Exploration said China had not decided what its vote would be in January 2012, but some Chinese scholars consider it important to maintain a link between civil and astronomical time due to Chinese tradition. The 2012 vote was ultimately deferred.^[31] At an ITU/BIPM-sponsored workshop on the leap second, Dr. Han expressed his personal view in favor of abolishing the leap second,^[32] and similar support for the redefinition was again expressed by Dr. Han, along with other Chinese timekeeping scientists, at the URSI General Assembly in 2014.

Arguments against the proposal include the unknown expense of such a major change and the fact that universal time will no longer correspond to mean solar time. It is also answered that two timescales that do not follow leap seconds are already available, International Atomic Time (TAI) and Global Positioning System (GPS) time. Computers, for example, could use these and convert to UTC or local civil time as necessary for output. Inexpensive GPS timing receivers are readily available, and the satellite broadcasts include the necessary information to convert GPS time to UTC. It is also easy to convert GPS time to TAI, as TAI is always exactly 19 seconds ahead of GPS time. Examples of systems based on GPS time include the CDMA digital cellular systems IS-95 and CDMA2000. In general, computer systems use UTC and synchronize their clocks using NTP (Network Time Protocol). Systems that cannot tolerate disruptions caused by leap seconds can base their time on TAI and use PTP (Precision Time Protocol). However, the BIPM has pointed out that this proliferation of timescales leads to confusion,^[33] and examples of how leap seconds have adversely affected GPS and NTP are given elsewhere in this article.

At the 47th meeting of the Civil Global Positioning System Service Interface Committee in Fort Worth, Texas in September 2007, it was announced that a mailed vote would go out on stopping leap seconds. The plan for the vote was:^[34]

• April 2008: ITU Working Party 7A will submit to ITU Study Group 7 project recommendation on stopping leap seconds
• During 2008, Study Group 7 will conduct a vote through mail among member states
• October 2011: The ITU-R released its status paper, Status of Coordinated Universal Time (UTC) study in ITU-R, in preparation for the January 2012 meeting in Geneva; the paper reported that, to date, in response to the UN agency's 2010 & 2011 web based surveys requesting input on the topic, it had received 16 responses from the 192 Member States with "13 being in favor of change, 3 being contrary."^[35]
• January 2012: The ITU makes a decision.

In January 2012, rather than decide yes or no per this plan, the ITU decided to postpone a decision on leap seconds to the World Radiocommunication Conference in 2015. This is scheduled for 2–27 November in Geneva, Switzerland. France, Italy, Japan, Mexico, and the US were reported to be in favor, while Canada, China, Germany, and the UK were reportedly against.^[36] Others, including Nigeria, Russia, and Turkey, called for more study. The BBC states the ITU decided further study of broader social implications was needed.^[37]

In October 2014, Dr. Wlodzimierz Lewandowski, chair of the timing subcommittee of the Civil GPS Interface Service Committee and a member of the ESA Navigation Program Board, presented a CGSIC-endorsed resolution to the ITU that supported the redefinition and described leap seconds as a "hazard to navigation".^[38] CGSIC meetings, coincident with the ION-GNSS meetings of the Institute of Navigation, have long provided a forum for public discussion of this matter; viewgraphs since 2008 are posted.^[39]

In May 2014, David Willetts, the ex-UK Minister State for Universities and Science, described as a non-scientist with a degree from the London School of Economics and Political Science, expressed opposition to the abolition of leap seconds. He indicated that as a layman, he wanted to keep "the link between time and people's everyday experience of day and night." He also wanted to keep Greenwich Mean Time in Britain, and "warned" that it would drift towards the United States.^[40] An article in the Times science section suggested that the abolition of leap seconds would mean the demise of Britain's role in timekeeping.^[41]

Some of the objections to the proposed change have been answered by its opponents. For example Dr. Felicitas Arias, who, as Director of the International Bureau of Weights and Measures (BIPM)'s Time, Frequency, and Gravimetry Department, is responsible for generating UTC noted in a press release^[42] that the drift of about one minute every 60–90 years could be compared to the 16-minute annual variation between true solar time and mean solar time, the one hour offset by use of daylight time, and the several-hours offset in certain geographically extra-large time zones. This value was computed using the pre-21st century slow-down rate; if the current slow-down rate prevails, it could take two centuries for the first one-minute drift to develop, though the rate of drift would increase over time. It has been suggested that if the proposal passes, those users who require the difference between solar time (GMT-equivalent) and UTC could still obtain it several ways, including from the IERS via the internet, and that GPS upgrade plans include broadcasting this information. It has also been suggested that sovereign nations could adjust their civil time if desired by changing the offset between their civil time and UTC, though this would be impractical to do for frequent small adjustments.

Examples of problems associated with the leap second

A number of organizations reported problems caused by flawed software following the June 30, 2012, leap second. Among the sites which reported problems were reddit (Apache Cassandra), Mozilla (Hadoop),^[43] Qantas Airways,^[44] and various sites running Linux.^[45]

Older versions of Motorola Oncore VP, UT, GT, and M12 GPS receivers had a software bug that would cause a single timestamp to be off by a day if no leap second was scheduled for 256 weeks. On November 28, 2003, this actually happened. At midnight, the receivers with this firmware reported November 29, 2003 for one second and then reverted to November 28, 2003.^[46][47]

Older Trimble GPS receivers had a software flaw that would insert a leap second immediately after the GPS constellation started broadcasting the next leap second insertion time (some months in advance of the actual leap second), rather than waiting for the next leap second to happen. This left the receiver's time off by a second in the interim.^[48]

Older Datum Tymeserv 2100 GPS receivers and Symmetricomm Tymeserv 2100 receivers also have a similar flaw as the previous noted Trimble GPS receivers, where the time is off by one second. The advance announcement of the leap second is applied as soon as the message is received, instead of waiting for the correct date. There is no firmware upgrade for this problem. A workaround has been described and tested, but if the GPS system rebroadcasts the announcement, or the unit is powered off, the issue will occur again.^[49]

The NTP packet includes a leap second flag, which informs the user that a leap second is imminent. This, among other things, allows the user to distinguish between a bad measurement that should be ignored and a genuine leap second that should be followed. It has been reported that never, since the monitoring began in 2008 and whether or not a leap second should be inserted, have all NTP servers correctly set their flags on a December 31 or June 30.^[50] This is one reason many NTP servers broadcast the wrong time for up to a day after a leap second insertion,^[51] and it has been suggested that hackers have exploited this vulnerability.^[52][53]

Four different brands of marketed navigational receivers that use data from GPS and/or GALILEO along with the Chinese BEIDOU satellites, and even some receivers that use BEIDOU satellites alone, were found to implement leap seconds one day early.^[54] This was traced to the fact that BEIDOU numbers the days of the week from 0 to 6, while GPS and GALILEO number them from 1 to 7. The problem was found to exist in commercial simulators that are used by manufacturers to test their equipment.

Workarounds for leap second issues

Instead of inserting a leap second at the end of the day, Google servers implement a leap smear, extending seconds slightly over a time window prior to the leap second.^[55]

It has been proposed that media clients using the Real-time Transport Protocol inhibit generation or use of NTP timestamps during the leap second and the second preceding it.^[56]

It has been proposed that, in the event the ITU resolution passes and leap seconds are no longer inserted, special Network Time Protocol and other time servers could be set up that provide UT1 rather than UTC.^[57] Those astronomical observatories and other users that require UT1 could run off that time – although in many cases these users already download UT1-UTC from the IERS, and apply corrections in software.^[58]

See also

• Clock drift, phenomenon where a clock gains/loses time compared to another clock
• Leap year, a year containing one extra day
• Unix time, a common representation of time for computer systems
• Delta-T (ΔT), the time difference obtained by subtracting Universal Time from Terrestrial Time
• Shortwave radio stations that continuously broadcast UTC
  • CHU
  • WWV

References

Notes

Bibliography

• Ahuja, Anjana (October 30, 2005). "Savouring the last leap second in history". New Straits Times, p. F10.
• Cowen, Ron. (April 22, 2006). "To Leap or Not to Leap: Scientists debate a timely issue". Science News
• Grossman, Wendy M. (November 2005). "Wait a Second". Scientific American, pp. 12–13.
• International Earth Rotation and Reference System Service (IERS). (January 16, 2014). Bulletin C, 47.
• Merali, Zeeya. (November 8, 2011). "Time is running out for the leap second". Nature News.

Further reading

• Finkleman, David et al. "The Future of Time: UTC and the Leap Second". American Scientist 99 (4): 312–319. doi:10.1511/2011.91.1.  CS1 maint: Explicit use of et al. (link)
• Kamp, Poul-Henning (2011). "The One-Second War". Communications of the ACM 54 (5): 44–48. doi:10.1145/1941487.1941505. 
• McCarthy, Dennis D. & Seidelmann, P. Kenneth. (2009). TIME From Earth Rotation to Atomic Physics. Weinheim: Wiley-VCH.

External links

Wikimedia Commons has media related to Leap second.

• UTC vs UT1 1972–2005
• IERS Bulletins, both current and historical bulletins from www.iers.org
• USNO article on leap seconds
• Leap Seconds in NTP, GPS, DCF77
• Dynamic differences between UTC and TAI
• How to Watch a Leap Second
• The Year 2005 to Have 'Leap Second' Added, NPR audio segment by Joe Palca
• NIST FAQ about leap year and leap second
• Time Scales in Satellite Geodesy
• "UTC and the Future of the Leap Second". Archived from the original on January 30, 2012. 

UTC redefinition

• The leap second: its history and possible future
• UTC might be redefined without Leap Seconds
• Efforts to abolish leap seconds

Time Key concepts Past history deep time Present Future futurology far future Eternity arguments for Eternal return Immortality Measurement and standards Chronometry UTC UT TAI Unit of time Planck time Second Minute Hour Day Week Month Year Decade Century Millennium Tropical year Solar year Sidereal year Measurement systems Time zone 12-hour clock 24-hour clock Daylight saving time New Earth Time Solar time Sidereal time Metric time Decimal time Hexadecimal time Calendars Gregorian Julian Hebrew Islamic Lunar Solar Hijri Mayan Intercalation Leap second Leap year Clocks Horology History of timekeeping devices Main types astrarium atomic quantum marine sundial watch water-based Chronology History Astronomical chronology Big History Calendar era Chronicle Deep time Periodization Regnal year Timeline Religion Mythology Dreamtime Kāla Kalachakra Prophecy Time and fate deities Wheel of time Philosophy of time A-series and B-series B-theory of time Causality Duration Endurantism Eternal return Eternalism Event Perdurantism Presentism Temporal finitism Temporal parts The Unreality of Time Human experience and use of time Accounting period Fiscal year Mental chronometry Procrastination Punctuality Temporal database Term Time discipline Time management Time perception Specious present Time-tracking software Time-use research Time-based currency (time banking) Time value of money Time clock Timesheet Time in Geology Geological time age chron eon epoch era period Geochronology Geological history of Earth Physics Absolute time and space Arrow of time Chronon Coordinate time Imaginary time Planck epoch Planck time Proper time Rate Spacetime Theory of relativity Time dilation gravitational Time domain T-symmetry other subject areas Chronobiology Circadian rhythms Dating methodologies in archaeology Time geography Related topics Carpe diem Clock position Space System time Tempus fugit Time capsule Time complexity Time signature Time travel Time portal

Time measurement and standards Major subjects Time Chronometry Orders of magnitude Metrology International standards UTC UTC offset UT ΔT DUT1 IERS ISO 31-1 ISO 8601 TAI 12-hour clock 24-hour clock Barycentric Coordinate Time Civil time Daylight saving time Geocentric Coordinate Time International Date Line Leap second New Earth Time Solar time Terrestrial Time Time zone Obsolete standards Barycentric Dynamical Time Ephemeris time Greenwich Mean Time Prime meridian Time in physics Absolute time and space Spacetime Chronon Continuous time Coordinate time Cosmological decade Discrete time Planck epoch Planck time Proper time Theory of relativity Time dilation Gravitational time dilation Time domain T-symmetry Horology Clock Astrarium Atomic clock Complication Equation of time History of timekeeping devices Hourglass Marine chronometer Marine sandglass Radio clock Sundial Watch Water clock Calendar Astronomical Dominical letter Epact Equinox Gregorian Hebrew Hindu Intercalation Islamic Julian Leap year Lunar Lunisolar Seven-day week Solar Solstice Tropical year Weekday determination Weekday names Archaeology and geology Dating methodologies Geologic time scale International Commission on Stratigraphy Astronomical chronology Galactic year Nuclear time scale Precession Sidereal time Units of time Century Day Decade Fortnight Hour Jiffy Lustrum Millennium Minute Moment Month Paksha Saeculum Second Shake Tide Week Year Related topics Chronology Duration Mental chronometry Metric time System time Time value of money Timekeeper

New Year's Eve and New Year's Day Events America's Party First Night Hogmanay New Year's Eve in London Objects dropped on New Year's Eve Peach Drop Pelican Drop Réveillon de Copacabana Sydney New Year's Eve The Possum Drop Times Square Ball Vienna New Year's Concert Sports Rose Bowl Orange Bowl Sugar Bowl Fiesta Bowl Cotton Bowl Classic Peach Bowl Citrus Bowl Gator Bowl Outback Bowl Heart of Dallas Bowl Four Hills Tournament NHL Winter Classic Spengler Cup Final Saint Silvester Road Race New Year Sprint Nos Galan road race Parades Tournament of Roses Parade London New Year's Day Parade Florida Citrus Parade Mummers Parade Television New Year's Rockin' Eve New Year's Eve with Carson Daly New Year Live CNN New Year's Eve Live Bye Bye Dinner for One Happy New Year, America Hogmanay Live Hootenanny Kōhaku Uta Gassen Only an Excuse? Red Bull New Year No Limits Rudolph's Shiny New Year Scotch and Wry Silvesterstadl Silvesterpunsch 2000 Today (US, Ireland) Happy New Year, Charlie Brown! First Night 2013 with Jamie Kennedy Film Wee Willie Winkie Winnie the Pooh: A Very Merry Pooh Year Music "Auld Lang Syne" "Happy New Year" "What Are You Doing New Year's Eve?" "Levy-Dew" "New Year's Day" Related topics Gregorian calendar Baby New Year Calennig Feast of St. Silvester Hogmanay Holiday season Leap second Guy Lombardo New Year's resolution New Year tree Vasilopita Watchnight service