Chrome Dino Max Score Data (What Players Hit)
Chrome dino max score data has one number everyone repeats: 99,999. Many sources call it the cap built into the game, the point where the counter rolls back to zero. The code says otherwise: the counter gains a sixth digit at 100,000 and only wraps after 999,999. Beyond the code, hard data is thin, so this piece sticks to what the source actually shows and labels every time figure as an estimate.
Key takeaways
- The Chrome Dino score counter starts at five digits and gains a sixth after 99,999; it only appears to wrap back to zero after 999,999.
- Speed rises from 6 to a fixed maximum of 13, reached at roughly 1,660 points (about two minutes) on a standard 60 Hz desktop screen.
- At top speed the score climbs about 19.5 points per second, so by our estimate 99,999 takes roughly 86 minutes of flawless play and 999,999 roughly 14 hours.
- Night mode starts every 700 points; pterodactyls only appear once speed passes 8.5, around 450 points.
- There’s no leaderboard in the original game, so “what players hit” can’t be measured; record claims are self-reported.
The 99,999 myth
The Chrome offline T-Rex Runner, built by Chrome’s UX team (including Sebastien Gabriel, Alan Bettes and Edward Jung) and added to Chrome in 2014, tracks distance as a number in the game state and converts it to a score. The display starts at 5 digits. When the score passes 99,999, the distance meter adds a sixth digit, so the counter keeps climbing toward 999,999. It can only grow once, so past 999,999 it shows just the last six digits and appears to roll over.
The run itself doesn’t stop at 99,999 or at 999,999. The distance keeps counting in memory, and only the displayed value wraps. From the player’s perspective, the counter seems to start over while the obstacles keep coming at full speed. There’s no “you win” condition at all.
This digit logic is in the distance-meter code of the original Chromium runner, the same code that powers our build of the Chrome Dino game.
How long does 99,999 actually take?
The game’s own constants let you estimate it. The score is the distance run in pixels multiplied by 0.025. Speed starts at 6 pixels per frame and gains 0.001 every frame until it hits the cap of 13. Distance is scaled to a 60 fps frame, so at top speed the score climbs about 13 × 60 × 0.025 ≈ 19.5 points per second.
Speeding up from 6 to 13 takes 7,000 frames, about 117 seconds at 60 fps, and covers roughly 1,660 points. After that the rate is constant. Our estimates for a run that never crashes:
| Score | Estimated time (60 Hz, no crash) |
|---|---|
| 700 (first night) | about 1 minute |
| 1,660 (top speed) | about 2 minutes |
| 10,000 | about 9 minutes |
| 50,000 | about 43 minutes |
| 99,999 | about 86 minutes |
| 999,999 (display wraps) | about 14 hours |
These are estimates computed from the code, not measured runs. They ignore the few seconds of intro at the start. The game also pauses when the tab loses focus, so real elapsed time can be longer. On a higher refresh-rate screen the speed-up happens per frame, so top speed comes sooner, but the score rate at top speed is the same. Narrow mobile screens start slower too.
The day-night cycle
One of the original game’s nice touches is the day-night cycle. Every time the score hits a multiple of 700, the colors invert to a dark “night” with a moon and stars. Going by the code, night lasts about 12 seconds before the screen fades back to day.
For long runs, the cycle is the most visible progress marker. At top speed a new night arrives roughly every 36 seconds by our estimate, which gives a marathon run a steady visual rhythm.
What players hit: why there’s no real data
The original game has no leaderboard and doesn’t save scores anywhere. The high score sits in memory and resets when the page reloads. There’s no central dataset of player scores, so any “typical score” breakdown you see online is guesswork.
What the code can tell you is how far a given run went. Using the estimates above:
- Under about 450: the run ended before pterodactyls could appear.
- About 1,660 and up: the player survived the whole speed ramp and played at the maximum speed.
- Over 99,999: the sixth digit appeared, which means roughly an hour and a half of play without a single crash.
- Very high scores reached quickly: not possible by normal play. Scripts, bots and edited game code can push the counter much faster, and those don’t count as human play.
We don’t host a leaderboard and don’t validate score claims. For community-tracked attempts, see the world records roundup.
Why the counter starts at five digits
The five-digit start is set by a single constant in the distance-meter code (a maximum of 5 digit units). It reads like an arcade-style score display and fits in the corner of the small canvas, though we haven’t seen the team explain the choice.
A 5-digit display would top out at 99,999, which is where the myth comes from. The code already handles it: the first time the score passes 99,999, the meter adds a sixth digit, and it only wraps after 999,999.
Speed scaling and the “peak speed” plateau
The dino’s running speed in the original game rises every frame until it reaches the maximum of 13. After that point, obstacles keep coming but the speed doesn’t get higher. That’s why marathon runs are possible at all. Our speed cap explainer covers the details.
On a standard 60 Hz desktop screen, the switch to peak speed happens at around 1,660 points. From then on, the game is about as hard as it will ever get. Obstacle types and gaps are randomized, but nothing in the code makes them harder over time once speed is maxed.
The pterodactyl variable
Pterodactyls, the flying obstacles, can only spawn once the speed passes 8.5. By our estimate that’s around 450 points. After that, each new obstacle is picked at random from small cacti, large cacti and pterodactyls, so they don’t get more common as the score rises.
On desktop they fly at three heights. Low birds must be jumped. Middle birds can be ducked under with the Down key. High birds pass over a running dino, so you can ignore them. Mobile uses only the low and high heights. Reading the height fast enough to commit to a jump, a duck or nothing is a big part of the skill in long runs.
Holding the jump key
One quirk that comes up in score discussions: the code has no cooldown between jumps. If you hold Space, keyboard auto-repeat makes the dino hop again almost as soon as it lands. That isn’t a cheat, just input timing, and it doesn’t break the game. Nonstop hopping also won’t save you from every obstacle, especially mid-height pterodactyls.
Whether bunny-hop runs count as “legitimate” is up to whoever is keeping score. Either way, the score display works the same.
What “world record” actually means here
No central leaderboard exists for the original Chrome offline T-Rex Runner. There’s no Google-sanctioned ranking. The “world record” claims that circulate online are user-submitted, sometimes with screenshots, sometimes with video. Since 99,999 can be passed and the counter keeps going, there isn’t a final score to chase, and no definitive record-keeper exists.
Frequently asked questions
What is the maximum score in Chrome Dino?
Not 99,999, despite how often that figure is repeated. The score display starts at 5 digits and gains a sixth after 99,999, so it can show up to 999,999. Past that it shows only the last six digits, so it appears to roll over while the run continues.
How long does it take to reach 99,999 in Chrome Dino?
By our estimate from the game’s code, about 86 minutes of crash-free play on a standard 60 Hz screen. The game reaches top speed at about 1,660 points, then adds roughly 19.5 points per second. It pauses when the tab loses focus, so real time can be longer.
Does the Chrome Dino game get faster forever?
No. Speed starts at 6 and stops at a maximum of 13, reached at roughly 1,660 points on a 60 Hz desktop screen. After that, the game stays at the same top speed for the rest of the run.
Is there a leaderboard for Chrome Dino?
Not in the original Chrome version. The high score is kept in memory only and resets when you reload the page. Record claims online aren’t centrally validated, and our site doesn’t host a leaderboard.
What happens when you reach 99,999?
The displayed counter gains a sixth digit and shows 100000, and the game carries on at top speed. There’s no “you win” screen. The game just keeps generating obstacles until you hit one.
The number, in context
99,999 is easy to memorize, but it isn’t a limit. By our estimate it’s about an hour and a half of perfect play. For most players, the score that matters is the personal best. If you want to push toward bigger numbers, the Chrome Dino game at the top of this site runs the original Chromium runner code. For more on the score display, see our max-score explainer.
