Why your D&D combat is running 40 minutes over (and the math to fix it)

A game master builds an encounter that looks perfectly reasonable on the page — four players, a handful of monsters, nothing exotic — and forty-five minutes later the party still has not landed a killing blow. The session's other three planned scenes get cut, and everyone leaves a little deflated. This happens constantly in D&D and other tactical TTRPGs, and it is almost never about the encounter being "too hard." It is about two numbers nobody budgets for in advance: how long each turn actually takes, and how many rounds the fight actually needs.

Turn time is not fixed — it scales with character level

A 1st-level fighter's turn is move, attack, done. A 12th-level wizard's turn is move, consider three spell options, check concentration, resolve a reaction, argue briefly about advantage. Both are "one turn," but they do not take the same amount of table time, and treating them as equivalent is where most encounter-length estimates go wrong from the very first assumption.

A workable baseline is a flat 60 seconds of table overhead per turn, plus roughly 10 seconds for every character level — a 1st-level turn runs about 70 seconds, a 15th-level turn runs about 210 seconds, because higher-level characters simply have more decision surface: more spell slots, more conditional abilities, more reactions to track. On top of that base figure, the group's decision speed acts as a multiplier — a tactical, rules-fluent table can run at roughly 0.7× that baseline, an average table at 1×, and a distracted or rules-uncertain table at 1.5×. The gap between a fast table and a slow one at the same level is enormous in practice, which is why the same encounter can feel brisk with one group and glacial with another.

Round count does not scale linearly with monster count

The second number is how many rounds the fight actually takes to resolve, and this is where intuition misleads GMs the most. It is tempting to assume "twice the monsters means twice the rounds," but that is not how attrition works in practice. More monsters means more total damage output hitting the field per round, so the fight tends to resolve in a similar or only slightly higher number of rounds — the extra bodies mostly add more turns per round, not more rounds overall. Meanwhile a higher-level party trims rounds off the fight from the other direction: more damage per hit, more area-effect spells, more ways to end multiple monsters in a single turn. Put those two forces together and round count should rise gently with monster count, fall gently with character level, and get clamped to a sane range — nothing table-breaking under 2 rounds, nothing absurd over 8 — so that neither an unusually easy nor an unusually swingy roll produces a nonsense estimate.

Multiply, and the real cost of a fight becomes visible

Total table time is turn time times the number of turns in the fight, and the number of turns is simply everyone at the table — players and monsters both — taking their turn, once per round, for however many rounds the fight runs. That last part is easy to undercount: monsters take turns too, and a fight with six monsters adds six turns to every single round, not one.

Worked example: the "reasonable" encounter that runs long

Take four 3rd-level players against four monsters, at an average decision speed. Turn time comes out to about 90 seconds. Round count lands around 4. Total turns per round is 4 players plus 4 monsters, or 8. Multiply 8 turns by 4 rounds by 90 seconds and the fight totals roughly 48 minutes of table time — comfortably past the point where "one more encounter this session" stops being realistic, from an encounter that on paper looks like a completely ordinary mid-session fight.

Now compare a higher-stakes version: five 10th-level players against six monsters, at a fast, tactically fluent table. Turn time drops to about 112 seconds thanks to the speed multiplier, even though the higher level would otherwise push it up. But round count still lands around 4, and now there are 11 combatants taking turns each round. Eleven turns times four rounds times 112 seconds runs past 80 minutes — a genuinely big set-piece fight, and worth knowing that going in rather than discovering it by watching the clock.

What this means for session planning

The practical takeaway is not "make fights smaller." It is that turn time and combatant count multiply, so a small increase in either one has an outsized effect on total duration, and that effect is easy to underestimate by just eyeballing the encounter. A GM who wants two set-piece fights and a social scene in a four-hour session needs to know, before the session starts, whether the first fight alone is going to eat half the available table time. The single most dangerous move is starting a full encounter fifteen minutes before the table needs to end — if the math says the fight runs 45+ minutes, that is exactly the fight to save for the start of next session instead.

Working this out by hand for every planned encounter is tedious, especially when you are trying to compare two or three possible fights against the same time budget. Our TTRPG encounter pacing predictor takes players, character level, monster count, and table speed, and returns the estimated rounds, per-turn time, and total real-world duration in one pass — including a flag when a fight is heavy enough that it should not be started near the end of a session.