Time attack games score a run by how quickly it finishes, and in Bomb Appétit the score is the time left on the clock at the defusal. A team gets faster by cutting out waiting, not by rushing: read the edgework aloud first, split the manual between Experts, and slow down when a wrong move means a strike.
Why time attack games punish guessing more than slowness
In a bomb defusal, a wrong guess costs far more than the seconds it tried to save. Every mistake is a strike, and strikes make the clock run faster: 1.25 times normal speed after the first and 1.5 times after the second. On the default limit, the third strike sets the bomb off and the run scores nothing.
Put numbers on it. Suppose a team takes a strike with two minutes on the clock and still needs 100 real seconds of work to finish. At 1.25 times speed, those 100 seconds drain 125 seconds from the clock. The guess cost 25 seconds of clock on top of whatever the mistake itself wasted. A second strike makes every remaining real second cost a second and a half.
Speedrun browser games often let a player shrug off a failed attempt and restart. A bomb is less forgiving. The leaderboard only ranks defusals, so a run that explodes has no time at all. Some missions also give fewer strikes to spend. No substitutions allows two, and the final mission, named Bomb Appétit after the game, allows one. On those bombs a single guess can end the attempt.
The board treats strikes as a tie-break as well. Time left is compared first, and strikes only decide between runs with the same time. Our guide to how ranks are decided walks through the order with an example. The practical lesson is that strikes hurt mainly through the clock, and the clock is the score.
Where a defusal loses its seconds
Most of the seconds a team loses are spent waiting, not solving. The Expert waits for a detail the Defuser has not read out. The Defuser waits while an Expert finds the right page. Everyone waits while a symbol gets described three different ways. Solving time shrinks slowly with practice, but waiting time can drop within one evening.
The timeline below is an invented example, not a recorded run. It follows one team, a Defuser and two Experts, on the mission Quick snack, which gives four minutes for four modules drawn from Wires, Big Button and Glyph Keypad. In this example the bomb dealt Wires, Big Button, Glyph Keypad and a second Wires module. The team ran it twice, once before and once after three changes.
| Step (invented example) | Before | After | What changed |
|---|---|---|---|
| Edgework read aloud at the start | 0 s | 15 s | Change 1: one readout before any module |
| Wires | 45 s (12 s finding the serial number) | 33 s | No serial hunt |
| Big Button | 55 s (15 s counting batteries and checking the indicator) | 40 s | No battery hunt |
| Glyph Keypad | 60 s (6 s flipping pages, 4 s naming symbols) | 50 s | Change 2: manual split. Change 3: agreed symbol names |
| Second Wires | 40 s (8 s asking for the serial again) | 32 s | Serial already written down |
| Total | 200 s, defused with 0:40 left | 170 s, defused with 1:10 left | 30 seconds recovered |
The edgework readout cost 15 seconds and removed 35 seconds of hunting, a net saving of 20. Splitting the manual removed 6 seconds of page flipping. Agreeing on names for the glyphs removed another 4. Neither run had a strike, so the clock ran at normal speed throughout and the before and after totals compare directly.
Two things stand out. None of the 30 seconds came from thinking faster about a module. And none came from skipping a check. Every saving removed a pause where somebody was waiting for somebody else.
Why reading edgework first saves the most seconds
Edgework is the detail printed on the sides of the case: the serial number, batteries, indicators and ports. Manual pages ask about it again and again, so reading it all out once at the start replaces a fresh hunt every time a rule needs it. In the example above, that single change was worth 20 of the 30 seconds.
The manual leans on edgework for some of the most common modules. The Wires page asks about the serial number, and the Big Button page asks about batteries and indicators. When the Defuser has not read them out, the Expert stops mid-rule, the Defuser turns the case to look, and both lose the thread of the module they were on. Batteries are the worst offender, because they can sit on any side of the bomb and all of them have to be counted.
A readout that works covers four items in a fixed order. Read the serial number one character at a time. Give the total battery count after checking every side. Name each indicator by its three letters and say whether its light is lit or unlit. List the port types. The Experts write all of it down where they can see it. With several Experts, each one copies it, so nobody has to ask the person beside them.
The habit pays off most on missions where the same module turns up twice, as Wires did in the example. Without a written note, the team asks for the serial number twice. With one, the second Wires module starts at full speed. For the exact way to say each character so it cannot be misheard, read reading the serial number out without ambiguity. The whole topic is covered in our post on reading the edgework in a bomb instructions game.
Should Experts split the manual to go faster?
Yes, as soon as a team has two or more Experts. Give each Expert a few modules to own, so their pages are already open when the Defuser names a module. The game's own advice says the same, and the mission Rush hour, six modules in six minutes, tells players outright to split the manual between Experts.
A split works best when it follows the mission's module pool. Quick snack draws from three module types, so two Experts might take Wires and Big Button for one and Glyph Keypad for the other. Rush hour draws from six types: Wires, Big Button, Glyph Keypad, Color Echo, Word Grid and Recall. Three Experts can take two each. A team can have up to four Experts, which leaves room for one of them to own the needy modules on the missions that have them. The mission ladder from First bite up lists every mission's pool, so a team can plan its split before pressing start.
The Defuser's job changes slightly with a split. Instead of describing a module to the whole group, the Defuser names the module first, then describes it. "Glyph Keypad" is enough to make the right Expert look up and the others stay on their own pages. That one word saves the few seconds in which two Experts both start flipping.
A team with a single Expert cannot split, so the saving has to come elsewhere. The Expert can keep the pages for the mission's pool marked and in reach, and the Defuser can name each module before describing it so the page turns while the description is still going.
When should a fast team slow down?
Slow down whenever the next action cannot be taken back and nobody has said it back yet. Slow down after a strike, when the clock already runs faster, and on missions with fewer strikes to spare. A two-second pause is cheap. A strike charges extra clock for the rest of the run.
Some modules make the case for patience on their own. On Color Echo, according to the Echo chamber mission note, the mapping between pads changes when you strike, so a mistake changes the puzzle under you. The Second helpings mission, which brings in Recall, asks the Defuser to remember what was pressed across five stages, so rushing one stage can spoil the next. The Word salad mission warns of words that sound alike and tells players to spell them out. Each of these punishes speed in a specific way, and a team that knows which modules are fragile can save its caution for them.
The strike count on the case is the other signal. After the first strike, the team should treat every remaining action as costing a quarter more time. After the second, on a default bomb, one more mistake ends the run. This is the point to tighten up: slower speech, more repeating, and a slower finish accepted over no finish.
The one-strike mission deserves its own warning. Bomb Appétit, the last mission in the game, gives ten minutes for eleven modules with a single strike, using rule seed 2026, a manual that differs from the standard seed 1. A team that plays it at its usual pace risks the whole run on every guess.
The speed mistake: cutting before the repeat-back
The speed mistake that undoes fast teams is acting on an instruction before saying it back. The Expert says "cut the third wire", the Defuser hears "the red wire", and the cut lands before anyone notices the mismatch. A repeat-back takes a second or two. Skipping it saves that second and risks a strike that slows every second after it.
The game's advice to players puts it plainly: Experts give one clear instruction, and the Defuser says it back before acting. Under time pressure, the second half is the easy part to drop. The instruction feels obvious, the clock is loud, and the Defuser's hand moves first.
A repeat-back does not need to be a full sentence. The Defuser can echo only the parts that could be misheard: the number, the colour, the position. "Third wire, cutting" takes about a second. If the Expert meant something else, that is the moment to say "no, stop". A wrong cut cannot be undone.
The repeat-back is not just a safety step. It is also a speed step, because it replaces the much longer conversation that follows a strike: what happened, which wire it was, whether the rule was read correctly, and what to do now with the clock running faster.
When a team has the three changes in place and the repeat-back holding up under pressure, the missions page shows its best time on each mission, and the leaderboard shows where that time ranks among signed-in players.