[ExT] Xilenxe vs. [OLFR] Victim IV
Result
The attacker won the battle.
Attacker
[ExT] Xilenxe
- Total result
- +208,984,319
21,930,000 units lost
Defender
[OLFR] Victim IV
- Total result
- −362,240,919
301,210,000 units lost
Total results include 4 follow-ups · 2 harvest reports
- Units destroyed
- 323,140,000
- Loot
- 7,176,000
- Debris field
- 169,869,000
- Rounds
- 5
Details
| Attacker | Defender | |
|---|---|---|
| Metal | +92,882,061 | −156,788,061 |
| Crystal | +63,704,400 | −113,030,000 |
| Deuterium | +52,397,858 | −92,422,858 |
| Total | +208,984,319 | −362,240,919 |
| Honour points | −36,889 | +4,045 |
| Attacker | Defender | |
|---|---|---|
| Battle losses | −21,930,000 | −301,210,000 |
| Loot | +7,176,000 | −7,176,000 |
| 4 follow-ups | +53,854,919 | −53,854,919 |
| 2 harvest reports | +169,883,400 | |
| Total result | +208,984,319 | −362,240,919 |
| Metal | Crystal | Deuterium | Total | |
|---|---|---|---|---|
| Loot (50%) | 2,392,000 | 0 | 4,784,000 | 7,176,000 |
| Debris field | 95,859,000 | 74,010,000 | 169,869,000 | |
| Harvested | 95,859,000 | 74,024,400 | 169,883,400 |
| Attacker | Defender | |
|---|---|---|
| Follow-up 1 | +28,722,624 | −28,722,624 |
| Follow-up 2 | +14,361,312 | −14,361,312 |
| Follow-up 3 | +7,180,655 | −7,180,655 |
| Follow-up 4 | +3,590,328 | −3,590,328 |
| Metal | Crystal | Deuterium | Total | |
|---|---|---|---|---|
| Harvest report 1 | 40,000,000 | 40,000,000 | 80,000,000 | |
| Harvest report 2 | 55,859,000 | 34,024,400 | 89,883,400 |
Fleets
Attacker · [ExT] Xilenxe
| Type | Before | Lost |
|---|---|---|
| Battlecruiser | 9,826 | −258 |
Defender · [OLFR] Victim IV destroyed
| Type | Before | Lost |
|---|---|---|
| Small Cargo | 2,876 | −2,876 |
| Large Cargo | 280 | −280 |
| Light Fighter | 1,580 | −1,580 |
| Heavy Fighter | 143 | −143 |
| Cruiser | 2,439 | −2,439 |
| Battleship | 55 | −55 |
| Recycler | 1,681 | −1,681 |
| Espionage Probe | 427 | −427 |
| Bomber | 251 | −251 |
| Destroyer | 36 | −36 |
| Deathstar | 3 | −3 |
| Battlecruiser | 1,374 | −1,374 |
Comments
Log in to leave a comment. Login