On this page
How to play Curb Hop
Your bike rides to the right by itself, and you choose when to hop. Hit an obstacle or come down inside a pit and the ride is over. Your score is the distance in meters, and nothing else adds points.
Controls
| Mouse | Touch | Keyboard | |
|---|---|---|---|
| Hop | Left button | Press the scene or the big button under it | Space, ↑ or Enter |
| Hop higher | Hold the button | Hold your finger down | Hold the key |
| Start, or ride again | Press and release | Press and release | Press and release the key |
| Pause | Pause button | Pause button | P or Esc |
- The ride starts when you let go, and the press that starts it does not hop.
- On a phone, dragging scrolls the page before and between rides, but not during one. A press that moves 10 pixels or more does not start a ride.
- Keys: a held key hops once, and Space does not scroll the page. Leaving the tab pauses the ride, and after you resume the bike waits 600 ms.
The two hops
Hold length decides the hop. Heights use the game’s units, where 32 units are 1 meter on the distance counter.
- Short hop: a press of up to about 125 ms. The wheels peak 57 units up, and you stay in the air for 492 ms.
- Long hop: a hold of 300 ms or more. The peak is 135 units and the flight lasts 825 ms.
- In between: the hop jumps up fast. A hold of 16 game steps (about 133 ms) already peaks at 107.
What ends a ride
| Obstacle | Hit box (units) | Your wheels must be |
|---|---|---|
| Cone | 16 wide, 22 tall | at least 18 up while you pass |
| Crate | 26 wide, 40 tall | at least 36 up |
| Barrier | 26 wide, 92 tall | at least 88 up |
| Beam | 120–160 wide, underside 125 up | at most 77 up |
| Pit | 62, 90, 150 or 230 wide | back on the road past the far edge |
The bike’s hit box spans 4 to 48 units above its wheels, hence 18 (22 − 4) and 77 (125 − 48). Any hit ends the ride. There are no extra lives.
Worked out from the game’s motion: a tap clears the 62, 90 and 150 pits wherever they appear. The 230 pit is a hold hop until about 950 m. After that a tap works too.
Tips for longer rides
- Start with plain taps. The first 180 m hold only pits, and a tap works across about half a second. A dotted arc marks the first pit and cone of your first three rides, and your first ten crashes at tap spots and ten at hold spots show the hop you needed.
- Commit. Our checks cover taps of 8 to 120 ms and holds of 300 to 450 ms. A hold in between is unchecked and gives a hop between the two.
- Ride under beams. A tap stays under the 77 limit, so a lone beam needs no press. With a cone under the beam, tap.
- Use the buffer and the grace. A press in the last 100 ms before landing is kept. At a pit you can still hop 75 ms after the road drops away.
- Look ahead. You see 14.4 m ahead: 1.5 s of road at the start, 0.85 s at top speed.
- Chase the flag. It marks your best distance.
Our numbers
Computed rows use the game’s formulas. The rest come from our test suite, with the date and count; How we test explains each check.
How the ride gets harder
There is no difficulty menu; the road gets harder with distance. Computed for a ride that never crashes; the real gap is 1 to 1.5 times the one shown.
| Distance | Time | Speed | Gap (s of riding) | New on the road |
|---|---|---|---|---|
| 0 m | 0 s | 34 km/h | 2.0 | Starter pits only |
| 180 m | 18 s | 37 km/h | 1.35 | Cones, small pits, then crates from 260 m |
| 330 m | 32 s | 40 km/h | 1.23 | Barriers, medium pits; beams from 400 m, large pits from 500 m |
| 450 m | 43 s | 42 km/h | 1.14 | Two-part groups, such as a cone under a beam |
| 1,500 m | 118 s | 61 km/h | 0.45 | Top speed. The gap stopped shrinking at 1,300 m |
What the course checker enforces
A group goes onto the road only after the checker finds presses that clear it. After 8 failed tries, the road gets one second of empty road. The limits, from the code:
- Window: each press has a window of at least 133 ms (16 steps of 1/120 s) where any moment works, for every hold length of its kind.
- Reaction: no press is needed sooner than 350 ms after a group comes into view.
- Recovery: the next window opens at least 125 ms after the planned landing.
- Hit boxes sit inside the pictures (checked 25 October 2026): 1 to 4 units in for obstacles, and 7, 4 and 7.5 for the bike’s sides, bottom and top.
What we measured
- Timing noise, 25 October 2026: the checker’s presses for 100 Free courses (to 2,000 m) and 60 Dailies (to 3,000 m) were replayed 20 times each, every press moved by up to 60 ms either way. Result: 0 deaths in 3,200 replays.
- Bots, 18 October 2026: 300 courses, 5 rides per bot on each, capped at 9,000 m. They follow the checker’s press plan with a timing spread (standard deviation) of 70 ms for Loose, 100 ms for Late and 30 ms for Sharp, and Late also averages 60 ms late. They press the wrong kind 10%, 10% and 1% of the time. They are not people.
| Bot | Median ride | Middle 80% | Past first 3 groups |
|---|---|---|---|
| Loose | 38.5 s (about 400 m) | 23.2–69.3 s | 99.9% |
| Late | 22.5 s (about 220 m) | 8.6–34.3 s | 83.5% |
| Sharp | 141.6 s (about 1,900 m) | 63.5–313.0 s | 100% |
On 25 October 2026, 30 courses with 5 rides per bot gave medians of 39.6, 22.2 and 132.8 s. Distances convert time with the speed formula.
Not measured or not passed. Without player data we give no finish rates. A 60-second top-speed run on 22 October 2026 (Chromium on a computer, 390 px wide, CPU slowed 4 times) had 95% of frame gaps at 16.8 ms or less and 1.47% of frames dropped. It also had 6 long tasks over 50 ms (the longest 70 ms), so it failed our old check. Later speed checks ended “not judged” because the test machine was too busy. We have no real-phone numbers.
Daily course and records
- Fixed by the date: the whole course. Your device’s date picks the course, so everyone on the same date rides the same one; it changes at your midnight. We built the 60 Daily courses from 25 October to 23 December 2026 before and after code changes on 25 and 29 October and hashed every obstacle and press plan to 3,000 m. All 60 matched both times.
- Three tries: each starts at the beginning of the same course. A try counts once you start riding, and a reload does not give it back.
- Recorded: after the third try (or when the page returns, if you reload during it), your best distance, with that try’s close calls, top speed and time, and the tries used.
- Where: in this browser, on this device. Free play keeps your plays and best distance.
For streaks and the rules all Dailies share, see the Daily page.
Frequently asked questions
Can I get an impossible course?
The generator places a group only after its checker finds presses that clear it within the limits above. On 25 October 2026, 160 courses replayed 20 times each with timing noise gave 0 deaths. Passable is not easy: the Late bot died within the first three groups in 16.5% of its rides.
Why won’t the ride restart right after a crash?
The result card appears 480 ms after the crash, and a press in the next 700 ms does not start a new ride. That keeps a late tap from wiping your result and the hop you needed. A press held since before the crash never restarts the ride: let go and press again.
What counts as a close call?
In the air, your hit box passing within 8 units of the top of a cone, crate or barrier, or of a beam’s underside. Landing within 12 units of a pit’s far edge counts too.
Last updated: November 2, 2026.