Download on the App StoreGet it on Google Play

Wiki

Chrome Dino Scoring System

How Points Are Earned and Tracked in the T-Rex Runner

Updated WikiFirst published
Chrome Dino Scoring System
The Jumping Dino gameplayiOS + Android

Short answer

Short answer

Short answer: Chrome Dino score is based on distance traveled. The display starts with five digits, but current Chromium code expands the score display after 99,999 instead of resetting there.

The Chrome Dino scoring system is simple: you earn points by covering distance. Each update adds currentSpeed × deltaTime / msPerFrame to distance. DistanceMeter converts that distance to score with a coefficient of 0.025 and rounds the result. There are no style bonuses or obstacle-specific rewards. Under nominal 60 FPS timing, normal mode produces about 9 points per second at the starting speed of 6 and 19.5 points per second at the maximum speed of 13. The display begins as a zero-padded five-digit counter and expands after 99,999. The HI value is synchronized through Chrome's profile-facing errorPageController after a run ends, not through page localStorage. The original game has no public leaderboard. The Jumping Dino adds local browser score history, shareable challenges, daily and all-time browser leaderboards, and app progression; its app Multiplayer mode uses nine AI-controlled ghost dinos rather than live-player matchmaking.

01

Score Calculation Details

Runner.update accumulates distance from current speed and elapsed time. DistanceMeter.getActualDistance then rounds distance × 0.025. At normal-mode speed 6 and nominal 60 FPS, that is about 9 score per second, or one point every 0.11 seconds on average. At the speed-13 cap it is about 19.5 score per second, or one point every 0.051 seconds. Score is therefore distance-based and increases faster as the runner accelerates.

02

Personal High Score and Persistence

Current Chromium initializes the high score from the user's Chrome profile through initializeEasterEggHighScore. On game over, if the run's distance exceeds the stored best, the runner calls updateEasterEggHighScore. The in-page TypeScript has no localStorage key for this value, and it updates HI after the collision rather than at the moment the current score passes the previous best. The Jumping Dino website separately keeps browser run history locally and can submit an optional display name and score to its public leaderboard.

03

Score Milestones and Their Significance

Only two score milestones are explicit in the current code: every 100 points triggers the score-achievement flash and sound, and positive 700-point multiples can trigger the temporary color inversion. Pterodactyl availability is gated by speed 8.5, which works out to roughly 450 score from the normal desktop start under nominal timing. The normal speed cap is reached around 1,660 score under the same assumptions. Other labels such as beginner, advanced, or elite are subjective community shorthand, not Chromium rules.

Topicschrome dinoscoringpointshigh scorescore system

Play while you read

Play now or get the full game

Play the browser runner, or get the mobile app with Campaign, Infinite mode, dinosaur progression, and AI ghost races.

Sources & References

Last verified:

LEVEL UP

Love the Classic? Meet the Evolution.

The Jumping Dino takes everything you love about the Chrome dino game and turns it into a full adventure.

Campaign + Infinite + Multiplayer
Rescue eggs across 5 eras
Hatch dinos, build the Sanctuary
iOS & Android; 2 offline modes

3M+

Downloads

4.3★

Google Play rating

9.28K

Reviews

Love the Classic? Meet the Evolution.
Download on the App StoreGet it on Google Play

Answers

Frequently Asked Questions

The runner accumulates distance from speed and elapsed frame time, then `DistanceMeter` multiplies that distance by 0.025 and rounds it. Under nominal 60 FPS timing, normal mode earns about 9 points per second at speed 6 and 19.5 points per second at the speed-13 cap.

Yes. The runner receives an initial high score from Chrome and writes a new best through `errorPageController` to the user's Chrome profile after the run ends. The TypeScript game does not use page `localStorage` for this.

No. Points are awarded purely based on distance traveled/time survived. There are no bonus points for style, obstacle types cleared, or specific techniques. The score is simply a measure of how long you've stayed alive.

The score starts as a zero-padded 5-digit number, but current Chromium code expands the display after the calculated distance passes 99,999. It should not be described as restarting at that point.

Keep exploring

Related Pages