How to run an OSRS tile race for your clan. Board layouts, snake and ladder placement, dice rules, team sizes, task lists, and how a tile race differs from bingo.
Bingo is the format every OSRS clan tries first. The tile race is the one they run second, once they have learned that a 5x5 grid lets a strong team disappear over the horizon on day one while everyone else quietly stops logging in.
A tile race fixes that with one structural change: instead of picking tiles freely from a grid, teams move along a path, one tile at a time, and cannot skip ahead. That single rule keeps the field bunched, makes every completion feel like progress, and turns the last night into an actual race rather than a formality.
This guide covers what a tile race is, how it differs from bingo, the board layouts that work, how to place snakes and ladders without ruining the event, and the rules you need to publish before you start.
| Bingo | Tile race | |
|---|---|---|
| Board shape | Grid (3x3 to 7x7) | Path of numbered tiles |
| Tile choice | Any tile, any order | Only the next tile |
| Win condition | Lines, blackout, or points | First to the final tile |
| Catch-up | None — leads compound | Built in, if you add snakes |
| Best for | Mixed clans, flexible schedules | Competitive teams, fixed windows |
| Feels like | A checklist | A race |
| RNG tolerance | Low — a bad tile is skippable | High — a bad tile blocks you |
The critical trade-off is in the last two rows. In bingo, an unlucky drop-RNG tile is an annoyance you route around. In a tile race, it is a wall — your team sits on tile 14 waiting for a pet while another team strolls past. That is either the best drama of your event or the reason three people quit, and which one it is depends entirely on the rules you write.
Most clans that run both end up alternating: bingo for the casual, come-and-go events, tile race for the shorter and more competitive ones.
A single line of 30 to 50 tiles. Teams move one tile at a time. No branching, no dice.
Best for a first tile race. There is nothing to explain and nothing to argue about. The whole event is "complete tile N, move to N+1".
Recommended length: 30 tiles for a weekend, 50 for a full week.
The same path, plus two special tile types:
This is the format most clans mean when they say "tile race" now, and there is a reason: the catch-up mechanic is what keeps last place playing. It also generates the moments people talk about afterwards, which is most of the point of a clan event.
Recommended: a 50-tile board with 5 ladders and 4 snakes.
If you want dice in the mix as well, that variant has its own tuning problems — board size against roll cadence, in particular — and its own guide: OSRS snakes and ladders.
Teams roll a d6 (usually once per day, or once per completed tile) and move that many spaces, completing the tile they land on. Adds variance and a daily ritual.
The catch: with a daily roll, a team that logs in at the wrong hour loses a day. Publish a fixed roll window and stick to it, or use "roll on completion" instead of "roll per day".
Two or three routes that diverge and rejoin, each with a different flavour — a PvM branch, a skilling branch, a clue branch. Teams choose at the fork.
Excellent for mixed clans, because a team stacked with skillers can play to its strength. It is also the most work to balance, since branches of unequal difficulty are immediately obvious and immediately complained about. Only attempt this on your third or fourth event.
This is where tile races go wrong, and it is almost always the same three mistakes.
Mistake 1: a snake near the end. A team on tile 47 of 50 hits a snake back to tile 22 and the event is emotionally over for them. Never place a snake in the final 20% of the board. If you want late-game tension, use a hard tile, not a setback.
Mistake 2: symmetrical snakes and ladders. If every ladder is matched by an equal snake, the net effect over a long event is zero and you have added variance without adding catch-up. Ladders should outnumber snakes and be slightly stronger. The point is to compress the field, not to randomise it.
Mistake 3: huge jumps. A ladder that skips 15 tiles skips 15 tasks, which is 15 pieces of content your members do not get to play. Keep jumps to 3–6 tiles. The feeling of a ladder matters more than the distance.
A layout that works reliably on a 50-tile board:
| Type | Tile | Effect |
|---|---|---|
| Ladder | 7 | → 12 |
| Snake | 15 | → 10 |
| Ladder | 19 | → 25 |
| Snake | 28 | → 23 |
| Ladder | 31 | → 36 |
| Snake | 34 | → 29 |
| Ladder | 38 | → 43 |
| Snake | 41 | → 37 |
| Ladder | 44 | → 47 |
Note the shape: ladders and snakes cluster in the middle third, the last six tiles are clean, and no jump exceeds six spaces.
The tile list matters more in a race than in bingo, because teams cannot skip. Three rules follow from that:
Cap the RNG. In bingo, a "get any boss pet" tile is a fun lottery. In a tile race it is a roadblock that can hold a team for the entire event. Either avoid pure-RNG tiles entirely, or pair every one with an alternative: "obtain any boss pet or 500 total boss KC". The alternative is what stops the race from becoming a coin flip.
Front-load the easy tiles. The first five tiles should take minutes, not hours. Teams that see movement in the first evening stay engaged; teams stuck on tile 1 do not come back on day two.
Escalate, but not monotonically. Difficulty should trend upward with a few deliberate breathers around tiles 25 and 40 — right where fatigue sets in. A wall of five hard tiles in a row is where clans stall out.
For task content, the 60+ OSRS bingo tile ideas list works directly here; just sort it by difficulty and lay it along the path instead of into a grid. Our free board generator can produce a balanced task set you then arrange in race order.
Tile races generate a specific set of disputes that bingo does not. Answer all of these in writing, in advance:
The single most important one is the approval-speed rule. In a race, admin latency is scoring latency. If your admin team sleeps in a European time zone and half your clan plays from Australia, "cannot work ahead" quietly hands the event to Europe. If your clan is spread out, either allow working ahead by one tile, or commit to an approval rota.
| Clan size | Teams | Board length | Event length |
|---|---|---|---|
| 10–20 | 2 teams of 5–10 | 25–30 tiles | 3–4 days |
| 20–40 | 4 teams of 5–10 | 40 tiles | 5–7 days |
| 40–80 | 6–8 teams of 6–10 | 50 tiles | 7–10 days |
| 80+ | 8+ teams, capped at 10 | 50 tiles + branches | 10–14 days |
Teams smaller than four stall whenever someone goes offline; teams larger than ten leave people with nothing to do. Five to eight is the reliable range.
Length is the more common error. A tile race is more intense than a bingo — teams feel the pressure of the next tile constantly — and burnout arrives faster. A tile race should be shorter than a bingo covering the same content. If you are unsure, cut two days.
Mechanically, a tile race needs less bookkeeping than a bingo — one position per team instead of a grid of completions — but it needs it faster, because every team is blocked on their current tile until it is approved. A 12-hour approval delay in bingo is mildly annoying; in a tile race it is 12 hours of a team having nothing to do.
That is the practical argument for hosting it rather than running it in Discord: submissions land in a queue, approval moves the team immediately, and the position update posts to Discord without anyone editing a pinned message. An OSRSHub server runs custom boards with teams, structured screenshot submissions, admin approval, and automatic Discord updates — the same machinery a bingo uses, arranged as a path. It is $12.10 a month and live in under a minute.
Want to sketch the task list first? The board generator is free, needs no account, and exports a PNG you can lay out as a race path.
A clan event where teams move along a numbered path of tasks, completing one tile at a time to advance. Unlike bingo, teams cannot skip tiles, so the field stays close and the first team to reach the final tile wins.
Shorter than a bingo covering similar content — a tile race applies constant pressure and burns people out faster. 30 tiles over 3–4 days suits a small clan; 50 tiles over 7–10 days suits a large one.
On a 50-tile board, about 5 ladders and 4 snakes. Ladders should slightly outnumber and outweigh snakes so the mechanic compresses the field rather than just adding randomness, and no snake should sit in the final 20% of the board.
That is your call, but publish it in advance. Banning it is cleaner but makes admin response time part of the scoring, which penalises teams in time zones your admins are asleep in. If your clan is spread across regions, allow working one tile ahead or commit to an approval rota.
Often yes. With 10–20 players a bingo grid finishes too quickly and one strong player can carry it. A tile race with a 25–30 tile path keeps a small clan engaged for several days and keeps teams within sight of each other.
A tile race is the natural second event for a clan that has run one bingo and noticed the runaway-leader problem. Keep the first one simple: a straight 30-tile path, front-loaded, no dice, a handful of ladders, and a clearly published approval rule.
When you are ready to build the task list, start with the tile ideas library, lock the rules down with the verification guide, and wire up announcements with the Discord integration guide.