What the raw report is actually telling you
The headline losses number hides the more useful information, which is the loss breakdown by unit type on both sides. An attacker who lost mostly cheap infantry but kept their cavalry intact is in a very different position than one who lost their elite units, even if the total loss percentage looks similar. On defense, which unit types survived tells you what's actually still garrisoned and able to fight the next wave, which matters far more than the report's overall verdict.
Wall level and morale/moral bonus effects are easy to miss but change the read on a battle completely: a defender who "lost" but ground down a much larger attacking force because of a high wall level is arguably winning the war of attrition, and a small-account attacker hitting a much larger target may be getting a morale bonus that makes the raw combat numbers look better than they'd be against an equal-sized target.
Why a single report is rarely the full picture
One report tells you what happened in one wave. Repeated raids or scouting reports on the same target over time tell you whether their defense is growing, static, or already gone, which is the actual question you're trying to answer before committing a real attack. Screenshots pasted into chat get lost fast; without a searchable archive, you end up re-deciding the same target from memory instead of from evidence.
This is especially true for alliance-level defense coordination: a single member's report on an incoming attack is only useful if it reaches the people who need to reinforce, in a format they can act on quickly, not just as a screenshot buried in a chat scroll.
Keeping a report archive that's actually useful later
Our Battle Report Parser reads pasted reports or report screenshots and pulls out losses, attack/defense strength comparisons, and a clean summary you can share with your alliance, then keeps a searchable archive so you can look back at how a target's defense has changed over several hits instead of relying on memory or a scrollback search.
Common questions
What's the most important number in a Travian battle report?
The loss breakdown by unit type on both sides usually matters more than the headline result, since which units survived tells you what's actually still able to fight the next wave.
Why does wall level matter in a battle report?
A high wall level can let a defender grind down a much larger attacking force even while technically losing the battle, so wall effects change how you should read the outcome.
How do I keep track of many battle reports?
A searchable archive of parsed reports lets you see how a target's defense has changed over several hits, instead of relying on memory or scrolling back through chat screenshots.