Blog

Your Age to Ten Decimal Places: The Math Behind a Ticking Age Counter

20 Aug 2026·4 min read·Appynox

An age counter takes the number of seconds since you were born and divides it by the number of seconds in a year. That is the entire calculation. What makes it interesting is deciding what “a year” means, how many digits are worth showing, and which of those digits are actually telling you the truth.

This article walks through all three, with real numbers.

Step one: elapsed time

Your phone keeps a clock that counts seconds (or milliseconds) since a fixed reference point. Your birth date can be expressed the same way. Subtract one from the other and you have your age in seconds.

For someone born thirty years ago, that is roughly 946 million seconds. Phones store this as a 64-bit integer in milliseconds, so there is no precision problem at this stage.

Step two: what is a year?

This is where a choice has to be made, because there is more than one kind of year.

• A calendar year is 365 or 366 days, depending on leap years.
• The Julian year used in astronomy is exactly 365.25 days.
• The mean Gregorian year, the long-run average length of a calendar year under the leap-year rules we actually use (every four years, except centuries, except every fourth century), is exactly 365.2425 days.
• The tropical year, the time it takes the Sun to return to the same position in the seasons, is about 365.2422 days and drifts slightly over centuries.

For an age counter, the mean Gregorian year is the natural pick. It makes the integer part of your age agree with the age on your passport, and the fraction advances evenly through the year rather than jumping on leap days. In seconds, 365.2425 days is:

365.2425 × 86,400 = 31,556,952 seconds

So age in years = elapsed seconds ÷ 31,556,952.

Does the choice matter? A little. Using 365.25 instead of 365.2425 makes each year 0.0075 days longer. Over thirty years that adds up to about 0.22 days, which shifts the age by roughly 0.0006 years. In other words, the choice of year shows up in the fourth decimal place.

Step three: how fast does each digit move?

Once you know a year is 31,556,952 seconds, the speed of every decimal place follows directly. One unit in the nth decimal place is 10⁻ⁿ years:

At ten decimals the last digit changes about 317 times per second, far faster than any display can show; a 120 Hz screen catches roughly one change in three. What you see is a digit that is a blur with the occasional readable frame, which is the effect people want from that setting.

At six decimals the last digit is a steady tick every half-minute or so. At two, the number is effectively static and changes while you are not looking.

Which digits are actually true?

Here is the honest part. The arithmetic is exact, but the input is not.

Time of birth. Most people enter a birth date, not a birth moment. If the app assumes midnight and you were born at 3 pm, the counter is off by 15 hours, which is 0.0017 years. That error lives in the third decimal place, and everything after it is precise arithmetic on an imprecise starting point.

Time zone. Midnight where you were born is not midnight where you are now. This is another few hours of uncertainty, again in the third decimal.

Leap seconds. UTC has inserted 27 leap seconds since 1972, and your phone’s clock generally smooths over them. The total effect is under a millionth of a year, so it appears around the seventh decimal. It is real, but it is smaller than the birth-time error by several thousand times.

So a ten-digit counter is, strictly, about three digits of information about your birth and seven digits of very accurate information about how long ago you last looked at it. That is not a flaw. Nobody sets ten decimals for accuracy; they set it because they want to watch time move. But it is worth knowing which part of the number is which.

Formatting the number

A thirty-year-old at ten decimals needs twelve digits plus a point, thirteen characters. In a proportional font the number wobbles as digits change width, so counters use tabular figures, where every digit takes the same space.

Seeing it for yourself

TimeBorn does the calculation above, using the 365.2425-day year, and lets you choose from 2 to 10 decimals on the wallpaper (2 to 7 on the widget, since widgets update in steps). The precision guide helps you pick a setting, and the home page has a counter you can scroll to your own age to see what each precision looks like in motion.