How to run a mobile battle royale custom room tournament
Three games, one operational problem: getting the right squads into the right room without the code reaching everyone else first.
The Fragnet team · Published 10 August 2026 · 11 min read
How we know this: Covers BGMI, Free Fire MAX, CODM and Mobile Legends in one operational frame rather than four shallow per-game posts, with the correct room mechanics and prize currency for each. The room-ID section describes a problem with a named product answer, and says what that answer does not solve.
Fragnet lists events. We don’t vet organizers, we never hold entry fees or prize money, and we have no brackets, results entry or leaderboards. Anything in this article about running an event assumes you own those parts.
What a custom room actually is, per game
Every mobile battle royale event runs inside a private lobby the organizer creates. The mechanics differ enough per title that assuming they are the same is how first events go wrong.
BGMI and PUBG Mobile
Created with a room card, which is consumed per room. Up to 100 players, 25 squads of four. You get a room ID and a password, and you admit players as they join. Confirm you have room cards before you publish an event, not on the night.
Free Fire MAX
Custom rooms have their own access requirements, and rounds are roughly ten minutes — far shorter than BGMI. Twelve squads is a common lobby size, which changes both the points table and how many matches you can run.
Call of Duty: Mobile
Private matches cover both multiplayer and battle royale. Multiplayer modes behave like a normal bracket; BR is scored on points. Decide which you are running before you write the rules, because they need different documents.
Mobile Legends
Not a battle royale, but the same custom-room mechanics: create the room, set draft mode, admit ten players. Ten-minute matches mean a 16-team bracket genuinely fits an evening.
Slot maths, and what happens when squads don’t show
A 25-squad BGMI lobby needs 100 people to be in the right place at the right time. That is a lot of coordination, and the realistic no-show rate at amateur level is high enough to plan around rather than hope about.
- Over-list slightly and keep a waitlist. Twenty-five confirmed squads with five waiting is a full lobby; twenty-five with none is twenty-one on the night.
- Open check-in well before start so no-shows surface while replacements can still be promoted.
- Decide in advance whether you run a short lobby or delay. Delaying once teaches everyone that start times are negotiable.
- A squad arriving with three is a rules question, not a live decision — write it down.
The rules that stop arguments in mobile BR
Mobile events generate a specific set of disputes, and all of them are preventable in writing.
- Emulators. Permitted or not — state it. "No emulators" is a rule; silence is an argument.
- Device restrictions, if you have any. Also state how you would verify one, because "no iPads" is unenforceable if you never check.
- Teaming. The most common BR-specific accusation you will receive. Define it and say what evidence you accept.
- ID verification: in-game name and UID must match registration. This is what lets you check the lobby against the roster.
- Hackusations. Require a clip or a screenshot. Without an evidence standard you will spend the event adjudicating vibes.
- What happens if a squad disconnects mid-match. Usually: the match stands. Say so.
Building the slot list
A slot list is the mapping between the squads that registered and the slots in the room. Publishing it before the event does two useful things: squads know which slot to take, and everybody can see who is supposed to be in the lobby.
- 1.Collect in-game names and UIDs at registration for every player, not just the captain.
- 2.Assign slot numbers and publish the list 24 hours ahead.
- 3.Name substitutes on the list. An unnamed substitute is an unregistered player.
- 4.Keep the list open during admission so you can check arrivals against it.
The room ID problem
Why posting it early costs you the lobby
A room ID and password in a Discord channel is readable by every member of that server, whether or not they registered and whether or not they paid. Thirty minutes is more than enough for it to travel. You then spend the start of your event removing people instead of running matches.
Ghost squads
The specific failure: unregistered players fill slots meant for registered squads, and by the time you notice, a paying entrant is locked out of a full lobby. Every organizer running custom rooms has had this happen at least once.
Sending it by hand is the same problem, plus an hour
Messaging 25 captains individually at T-15 both exposes the code — captains forward it — and consumes exactly the window when you should be admitting players.
Timed reveal
Enter the room ID and password once when you publish. They stay encrypted until a set number of minutes before start, then unlock for confirmed players only. Nobody unapproved sees them, and you send nothing manually.
What it does not solveA confirmed player can still forward the code after it unlocks. Timed reveal shrinks the window from half an hour to a few minutes and removes the public and the unapproved from the audience entirely. It does not make a code unshareable — nothing does. Admission checks against your slot list are still the last line.
Scoring across multiple matches
Placement points plus kill points, across four to six matches. Three is mostly variance; one is entertainment. Publish the table before registration opens, because the table is the event’s design and people choose events on it.
Running matches back to back
The gap between matches is what decides whether a six-match event finishes. Aim for eight minutes and enforce it.
- 1.Announce the next start time the moment the previous match ends, as a clock time rather than "in a few minutes".
- 2.Collect result screenshots during the gap, not after the event.
- 3.Update the standings sheet between matches so nobody asks.
- 4.Re-admit squads while you are doing the above — the lobby refills in parallel with the admin.
- 5.Start on the announced time whether or not everyone is back.
Prizes in mobile BR events
Cash, or in-game currency: UC for BGMI and PUBG Mobile, Diamonds for Free Fire and Mobile Legends, CP for CODM. Getting the name right matters — advertising diamonds for a BGMI event tells players you copied the listing.
State the delivery method and a timeframe. Fragnet displays the prize you entered and converts it for orientation, and holds none of it — the promise is yours.
The five things that go wrong most
| Problem | Fix |
|---|---|
| Room code leaked before start | Timed reveal, plus admission checked against a published slot list |
| Lobby short by four squads | Over-list, keep a waitlist, open check-in 30 minutes early |
| Points disputed after match four | Publish the table before registration; update standings between matches |
| Emulator accusation with no policy | State the policy in the rules and the evidence you will accept |
| Event overruns by 90 minutes | Fixed eight-minute turnaround, announced as clock times, started on time |
Common questions
- Do I need a room card to host a BGMI tournament?
- Yes, for BGMI and PUBG Mobile custom rooms, and they are consumed per room. Confirm you have enough before publishing an event rather than on the night.
- When should I share the custom room ID and password?
- As late as is practical, and to confirmed players only. Timed reveal handles this automatically — commonly 15 minutes before start, or five for a lobby of regulars already waiting.
- How many matches should a mobile BR event run?
- Four to six. Free Fire rounds are short enough for six comfortably; BGMI matches are longer, so four to five is more realistic on a weeknight.
- How do I stop unregistered players joining the room?
- Publish a slot list with in-game names and UIDs, admit against it, and do not distribute the code publicly. Reveal timing reduces exposure; the slot list is what catches anyone who still gets in.
Read next
- Battle royale points systems for tournamentsPlacement points plus kill points, with copy-paste tables, tiebreakers, how many matches you need for a fair result, and how the ratio changes play.
- A tournament rules template you can copy-pasteA complete rules template covering eligibility, conduct, disputes, no-shows, substitutes, fees and payouts — plus the clauses that stop arguments at 23:00.
- How to run a weekly scrim ladder that survives month twoWeekly series die from admin fatigue, not lack of players. A repeatable routine: fixed variables, cloned listings, a real waitlist and a T-minus timeline.