[n0rul3z] Feigling vs. Toto
Result
The attacker won the battle.
Attacker
[n0rul3z] Feigling
- Total result
- +14,587,550
11,269,000 units lost
Defender
Toto
- Total result
- −67,344,550
136,170,500 units lost
Total results include 1 harvest report
- Units destroyed
- 147,439,500
- Loot
- 18,511,050
- Debris field
- 7,344,000
- Moon chance
- 20%
- Rounds
- 3
Details
| Attacker | Defender | |
|---|---|---|
| Metal | +7,003,995 | −41,694,295 |
| Crystal | +4,612,456 | −18,611,656 |
| Deuterium | +2,971,099 | −7,038,599 |
| Total | +14,587,550 | −67,344,550 |
| Honour points | +6,218 | +2,186 |
| Attacker | Defender | |
|---|---|---|
| Battle losses | −11,269,000 | −136,170,500 |
| Loot | +18,511,050 | −18,511,050 |
| Repaired defence | +87,337,000 | |
| 1 harvest report | +7,345,500 | |
| Total result | +14,587,550 | −67,344,550 |
| Metal | Crystal | Deuterium | Total | |
|---|---|---|---|---|
| Loot (75%) | 10,855,295 | 4,482,656 | 3,173,099 | 18,511,050 |
| Debris field | 4,373,700 | 2,970,300 | 7,344,000 | |
| Harvested | 4,373,700 | 2,971,800 | 7,345,500 |
| Metal | Crystal | Deuterium | Total | |
|---|---|---|---|---|
| Harvest report 1 | 4,373,700 | 2,971,800 | 7,345,500 |
Fleets
Attacker · [n0rul3z] Feigling
Weapons 160% · Shields 150% · Armour 160%
| Type | Before | Lost |
|---|---|---|
| Small Cargo | 2,500 | −50 |
| Light Fighter | 114,222 | −2,035 |
| Cruiser | 16,768 | −101 |
Defender · Toto destroyed
Weapons 120% · Shields 120% · Armour 120%
| Type | Before | Lost |
|---|---|---|
| Small Cargo | 2 | −2 |
| Large Cargo | 1,000 | −1,000 |
| Light Fighter | 50 | −50 |
| Recycler | 20 | −20 |
| Espionage Probe | 15 | −15 |
| Solar Satellite | 435 | −435 |
| Rocket Launcher | 30,000 | −30,000 |
| Light Laser | 1,000 | −1,000 |
| Heavy Laser | 500 | −500 |
| Gauss Cannon | 150 | −150 |
| Plasma Turret | 391 | −391 |
| Small Shield Dome | 1 | −1 |
| Large Shield Dome | 1 | −1 |
21,900 Rocket Launcher, 610 Light Laser, 355 Heavy Laser, 101 Gauss Cannon, 274 Plasma Turret, 1 Small Shield Dome, 1 Large Shield Dome could be repaired.
Comments
Log in to leave a comment. Login
No comments yet — be the first.