TTK vs DPS: Why the Higher-DPS Gun Can Still Kill Slower

This is a condensed cross-post of the original KeyboardTester.click guide: TTK vs DPS: Why the Higher-DPS Gun Can Still Kill Slower.

A weapon stat screen says one rifle has more damage per second. Does that guarantee a faster kill?

No. In a short FPS gunfight, the lower-DPS weapon can win if it crosses a bullets-to-kill breakpoint.

The shortcut target HP ÷ DPS treats damage as a continuous stream. Most guns do not deal tiny fractions of damage every millisecond. They deliver whole bullets at specific times. The target may survive with a few HP, forcing the weapon to wait for one more shot.

The three numbers answer different questions

• DPS is a damage rate over a defined firing window.
• BTK is the number of complete bullets required to reach or exceed the target's effective HP.
• TTK is the elapsed time from the first landed hit to the killing hit under a stated timing convention.

TTK is usually the clearer metric for a fixed-HP duel. DPS becomes more useful for long damage windows, large health pools, barriers, vehicles, bosses, or several targets.

Neither number is universally better. The mistake is asking one metric to answer the other's question.

Why HP divided by DPS can misrank a gunfight

Imagine an automatic weapon that deals 32 damage per bullet at 900 RPM.

Its raw DPS is:

32 × 900 ÷ 60 = 480 DPS

Dividing a 100 HP target by 480 DPS suggests about 208.3 ms of exposure. But the actual hit sequence is discrete:

Hit 1: 32 damage
Hit 2: 64 total
Hit 3: 96 total — target survives
Hit 4: 128 total — target dies

The four-HP shortfall after hit three matters. The weapon must wait for bullet four.

For a simple full-auto comparison, use this sequence:

effective damage = base damage × range multiplier × (1 − armor reduction)
BTK = ceil(target HP ÷ effective damage)
shot interval in ms = 60,000 ÷ RPM
TTK = max(0, BTK − 1) × shot interval
DPS = effective damage × RPM ÷ 60

The ceil is essential because a fraction of a bullet cannot finish the target.

The armor term above is only a transparent flat-percentage comparison model. Real games may use shields, plates, penetration, armor tiers, separate health pools, limb multipliers, or damage-specific rules. Use effective damage that matches the game and patch you are studying.

Why TTK uses BTK minus one

Under the first-landed-hit convention, the first successful bullet starts the clock at 0 ms.

At 600 RPM, one shot interval is 100 ms:

Bullet 1 lands at 0 ms
Bullet 2 lands at 100 ms
Bullet 3 lands at 200 ms
Bullet 4 lands at 300 ms

A three-bullet kill therefore contains two intervals, not three. That is why the formula uses BTK − 1.

The convention does not claim that mouse input, firing animation, projectile travel, rendering, or server processing take zero time. It starts the narrow weapon-only measurement when damage first lands.

For the same reason, a one-shot kill is 0 ms only from first landed hit to killing hit. Time from input to impact can still be nonzero.

Worked example: 480 DPS loses to 368.3 DPS

Compare two fictional automatic weapons against the same 100 HP target. Keep armor at 0%, range damage at 100%, and the hit multiplier at 1×.

Weapon	Damage	RPM	Raw DPS	BTK	Shot interval	Theoretical TTK
A	32	900	480.0	4	66.7 ms	200.0 ms
B	34	650	368.3	3	92.3 ms	184.6 ms

Weapon A produces about 30% more raw DPS. Its 32-damage bullets need four hits, though, so the kill lands after three 66.7 ms intervals.

Weapon B fires more slowly, but three 34-damage hits total 102. It kills after two 92.3 ms intervals—about 15.4 ms sooner.

You can reproduce both results in the TTK Calculator by changing only damage and RPM.

Breakpoints create step changes

A damage breakpoint is the point where a small damage increase removes one complete bullet from the kill.

Against 100 HP at 600 RPM:

Case	Damage	Raw DPS	BTK	TTK	Damage delivered
Before breakpoint	33	330.0	4	300.0 ms	132 total; 32 overkill
After breakpoint	34	340.0	3	200.0 ms	102 total; 2 overkill

One extra point of damage removes an entire 100 ms interval.

That staircase behavior is why a range falloff, armor change, or hit-location multiplier can suddenly alter a weapon's TTK. A small numerical change may do nothing until it crosses a threshold; then it can remove a full bullet.

Overkill shows how far a weapon sits beyond the target's remaining HP on the killing shot. It is useful context, but it should not be judged alone. Higher per-shot damage may improve other range, armor, head, or limb breakpoints, while faster fire may recover from a miss sooner.

When DPS is the better metric

Use DPS when the damage window is long enough that one final-bullet threshold is no longer the main story:

• a boss, vehicle, or barrier has a large health pool;
• the target survives one magazine;
• reload and cooldown cycles matter;
• several targets are damaged over time;
• a beam or damage-over-time effect behaves more continuously.

Define the window. Burst DPS may ignore reloads. Sustained DPS usually includes them. Effective DPS may account for accuracy, falloff, weak-point rate, or uptime. Two correct DPS figures can differ because they use different windows.

Theoretical TTK is not total gunfight time

The formula assumes the required hits land on schedule after the first hit. A real duel also includes:

• target detection and reaction;
• aim acquisition and movement;
• recoil correction and misses;
• hit-location and distance changes;
• projectile travel, charge time, or burst delay;
• magazine and reload limits;
• input, rendering, network, and server processing.

EA's 2026 Battlefield gunplay discussion used a scoped 200–300 ms close-range benchmark for automatic primary weapons, while treating recoil, bullet deviation, muzzle velocity, and body-part multipliers as separate balance levers. That game-specific example reinforces the broader point: low best-case TTK can come with harder control or more demanding hit placement.

Browser checks can investigate individual setup factors. A reaction-time measurement or mouse accuracy test does not measure a game server's complete end-to-end gunfight latency, and it does not change the damage/RPM formula.

A comparison workflow that stays honest

1. Write down target HP, armor or shield assumptions, range, hit location, and fire pattern.
2. Enter Weapon A and record effective damage, BTK, interval, TTK, and DPS.
3. Enter Weapon B without changing the target rules.
4. Compare BTK before DPS and identify any breakpoint.
5. Change one input at a time—range, mitigation, or hit multiplier.
6. Add recoil, accuracy, magazine, reload, travel, movement, and system conditions after the weapon-only result is clear.

Use real weapon values only when they are dated and tied to the same patch. Otherwise, label the result fictional or theoretical.

The takeaway

DPS is a rate. TTK is a threshold result.

For short bullet-based fights, calculate complete bullets first, then count the intervals after the first landed hit. That is how a 368.3-DPS weapon can beat a 480-DPS weapon against the same target without either calculation being wrong.

For the full explanation, source notes, practical limitations, breakpoint visualizations, and FAQs, read TTK vs DPS on KeyboardTester.click.