[TML] Epylon Corporation vs. [Tut] Hagen
Result
The attacker won the battle.
Attacker
[TML] Epylon Corporation
- Total result
- +1,455,406,981
284,000 units lost
Defender
[Tut] Hagen
- Total result
- −1,640,585,081
611,461,500 units lost
Total results include 5 follow-ups · 1 harvest report
- Units destroyed
- 611,745,500
- Loot
- 523,625,869
- Debris field
- 424,943,400
- Rounds
- 6
Details
| Attacker | Defender | |
|---|---|---|
| Metal | +966,537,100 | −1,060,482,300 |
| Crystal | +283,609,253 | −374,778,653 |
| Deuterium | +205,260,628 | −205,324,128 |
| Total | +1,455,406,981 | −1,640,585,081 |
| Honour points | −762 | 0 |
| Attacker | Defender | |
|---|---|---|
| Battle losses | −284,000 | −611,461,500 |
| Loot | +523,625,869 | −523,625,869 |
| Repaired defence | +4,204,000 | |
| 5 follow-ups | +506,785,712 | −509,701,712 |
| 1 harvest report | +425,279,400 | |
| Total result | +1,455,406,981 | −1,640,585,081 |
| Metal | Crystal | Deuterium | Total | |
|---|---|---|---|---|
| Loot (50%) | 383,171,200 | 36,195,302 | 104,259,367 | 523,625,869 |
| Debris field | 212,382,800 | 212,560,600 | 424,943,400 | |
| Harvested | 212,550,800 | 212,728,600 | 425,279,400 |
| Attacker | Defender | |
|---|---|---|
| Follow-up 1 | +261,716,934 | −262,778,934 |
| Follow-up 2 | +130,806,467 | −131,488,467 |
| Follow-up 3 | +65,333,878 | −65,771,878 |
| Follow-up 4 | +32,635,464 | −33,055,464 |
| Follow-up 5 | +16,292,969 | −16,606,969 |
| Metal | Crystal | Deuterium | Total | |
|---|---|---|---|---|
| Harvest report 1 | 212,550,800 | 212,728,600 | 425,279,400 |
Fleets
Attacker · [TML] Epylon Corporation
Weapons 200% · Shields 190% · Armour 200%
| Type | Before | Lost |
|---|---|---|
| Small Cargo | 55,000 | −71 |
| Cruiser | 8,008 | 0 |
| Battlecruiser | 8,008 | 0 |
Defender · [Tut] Hagen destroyed
Weapons 180% · Shields 180% · Armour 200%
| Type | Before | Lost |
|---|---|---|
| Small Cargo | 49,703 | −49,703 |
| Large Cargo | 33,976 | −33,976 |
| Solar Satellite | 127 | −127 |
| Rocket Launcher | 2,310 | −2,310 |
2,102 Rocket Launcher could be repaired.
Comments
Log in to leave a comment. Login
No comments yet — be the first.