How clan vs clan OSRS bingo works: one shared board, two clans, one scoreboard. Setup, scoring, roster imbalance, disputes and what to agree before you start.
Most clan bingo is a clan playing against itself. You split forty members into four teams, they race each other for a week, and the trash talk stays inside your own Discord.
Clan vs clan bingo is the other thing: two separate clans, one shared board, one scoreboard. Your clan against theirs, with bragging rights that leave your server.
It is a better event than internal bingo when it works, and a worse one when it does not — because every problem that internal bingo solves by having one person in charge comes back the moment two clans who do not report to each other have to agree on something. This guide covers what actually changes, how to set it up, how to score it fairly when the rosters are not the same size, and the five things to agree in writing before anyone kills a boss.
On the surface a two-clan match looks like ordinary team bingo with better branding. Structurally, three things are different, and all three are about authority rather than gameplay.
| Internal bingo (one clan) | Clan vs clan bingo | |
|---|---|---|
| Who owns the board | One admin, unquestioned | Two admins who must agree |
| Who approves drops | Your staff, trusted by everyone | Your staff, judging their tiles |
| Roster control | You balance the teams | Neither clan controls the other's size |
| Dispute escalation | Clan leader decides, done | Nobody outranks both sides |
| Cost of a bad rule | An argument | The match ends early |
The middle row is the one that ruins events. If your admin approves your own clan's screenshots and theirs, you have not run a match — you have run a match with a referee wearing one team's shirt. It does not matter whether the calls are fair. The losing clan will not believe they were, and they are not being unreasonable for wondering.
That single problem is why a clan-vs-clan setup needs two admins with equal rights over the same board, and why "just add them to my server as a normal member" does not work.
There are two honest ways to run this.
The cheapest option. One clan runs the bingo on its own board and gives the opposing clan nothing but a scoreboard to look at.
It works if the two clans already know each other well. It fails the first time a marginal screenshot gets rejected, because the rejecting admin is also a competitor. If you take this route, at minimum agree that any disputed tile is approved for both clans or neither, and put a neutral third party in the Discord.
Both clans get an admin account on the same bingo. Both can build the board, both can approve submissions, and neither is a guest. That is the setup this format is built for.
Several free tools list a clan-vs-clan mode and one of them may well do the job — our comparison of OSRS bingo sites is honest about which, and for a single friendly match a free tool is often the right answer. What you are paying for, if you pay, is your own address and a clean split of authority. Here is what OSRSHub's versus checkout provisions:
clan-a-vs-clan-b, not at one clan's name, which sounds trivial and is not: the URL is the first thing that tells the opposing clan whether this is a joint event or a visit to your house. Two long clan names get shortened to fit the address limit, and checkout shows you the exact address before you pay.One thing both clans should understand before they start: it is one subscription covering both sides. If it lapses, both clans lose access together — there is no state where the paying clan keeps playing and the other does not. That is worth saying out loud to your opponent rather than letting them discover it, and it is an argument for the clan with the steadier finances to be the one that buys.
Whichever option you choose, the sequence is the same: agree the rules, build the board together, share join links, run the event, publish the result.
Internal bingo can get away with lazy scoring because the teams were built to be even. Two real clans never are.
Points, not lines. A lines-and-blackout win condition rewards the clan that happened to draw a favourable corner of the board. Points per tile, with bonuses for completed sets, tracks total work done and is far harder to argue with. If you want the drama of lines, keep points as the primary score and treat lines as a tiebreak.
Decide what a set bonus is worth before you build the board. A 10-point bonus on a five-tile set is a nudge. A 50-point bonus is the entire match, and whichever clan spots that first will build their whole week around one set.
Publish the scoreboard both clans can see. Not a spreadsheet one clan maintains. A live head-to-head score removes an entire category of accusation, because nobody has to trust a screenshot of a total.
The most common version of this match is 40 players against 25, and the most common outcome is that the 25 stop playing on day three.
Four workable fixes, in rough order of how often they actually get used:
Whatever you pick, write it in the rules post before the board goes live. A handicap introduced after the first day is not a handicap, it is a concession, and it reads as one.
No tool solves this for you. The hiscores cannot see individual item drops, so anything drop-based comes down to a screenshot and a human decision — the full picture is in the automatic tracking guide, and it is worth reading before you promise your opponent anything about "automatic" verification.
What a two-clan match needs on top of ordinary bingo rules:
The drop verification guide covers the underlying rules in more depth; everything above is what you add because there are two clans in the room.
Two admins building one board sounds like a recipe for a mess. It is fine, with one rule: split the board by set, not by tile.
Give each clan responsibility for drafting half the sets, then review each other's half before anything goes live. Splitting tile by tile means two people editing the same set within minutes of each other and losing work; splitting by set means clean ownership and one review pass.
Watch for the bias that shows up in every co-authored board: people write tiles around content they already do. A clan that raids constantly will draft a raids-heavy set without noticing, and their opponent will read it as an attempt to rig the match — usually wrongly, occasionally not. The fix is mechanical rather than diplomatic: agree a content spread first (so many boss tiles, so many skilling, so many clue, so many minigame), then draft into it.
If neither clan wants to start from a blank grid, our board templates and the free board generator both give you a structure to argue with instead of a blank page, and community boards shows what other clans have published.
A match nobody outside the two clans ever hears about is a missed opportunity — the whole appeal of clan vs clan is that it produces a story with a scoreline.
If you want the result public, OSRSHub has an opt-in public battles page that lists both clan names, the board, both scores and whether the match is still running. It is off by default and stays off until the owner turns it on, which is the correct default for something that publishes another clan's name alongside your own. Player names, tile detail and your bingo's address never appear there.
Publishing also solves a smaller problem: it gives you a link to point at the next time somebody asks whether your clan actually runs events.
Copy this into your Discord and get both clan leaders to react to it before you build anything:
Every one of these takes a minute to agree in advance and a week to argue about afterwards.
Clan vs clan bingo is a bingo event between two separate clans playing the same board at the same time, scored head to head. Instead of splitting one clan into internal teams, each clan is a team, and the event produces a single result between two communities rather than an internal winner.
No — and they should not have one each, because two boards cannot produce one scoreboard. A clan vs clan match runs on a single shared bingo with two teams, one per clan, and both clan leaders administering it. On OSRSHub that is a single versus subscription at $13.60 a month rather than two separate ones.
Pick one of four rules before the event starts: cap the number of active participants on both sides, score points per capita, give the larger clan a higher target, or agree openly to play it straight. The unfair version is not the mismatch itself — it is a mismatch nobody discussed, which the smaller clan notices on day two.
Both clans should have an admin with equal approval rights, and any borderline submission should need both. One clan approving every tile, including their opponent's, is the single most common reason these matches end in an argument, however fairly that admin actually judged.
One to two weeks. Shorter than that and drop RNG decides it; longer and the losing clan disengages once the gap looks unrecoverable. Our guide on how long an OSRS bingo should last covers the trade-offs, and they are sharper here because a clan that loses interest is an entire half of the event.
Yes, and it is a good fit — a path-based format keeps both clans bunched together instead of letting an early lead compound. The tile race guide covers layouts; everything in this article about admin rights, evidence standards and roster rules applies unchanged.
If you have an opponent lined up, agree the five checklist items, then build the board together rather than presenting one.
If you do not have an opponent yet, that is the harder half of the problem: read how to find an opponent for your clan bingo match, which covers where to look, how to write a post that gets replies, and how to spot a clan that will go quiet three days in.