How to Use Rust Combat Log Parser

Getting Your Combat Log

To analyze your combat data, you first need to get the raw log from the game. Here is how to do it:

Open the Console: While in-game, press the F1 key.
Type the Command: Type combatlog and press Enter. You can also use combatlog 100 to see the last 100 entries (default is 30).
Copy the Output: Highlight the text in the console window. It will look like a messy table. Press Ctrl + C (or Cmd + C) to copy it.
Paste and Analyze: Paste the text into the main input box. Your report appears automatically. You can also open a local .txt or .log file up to 5 MB. After editing the original text, click "Analyze changes" or press Cmd/Ctrl+Enter.

Understanding the Data

The raw combat log contains several columns. Here is what each one means and how we interpret it:

Field	Description
Time	Seconds before the log was captured. The report displays a stable time such as −01:33.71, preserving the order and sub-second timing of hits.
Attacker	The entity that dealt the damage. This can be a player, an animal, or the environment (e.g., "cold", "fall").
Target	The entity that received the damage.
Weapon	The weapon or tool used. We clean up these names (e.g., "rifle.ak" becomes "AK-47") for better readability.
Ammo	The type of ammunition used (e.g., "ammo.rifle.hv"). This helps identify if someone was using special ammo.
Area	The body part that was hit (e.g., "head", "chest", "leg"). Headshots usually deal double damage.
Distance	The distance between the attacker and the target in meters.
Old HP / New HP	The target's health before and after the hit. This is crucial for knowing how close you were to winning a fight.

Advanced Features

Steam Profile Integration

The combat log alone never names the player behind an id. Your full client log does, on its death lines — so if you paste that instead of only the console output, we identify whoever killed you and link their Steam profile. Everyone else can be renamed by hand.

Sharing & Exporting

Share view creates a link containing only your visible events and their participant names. Export image previews a PNG with summary + events, or just the summary, before you download it.

Filtering

Use the controls above the report to filter by players, weapons or time range. The general log and selection summary update together. Turn off PvP only to include creatures and structures.

Privacy

Your logs are processed in your browser. We don't save them to our servers unless you click "Share view" to save the visible selection. Identified SteamIDs are used for profile lookups.

Common Weapons Reference

These are the most popular weapons you will encounter in Rust combat logs. Understanding each weapon helps you interpret engagement distances, damage patterns, and ammo types.

AK-47 (Assault Rifle)

Full auto, rifle ammo. The most common PvP weapon in Rust and the one you will see most in combat logs.

LR-300

Lower recoil assault rifle, rifle ammo. Easier to control than the AK, popular among players who prefer consistency.

MP5A4

SMG, pistol ammo. Excels at close range with a high rate of fire. Common in monument fights.

Thompson

SMG, pistol ammo. A popular early-game weapon that is cheap to craft and effective in close-to-mid range.

Custom SMG

Craftable SMG, pistol ammo. The go-to budget automatic weapon, often the first full-auto gun players craft.

Bolt Action Rifle

Single shot, high damage, long range. Used for sniping and opening fights before switching to an automatic.

L96

Sniper rifle with the highest effective range in the game. One-shots headshots against most armor setups.

Semi-Auto Rifle (SAR)

Semi-auto, rifle ammo. The budget option for mid-range fights, very common in early-to-mid wipe combat logs.

Pump Shotgun

Close range, devastating damage. Can one-shot at close range. Watch for multiple pellet hits in the log.

Eoka Pistol

Primitive, unpredictable. Has a random fire delay. Seeing Eoka kills in a log usually means early-wipe chaos.

Compound Bow

Silent, can be deadly. Charged shots deal significant damage. No sound signature makes it great for ambushes.

Hunting Bow

Primitive ranged weapon. The first ranged weapon most players craft. Common in early-wipe beach fights.

Understanding Hit Areas

Damage in Rust varies depending on which body part is hit. The combat log records the exact hit area for every shot. Understanding these multipliers helps you evaluate how effective your aim was and how much damage each shot actually dealt.

