How long should an OSRS bingo last? Match duration to board size and format, spot the day-three engagement drop, and know when to end an event early.
Ask a clan why their last bingo fizzled and you will hear about the board, the tiles, or one guy who did not submit screenshots. Ask what day people stopped logging in and you will usually get the same answer: day four.
Duration is the most consequential decision in a clan event and the one made most casually. It is typically set by the calendar — "let's run it over the long weekend" — rather than by the board, and then the board is stretched or crammed to fit. That is backwards, and it produces the two classic failures: an event that is over by Saturday lunchtime, and an event that technically runs for two weeks but that everyone stopped caring about on Tuesday.
| Board | Tiles | Duration | Format note |
|---|---|---|---|
| 3x3 | 9 | One evening, 2–4 hours | Sprint |
| 5x5 | 25 | 48 hours, Friday night to Sunday night | The default |
| 5x5 (relaxed) | 25 | 5–7 days | For casual clans with low daily playtime |
| 7x7 | 49 | 10–14 days | Needs a mid-event hook |
| Tile race, 30 tiles | 30 | 3–4 days | Every team does every tile |
| Snakes & ladders 7x7 | 49 | 1–2 weeks | ~14 rolls to cross |
If you take one number away: a 5x5 over a weekend is the format that works most reliably for most clans, and if you are unsure, run that.
Clan events do not decay linearly. They follow a fairly consistent shape:
Day 1 — peak. Everyone is online, the board is fresh, easy tiles fall fast. Expect your highest participation of the entire event in the first six hours.
Day 2 — the real event. Still high. Teams have a strategy, the medium tiles get worked, the leaderboard starts to mean something. This is where a well-designed event lives.
Day 3 — the drop. Participation falls noticeably. The easy tiles are gone, what remains is grindy, and the leaderboard has usually separated enough that some teams can see they will not win.
Day 4+ — the committed few. Only the top teams and the genuinely obsessed are still playing. Everyone else is nominally in the event and functionally out of it.
Final 12 hours — a partial spike, but only if the result is still in doubt.
That last condition does more work than it looks. The final-night surge only happens if teams can see that the result is close, which means a leaderboard that updates while they play. A standings post edited by hand every evening cannot produce it, because by the time the numbers are current the night is over. This is one of the few places where the tooling genuinely changes player behaviour rather than just saving admin time — a live board on an OSRSHub server keeps the last night competitive in a way a pinned message cannot.
Two conclusions follow, and they are the whole point of this article.
First: most of your event happens in the first 48 hours regardless of how long you schedule it. A 14-day event does not get 7× the engagement of a 2-day one. It gets roughly the same first 48 hours, plus a long tail of decreasing activity.
Second: length is not generosity. Clan leaders extend events to be inclusive — "so people who work weekends can join" — and then watch the extra days go unused. If you genuinely need to include people with awkward schedules, a shorter event on a better-chosen weekend usually serves them better than a longer one they still miss.
The real constraint is completion percentage. A good event ends with the winning team having completed roughly 40–60% of the board. Under 40% and it feels like nobody got anywhere. Over 80% and the last stretch is a formality, because everything interesting has been done.
Work backwards from that:
Worked example. A 25-tile board, average 60 minutes per tile, target 12–13 tiles completed. A team playing 3 hours a day completes about 3 tiles a day. 13 ÷ 3 ≈ 4.3 days.
So that board wants a long weekend — Thursday evening to Monday night — not a two-week run and not a 48-hour sprint.
Run the same maths with 8 hours a day and you get under two days, which is why a hardcore clan and a casual clan need genuinely different schedules for the identical board. Duration is not a property of the board. It is a property of the board and the clan.
Bingo (grid). Teams choose tiles freely, so they front-load the easy ones and the completion rate is high early. Bingo tolerates being short better than any other format — a 3x3 evening bingo is a genuinely complete event.
Tile race. Every team completes every tile in order, so total time is the sum of all tile times, not a subset. A 30-tile race is 30 tiles of work, not 15. Races need to be shorter in tile count than a bingo covering the same period. See the tile race guide.
Snakes and ladders. Teams complete only the tiles they land on — roughly one in 3.5 — so a 49-tile board is about 14 tasks. But if you gate rolls to one per day, you have just set a 14-day minimum by accident. The snakes and ladders guide covers this trap in detail.
The general rule: the more tiles a team must complete, the longer the event; the more tiles they may skip, the shorter it can be.
Long events are not always wrong. They work when at least one of these is true:
If none of those is true, the extra days are decoration.
This is the option almost nobody uses and it is often right.
If your event is scheduled for ten days and by day five one team has an unassailable lead and participation has collapsed, you can end it. Announce the result, pay the prize, and start planning the next one while people still remember enjoying this one.
The instinct is that ending early is unfair or looks like failure. In practice, a clan that ends an event at its natural peak and immediately announces the next one has far more momentum than one that lets a dead event run its full course. A five-day event that felt alive beats a ten-day event that spent five days as a graveyard.
Publish the possibility in your rules so it is not a surprise: "The event may be closed early if the result is mathematically settled. The published prize is paid in full regardless." The second sentence is what makes it acceptable.
Start on a Thursday or Friday evening, not a Saturday morning. Friday evening captures a full weekend plus the anticipation of Friday afternoon. Saturday-morning starts lose the entire first evening to people who did not realise it had begun.
End on a Sunday evening, not a Monday. The final push should land when people are actually online.
State a time zone. Every time. "Ends Sunday at 22:00 UTC" prevents an entire category of argument.
Give at least a week of notice. Clans need to schedule around events, and an announcement two days out means the people with plans simply do not participate.
Avoid major game updates and big community events if you can see them coming. Competing with a league launch is a losing game.
For a standard 5x5 board and a typical clan, 48 hours from Friday evening to Sunday evening. Use a single evening for a 3x3, and 10–14 days only for a 7x7 that no team could finish. The right length is the one where the winning team completes 40–60% of the board.
Because engagement drops sharply around day three: the easy tiles are gone, what remains is grindy, and the leaderboard has separated enough that some teams can tell they will not win. Milestone and participation prizes are the most effective counter.
Usually not. Most engagement happens in the first 48 hours regardless of total length, so extra days tend to go unused. A shorter event scheduled on a better weekend generally includes more people than a long one they still miss.
Yes, and often you should — if the result is settled and participation has collapsed, ending at the natural peak preserves momentum for the next event. Publish the possibility in your rules in advance and commit to paying the full prize regardless.
Estimate average time per tile, estimate realistic daily play hours per team, and target the winning team completing about half the board. A 25-tile board at an hour per tile with teams playing 3 hours a day works out at roughly four days.
Set the duration from the board and your clan's real playtime, not from the calendar. Then front-load the easy tiles so day one feels fast, and put something on the schedule for day three — a milestone prize, a bonus window, anything — to interrupt the drop before it happens.
If you are still designing the board, the setup guide covers sizing and balance, and the templates page has complete grids sized for each duration in the table above.