Trail Bike Tips: Clean Landings and the Real Distance Limit

Updated October 2026

Trail Bike hands you a motorbike that rides itself and asks you to look after one thing: the angle of the bike while it is in the air. Every run builds a new course, every jump wants a different correction, and the bike never stops getting faster, so a run ends when your reading of the landings runs out. This guide explains how the jumps are built, how the lean controls really behave, and where the distance limit comes from.

What you control and what you do not

You cannot brake or accelerate, and your score is simply the distance covered in whole metres. On the ground the bike follows the shape of the course exactly, and the lean controls do nothing. Only in the air do they turn the bike.

There are two controls. Holding the left button (◀) tips the nose up; holding the right button (▶) tips the nose down. You do not have to hit the round buttons precisely: any touch on the left half of the play area counts as left, and any touch on the right half counts as right. On a keyboard, the arrow keys or A and D work the same way. The small dial between the buttons shows the bike's current pitch.

How a course is built

The course is generated fresh for each run, so memorising it is impossible. It alternates between rolling ground and jumps. The rolling sections are shaped so that, at the speed you are doing there, the ground never curves away faster than gravity pulls the bike down, which means they almost never lift you. The jumps are where the game happens.

A jump has three parts: a kicker ramp that ends in a lip, a gap, and a landing slope on the far side. The bike leaves the lip carrying the angle of the ramp, flies along an arc that does not depend on anything you press, and comes down on the landing slope. In our simulation there were about 10 to 11 jumps per kilometre, and the time in the air ranged from about half a second to just under a second, with a median of three quarters of a second.

The first 300 metres are a warm-up: small kickers whose landings line up with the ramp, so you can ride them without touching anything. After that the jumps come in three kinds, in roughly these shares:

• Forward jumps (about half). The landing slope is much steeper than the kicker. Arriving at the take-off angle means landing nose-high, so you need a firm press of ▶.
• Matched jumps (about a third). Long, high flights onto a slope that already points the same way as the ramp. The right move is to leave the bike alone; holding a button through the whole flight turns you far past the slope.
• Uphill jumps (about a fifth). The far side rises, so the ground meets you nose-down. You need to lift with ◀.

The landing rule

When the wheels touch the ground, the game compares the bike's pitch with the slope of the ground at that exact point. The allowed difference starts at about 34 degrees and narrows steadily from 300 metres onwards, reaching about 24 degrees at 3.3 kilometres, where it stays. Outside the allowance, in either direction, you crash. The judgement is made at the moment of contact on a fixed physics clock, so a slow phone and a fast phone see exactly the same result for the same inputs.

Why no single habit works

Because the three kinds of jump need opposite answers, any one fixed habit fails on most of them. We rode every jump between 300 metres and 5 kilometres on 40 generated courses three ways. Doing nothing landed cleanly on 33 percent of them, holding ▶ for the whole flight on 34 percent, and holding ◀ on 18 percent. Over full runs on ten courses, holding ▶ ended the run after a median of about 720 metres, doing nothing after about 1,130 metres, and holding ◀ after about 360 metres. A fixed 0.2-second tap of ▶ at every take-off did a little better, but did not pass about 2,150 metres on any of the ten courses.

The habit that does work is reading each landing. As you climb a kicker, look at where the arc will come down and compare that slope with the ramp you are on. Steeper downhill: press ▶. Roughly the same: hands off. Rising: press ◀. You may press before the lip; the lean starts working the instant the wheels leave the ground.

How the lean really behaves

Holding a button builds up spin, and letting go does not stop it instantly: the spin fades over roughly a third of a second, and the bike keeps turning a little while it does. Held continuously, the spin tops out at about 140 degrees per second, so a full-second flight with a button held can turn the bike by roughly 100 degrees. That is why holding through the long matched jumps is so dangerous.

The steadiest technique is a firm press followed by an early release. Let go when the dial is still a little short of the landing slope and let the fading spin carry it the rest of the way. Correcting at the very last moment rarely works, because the spin you add then has no time to build.

Crashes, lives and the blink

You start with three lives. A crash plays a 1.5-second tumble, then puts you back on the ground at the spot where you fell, already lined up with the slope. For 1.2 seconds afterwards the bike blinks, and any landing during the blink is forgiven: the bike is simply set straight on the ground. Losing the third life ends the run. There is no clock, so a crash costs you a life and a moment, not time from a timer.

The real distance limit: speed

The bike starts at 16.5 metres per second, about 59 km/h. After 300 metres it gains 4 metres per second for every kilometre, with no top speed: about 69 km/h at 1 km, 98 km/h at 3 km and 127 km/h at 5 km. The screen always shows the same stretch of course, about 24 metres ahead of the bike, whatever the size of your phone.

Speed matters because a jump's length is speed multiplied by time in the air. At the start, every landing is on screen before you leave the lip. Beyond about 3 kilometres the longest flights begin landing further ahead than the screen shows at take-off, and the faster you go, the later the landing slides into view and the less time you have to turn the bike. Eventually that window becomes shorter than the time the bike needs to rotate, and no amount of skill can keep up. That is what ends a good run.

In our simulation, a reading-the-landing controller with a human-like reaction delay of 0.15 seconds and a few degrees of error reached between about 5,900 and 8,300 metres, and almost all of its crashes came beyond 5 kilometres. A slower controller with a 0.25-second delay reached about 3,900 to 6,700 metres. Even a controller with no delay and perfect aim, limited to what is on screen, stopped somewhere between about 9,500 and 20,000 metres depending on the course. There is no common ceiling: where your run ends depends on how well you read the jumps.

A practice plan

1. Ride the first 300 metres without touching anything and watch how the bike follows the arc off each kicker.
2. On the next few jumps, before each lip, say out loud which of the three kinds it is: forward, matched or uphill.
3. Once the call is automatic, work on the release: press firmly, let go early, and check the dial against the landing slope just before contact.
4. When you crash, notice which kind of jump it was. Crashing on matched jumps means you are holding too long; crashing on forward jumps past 3 kilometres usually means you committed too late.

Your best distance is saved on your device and can be submitted to the Hall of Fame from the game-over card.