Match Timers and Tournament-Style Play
How time limits work in Pokémon TCG tournaments, best-of-one versus best-of-three, what happens when time is called, and good table etiquette.
Last updated · 2 min read
Casual games rarely use a clock, but practising with one prepares you for events, where every match has a time limit.
Common time limits
Time limits are set by the organiser and by the official Play! Pokémon rules for the event type. Common setups are:
- Best-of-three matches with about 50 minutes on the clock, used for most competitive Swiss rounds.
- Single games (best-of-one) with about 25–30 minutes, common at smaller local events.
Always check what your event uses. PTCG Companion’s timer can be set to 25, 30 or 50 minutes from ☰ Menu.
When time is called
At official events, when the round’s time runs out, the game does not just stop. The player whose turn it is finishes that turn, and then a small number of extra turns are played. If no one has won after that, the winner is decided by who has taken more Prize cards, with further tie-break procedures in the official rules. Because these details change between seasons, read the latest Play! Pokémon Tournament Rules Handbook before an event.
Playing at a good pace
- Shuffle efficiently. A few good riffle or mash shuffles are enough; long shuffling eats into the clock.
- Announce what you do. Say when you attach Energy, play your Supporter or use an Ability. It avoids disputes and saves time.
- Keep the board readable. Clear damage, markers and Prize cards make it easy for both players to check the game state. Putting the phone between you with PTCG Companion keeps damage, conditions and Prize cards visible to both players.
- Call a judge, not a guess. At an event, if you disagree with your opponent about a rule, pause and call a judge.
Practising with the timer
Run the timer during practice games to learn how many turns a typical game takes with your deck. If you often run out of time, look at which turns take longest. Searching your deck and long combo turns are usually the cause, and simple routines (for example, always counting Prize cards the same way) speed things up.
