Start here
New here? This page teaches you to read our boards. It takes about a minute.
We pay for Claude Code, Codex, and Grok Build — the same paid coding apps you type into every day. A machine in our lab gives each app the same short jobs every hour and times what comes back. You only read the results: no sign-up, nothing to set up.
Anatomy
One row, taken apart
A leaderboard row with example numbers, not live data. Five parts. Read one row and you can read every board on the site.
Example numbers for teaching. The live board is on the home page.
Rank
The 24-hour board sorts on total wait, shortest first. A dash means it is still collecting the 12 checks needed for a typical result.
Swatch and name
The color square names the app: orange is Claude, violet is Codex, green is Grok. The name links to that model's page.
Pin and effort
The small line under the name: the exact model we ask for, then the thinking setting we pinned. Each model runs at the top of its own scale.
Writing speed and total wait
Writing speed says how quickly the visible answer arrived. Total wait says how many seconds the whole job took. The table shows both and ranks the shorter wait first.
The pace line
The small line under the number. The leader says “Sets the pace”. Every other row says how much longer its total wait was, like “11% longer wait”.
Model pages carry the detail numbers: writing speed, total wait, time to first word, answered checks, and rate limits.
Open the live board and read along.
The words on the boards
The terms you will meet on the boards, in plain English.
- Token
- A token is a small chunk of text, roughly four letters. Models read and write text one token at a time.
- Writing speed
- Visible answer tokens per second from start to finish. Higher is faster. Hidden thinking does not make the score larger.
- Total wait
- The seconds from starting the app to the completed answer. Lower is faster. This is what the typical 24-hour table ranks.
- Ping
- A tiny check that asks for the word “ok”. It shows how long the app takes to wake up and reply. It is not a writing-speed test.
- Round
- A one-hour slot. Our lab runs one set of checks per round, at the top of each hour. We try once. A fail stays a fail.
- Usual
- The middle value of a column, not the average. Line the samples up smallest to largest and take the one in the middle. One freak run cannot drag it around.
- Completed check
- A check where the tool finished and the answer was right. A plain script checks it. A fast wrong answer earns nothing.
- An empty cell
- Fewer than 12 completed checks for that model inside the window. It does not mean zero or broken. We leave the typical result blank on purpose.
Live means the newest completed check. Typical means at least 12 checks from the last 24 hours. We never mix those two.
Questions people ask first
- Is my tool slow right now, or is it just me?
- Open the live board. If our lab is slow on that tool in the round that just finished, it is not you. If our numbers look normal, the trouble is closer to your machine, your network, or your prompt.
- Why is a cell empty?
- That model has fewer than the 12 completed checks needed for a typical result. We would rather show a blank than a shaky guess.
- Why is there no single winner?
- Write speed and the wake-up ping answer different questions. A tool that writes fast but takes ages to start has not won anything, so we never blend the two into one score.
Next: open the Live board, see Today’s card, or read For teams if you buy seats.
How to read this
Every number here comes from one lab machine, on one connection, with the app versions listed on Status. These are our own measurements, not official vendor numbers.