🌍
Global Unity
One clock for all. UTE enables us to coordinate instantly, without conversion or confusion.
The clock for one planet, one humanity.
One clock for all. UTE enables us to coordinate instantly, without conversion or confusion.
12:00 UTE is the exact same instant everywhere. No ambiguity, no daylight-saving mistakes.
Based on atomic seconds, not sunrise: ideal for the Moon, Mars, and interplanetary events.
360 degrees or 1000 millidays—easy fractions of a day, always precise to as many decimals as you want.
Set a meeting at 542.38 mD—it means the exact same moment for everyone, everywhere, no time zones, no “wait, is that my morning?”
Program a global radio show or game server reset to happen at 750.00 mD—it’s perfectly coordinated in every country at once.
For astronomy, satellite ops, or future Mars colonies, a decimal global clock is future-proof and planet-agnostic.
Automate logs, IoT devices, batch jobs, or blockchains to trigger at specific mD (e.g. 333.333 mD). Decimal time is perfect for computers and logs.
UTE (Universal Time for Earth) is a global clock system that divides every day into 360 degrees (°) or 1000 millidays (mD). It’s always the same everywhere—no time zones, no confusion.
UTE is a “planetary clock.” At any instant, everyone on Earth sees the same UTE time—even if their local time is different.
Example: At 670 mD, Berlin = 18:01, New York = 12:01, Tokyo = 01:01 (next day)—but all are at 670 mD UTE.
Use a converter or this formula:
mD = (hours × 3600 + minutes × 60 + seconds) ÷ 86.4
deg = (hours × 3600 + minutes × 60 + seconds) ÷ 86400 × 360
Leap years only add an extra day. Every day resets to 0° / 0 mD at midnight UTC—no confusion.
Leap seconds only affect ultra-precise logging. For daily use, UTE is unaffected.
Similar concepts: UTC (for aviation, science), Swatch Internet Time (“.beats”), Julian Date, Unix time. UTE combines clarity, decimals, and a human-friendly approach for everyone—not just scientists or coders.
No. UTE always appears alongside classic time for comfort and learning. Over time, you’ll recognize anchor points like 500 mD = noon, 750 mD = 18:00 UTC, etc. It’s a global anchor, not a replacement for your local clock.
Publish and coordinate global events in UTE: “Live at 800 mD.” AI and automation use it as a universal moment for logs, jobs, scheduling, and more—no conversion needed.
Returns the current UTE time in degrees, millidays, and classic UTC time.
{
"frac": 0.234567,
"degrees": 84.44412,
"millidays": 234.567,
"utc": "05:37:45 UTC"
}
Convert classic UTC time (hours, minutes, seconds) into UTE degrees and millidays.
{
"degrees": 195,
"millidays": 541.666667
}
Convert UTE degrees to classic UTC time.
{
"hour": 16,
"minute": 42,
"second": 0,
"utc": "16:42:00 UTC"
}
Convert millidays to classic UTC time.
{
"hour": 18,
"minute": 0,
"second": 13,
"utc": "18:00:13 UTC"
}
Returns a human-readable “words” version of any UTE value or classic time.
{
"type": "millidays",
"value": 578.25,
"words": "five hundred seventy-eight point two five millidays past global midnight"
}
Production: https://une.earth/api/ute/
Local: http://localhost:3690/api/ute/
All endpoints are GET and respond with application/json.