Julian Date Examples

1. A full YYYYDDD code

A seven-digit code has a four-digit year followed by a three-digit day of that year. For example, 2026202 separates into 2026 + 202. Day 202 of 2026 is 21 July 2026. This is the clearest option for production records, exports and long-lived databases because it has no century ambiguity.

2. A five-digit YYDDD code

A five-digit code shortens the year to two digits. 26202 is commonly read as 2026, day 202, or 21 July 2026. The date portion works exactly the same way as a seven-digit code, but the century is inferred from context. It is useful on a compact label, yet risky as the only value in an archive.

If software must accept short years, document its pivot rule. This site uses the common 1969–2068 window: 00–68 map to 2000–2068 and 69–99 map to 1969–1999. That is a convenience, not proof of the code’s intended century.

3. A three-digit day-of-year code on a product

On an egg carton, batch sticker or can, 202 usually means only “the 202nd day of the year.” It may be a pack or production date, but it does not identify an expiry date and it does not contain the year. Look for a separate sell-by, best-by, lot, plant or inspection code before drawing conclusions about freshness.

The same three-digit code falls on a different date in a leap year after February. Day 060, for example, is 1 March in a common year but 29 February in a leap year. Use the year printed elsewhere on the item whenever possible.

4. The leap-year checkpoint

Leap years have 366 days. In 2024, day 060 is 29 February, day 061 is 1 March, and day 366 is 31 December. In a common year such as 2026, day 060 is already 1 March and the largest valid value is 365. This one-day difference is a common source of errors in spreadsheets and batch imports.

The Gregorian rule is precise: a year divisible by 4 is a leap year except a century year unless it is also divisible by 400. Thus 2024 and 2000 are leap years; 1900 and 2100 are not.

5. Preserve the leading zeroes

The day portion should be written as 001 through 365 (or 366). Without padding, 2026 day 9 might be written as 20269, which is ambiguous and does not sort with the rest of the year. Use 2026009 instead. In spreadsheets, store the display as text or apply a custom numeric format such as 0000000 when appropriate.

6. An astronomical Julian Date example

Astronomical Julian Dates identify an instant, not just a calendar day. At 00:00 UTC on 21 July 2026, the value is 2461242.5. At noon UTC it becomes 2461243.0, because the astronomical day begins at noon. Its integer label is the Julian Day Number (JDN).

This is why an astronomical JD should be recorded with a time scale and enough decimal places for the required precision. It is not a replacement for an industrial YYYYDDD code.

7. Modified Julian Date (MJD) example

The Modified Julian Date subtracts 2,400,000.5 from the full JD. For the same midnight moment above, 2461242.5 − 2400000.5 = 61242.0. MJD begins at midnight UTC, which makes it more convenient for satellite, geodetic and computing applications. A number around 60,000 with a decimal is a useful clue that you are looking at MJD rather than a product code.

Before you decode a real-world label

1. Count the digits and note whether there is a decimal point.
2. Find the year and the source context: product label, database, telescope, or telemetry file.
3. Check whether the year is a leap year before interpreting days after February.
4. Confirm whether the code is a production date, a lot code, an inspection date, or an actual expiry date.
5. Use the full YYYYDDD format in records you create, rather than guessing a century later.

Convert a code instead of guessing

• Decode YYYYDDD, YYDDD or DDD
• Turn a calendar date into a code
• Read an egg-carton pack date
• Decode an MRE date code
• Convert astronomical JD and MJD