0 Kommentare
Teamvorteil Inferno (M1)
Datensätze Inferno
Rekord/Zeit/Karte
Wert/D
Setzen durch
Rivael
Runden-Siegesserie
113
Schnelle Bombenanlage (sec)
00:27s01:30s
Rauch auf eine Karte geworfen
1815.0371
AWP Kills auf der Karte
136.5798
Flash Dauer auf der Karte (sec)
01:14s00:39s
M4A1 Kills auf der Karte
94.6963
M4A4 Kills auf der Karte
73.6448
M4A4 Schaden (avg/round)
43.312.7
GLOCK Kills auf der Karte
51.4398
GLOCK Schaden (avg/round)
21.63.8
Info
Map Analysis of ALTERNATE aTTaX vs EYEBALLERS by the Bo3.gg Team
ALTERNATE aTTaX on Inferno Analysis
ALTERNATE aTTaX demonstrated their prowers on Inferno, securing 15 out of 18 rounds, showcasing their ability to control and adapt to various situations on this specific map. Victory on this map contributed to their overall success in the match.
The standout players for ALTERNATE aTTaX on Inferno were PANIX, who contributed 21 kills, and awzek, who added 19 kills to the team's efforts. Their exceptional skills and coordination were instrumental in securing the map win. Throughout the match on Inferno, the team inflicted a total of 7941 overall damage.
On the defensive side of Inferno, ALTERNATE aTTaX held their ground firmly, successfully defending 11 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
EYEBALLERS on Inferno Analysis
Inferno proved to be a challenging battleground for EYEBALLERS, as they managed to secure 3 out of 18 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for EYEBALLERS on Inferno included sapec, who contributed 10 kills, and Svedjehed, who added 9 kills. Despite their individual efforts, inflicting 4618 total damage, EYEBALLERS couldn't prevent ALTERNATE aTTaX from securing victory on Inferno
On the defensive side of Inferno, EYEBALLERS struggled to hold their ground, successfully defending 0 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Kommentare