Hit Area	Damage Multiplier	Notes
Head	2x damage	Highest priority shots. A headshot deals double the weapon's base damage. Helmets reduce this but it remains the most impactful area.
Chest	1x damage	Standard base damage. The largest target area and the most commonly hit zone in most fights.
Stomach	1x damage	Same base damage as chest. Often hit when aiming center mass at mid-to-long range.
Arm	0.5x damage	Half damage. Arms often absorb shots aimed at the chest, especially during strafing.
Hand	0.5x damage	Half damage. A small hit area that is rarely hit intentionally.
Leg	0.5x damage	Half damage. Frequent in long-range fights where recoil pulls shots low.
Foot	0.5x damage	Half damage. Usually hit when an opponent is behind low cover or running at a distance.

Tips for Analyzing Your Combat Log

Getting the most out of your combat log analysis takes practice. Here are some practical tips to help you improve your gameplay by studying your fights.

1
Look at hit areas to evaluate your aim. A high percentage of head and chest hits means your crosshair placement is solid. Too many arm and leg hits suggests you need to work on recoil control.
2
Compare distances to understand your engagement range. If you consistently lose fights beyond 50 meters, you may want to practice long-range sprays or switch to a weapon better suited for range.
3
Check health values to see how close fights were. The summary shows each player’s last observed HP within your selection. If your last hit left an enemy at 5 HP, that is the last recorded value; the log may not show later healing or damage. An attacker’s HP remains unknown until they appear as a target.
4
Use the PvP filter to ignore animal and environment damage. Combat logs include everything: bear attacks, fall damage, and cold exposure. Filter to PvP only to focus on the fights that matter for improving.
5
Use time range filter to isolate specific fights. A long play session might have dozens of encounters mixed together. Narrow the time range to focus on one fight at a time for a clearer picture.
6
Share results with teammates to review fights together. Use the share link or image export to send your combat log to your team. Reviewing fights together helps coordinate better in future encounters.

Frequently Asked Questions

What is the combat log in Rust?

The combat log is a built-in feature in Rust that records all damage events involving your character. Every time you take or deal damage, the game logs the details including the attacker, target, weapon, body part hit, distance, and health values. You access it by typing combatlog in the in-game console (F1). This tool parses that raw text into a visual, easy-to-read format.

How do I open the console in Rust?

Press F1 while in-game to open the developer console. Once it is open, type combatlog and press Enter. The log output will appear in the console window. You can then highlight and copy the text.

How many entries does combatlog show?

By default, typing combatlog shows the last 30 entries. If you want to see more, you can specify a number: for example, combatlog 100 will display up to the last 100 damage events. This is useful for reviewing longer play sessions.

Is my data safe?

Your combat text is parsed in your browser. Identified SteamIDs are sent to the profile lookup endpoint. Combat events are saved only when you choose "Share view", and only the visible selection is included. Downloading an image does not save your combat events to our server.

Can I see who killed me?

Yes. The combat log records the attacker and target for every damage event. When your health reaches zero, the log shows who dealt the final blow, what weapon they used, the distance, and which body part they hit. Paste your full client log rather than just the console output and we can go one step further: it records the killer's name and Steam ID on a separate line, which we match back to the kill so you get their real name and a link to their profile.

What does the "info" column mean?

The info column describes the type of damage event. Common values include: projectile (a bullet or arrow hit), melee (a melee weapon hit), bite (animal attack), and killed (the final blow that resulted in a death). This field helps you distinguish between different types of combat interactions in your log.

Why are some players shown as numbers?

Because Rust does not put their name there. The combat log refers to other players by an internal server id such as player_804072, which is not a Steam ID and cannot be looked up. The one exception is whoever killed you: your client log records that death with the killer's name and Steam ID, so pasting the full log lets us resolve it. Any other player can be renamed by clicking on their name.

Can I share my combat log?

Yes. After parsing your combat log, you can share it in two ways: generate a unique URL that anyone can visit to see your parsed results, or export the analysis as a high-quality image that you can post on Discord, Twitter, Reddit, or send directly to teammates.

Does this work on modded servers?

Yes. The combat log format is part of the base Rust client and is the same regardless of whether you are playing on a vanilla or modded server. As long as the combatlog command works in the console, you can paste the output here and it will be parsed correctly.

Is this tool affiliated with Facepunch?

No. This is an unofficial, fan-made tool and is not affiliated with, endorsed by, or connected to Facepunch Studios (the developers of Rust) in any way. It is an independent community project built to help players analyze their combat performance.