Scoreboard and leaderboard
Where standings live, how ties in time work, and what freezing means.
Standings live in two places: the scoreboard (the public, shareable standings page) and the in-app Leaderboard for signed-in players. Both read the same rankings; they differ in audience and detail. This page covers both, plus tie-breaking, the freeze, and the CTFtime feed.
The public scoreboard
/scoreboard on your event’s site needs no login; share the link with anyone. It shows:
- A Top 10 Score Progression chart showing the leading teams’ scores since the event started.
- The standings table: Rank / Team / Score / Solves, with trophy and medal icons on the top three.
It refreshes itself every few seconds while the event is live (“Live rankings and score history.”). Before the event starts, the page sits behind the start countdown like the rest of the competition pages.
Per-challenge stats
Challenges in the scoreboard’s header opens /scoreboard/challenges: “Category, points, and the first three solves per challenge.” One row per released challenge: Challenge / Category / Points / Solves / Bloods, where the Bloods column names the first three solving teams with 🥇 🥈 🥉 (or a dash placeholder while unsolved).
The Points column here is the challenge’s base value, not its current decayed value; for what the next solve is actually worth, check the challenge list or the challenge page.
The in-app leaderboard
Signed-in players get the Leaderboard in the navbar: “See how you rank among all competitors globally”. Compared to the scoreboard it adds:
- A sort toggle to rank by Points or by Challenges Solved.
- On team events, a Filter by team dropdown narrows the board to a single team; pick All teams for the full list.
- Avatars, display names, and handles per row; on solo events each row links to that player’s public profile.
It refreshes even more frequently, and your own dashboard’s Rank card shows your position without visiting either page.
How ties break
Teams with equal points are ranked by who reached that score first: the team whose last score-increasing event came earlier ranks higher. That’s usually a solve, though an organizer’s bonus counts too. Losing points later (a hint penalty) doesn’t reset your tie-break time; only gaining points sets it. So when you and a rival are neck and neck, the solve that gets you to the shared total sooner is what puts you above the line.
What freezing means
At the event’s freeze time, competition ends and the standings become final:
- The scoreboard’s subtitle flips to “Standings are frozen: final rankings as of the freeze.” and it stops refreshing.
- Flag submission closes everywhere (“Submissions are closed.”), so no solve can change the board after the freeze: the frozen board is the final board. There’s no hidden backlog of late solves waiting to be revealed.
- The per-challenge stats page counts only solves and bloods from before the freeze.
- The in-app leaderboard shows no freeze notice; it simply stops moving, because scoring has stopped.
What opens up at the freeze (feedback, writeups, certificates) is covered in After the freeze.
The CTFtime feed
Every event site serves a public scoreboard feed at /api/ctftime/scoreboard, in the standard format CTFtime expects:
{ "standings": [{ "pos": 1, "team": "TeamName", "score": 1234 }] }
It mirrors the public scoreboard. Nothing links to it in the UI. Organizers hand the URL to CTFtime so results can be rated; as a player you never need it, but it’s there if you’re curious.