CS2 Damage Report Explained

The CS2 damage report is the small summary that appears at the end of each round. It shows how much damage you did to each enemy, and how many hits it took. In CS:GO many players read this from the console. CS2 changed that, so this guide explains where the numbers are now and how to use them.

Where does the CS2 damage report appear?

When a round ends, look at the player portraits across the top of the screen. Under each enemy you damaged, the game shows your damage and your number of hits. It is on by default. It only stays for a short time before the next round starts.

If you miss it, hold Tab. The scoreboard keeps the figures visible a little longer and shows your running damage totals. Our scoreboard guide explains those totals.

What happened to the console damage print?

In CS:GO you could open the console after dying and read lines of damage given and taken. Official CS2 servers do not print that summary. The old sv_damage_print_enable setting is not part of CS2, and turning on cheats does not bring it back. Old configs that used con_filter tricks to show the print on screen also do nothing now.

Some community servers add their own damage summaries with plugins. That varies by server and does not apply to matchmaking. For a refresher on what still works, see our CS2 console guide.

How to turn the report on or off

The report is controlled by one client setting. Open the console and type:

• cl_disable_round_end_report 1 to hide it.
• cl_disable_round_end_report 0 to show it again. This is the default.

Type the command on its own to see the current value. Most players should leave it on. The information is free and useful.

Why hits matter more than you think

Damage alone can mislead. Thirty damage from one leg shot is a different story from thirty damage spread over four body hits through a smoke. The hit count tells you which happened. Many hits with low damage often means you were spraying at range or shooting through cover. One or two hits with high damage means your first shots were good but you did not finish.

How to use the CS2 damage report in a match

The report is most useful as communication. A few habits help.

1. Call damage with a number. Say "B apps player is hit for 80" rather than "I hit one". Teammates can then decide whether to swing.
2. Check before you call "lit". Players often think they did more than they did. The report keeps you honest.
3. Spot patterns. If you keep doing 20 to 40 damage in duels, your first shot is landing low. Work on crosshair placement at head height.
4. Value utility. If your HE or Molotov chipped several players, it bought your team time. Our utility buy guide covers when grenades are worth the money.

Note that the report arrives after the round, not at the moment you die. So during a live round, tell your team what you saw and trust your memory. The report then confirms it.

Reviewing duels after the match

The report is brief, so a demo is the best way to go deeper. Open the match replay from the main menu and jump to rounds where you lost a duel with damage on the enemy. Ask three questions. Did I peek first or get peeked? Did I stop moving before shooting? Did I have a teammate ready to trade? Short reviews like this turn the numbers into fixes. Our guide to trade kills explains the last point.

Using damage for practice

For drills, offline servers with cheats enabled can show live damage numbers above targets. That is helpful for learning which weapons kill in how many hits at range. It does not work in matchmaking. Pair it with the aim training guide for a structured routine.

Sources and checks

Commands and behaviour checked on 1 November 2026 against the CSDB guide to seeing damage in CS2 and other current CS2 guides. Valve may change the round end report in future updates.

damage report round end report console stats