0 Komentarze
Przewaga drużyn Inferno (M2)
Rekordy Inferno
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Szybkie podłożenie bomby (sec)
00:33s01:27s
Obrażenia od GLOCK (avg/round)
11.23.9
Zabójstwa za pomocą GLOCK na mapie
31.4429
Obrażenia od koktajla Mołotowa (śr./runda)
6.52
Obrażenia od USP (avg/round)
15.54.7
Rzucenie dymówki na mapie
2214.8354
Obrażenia od Galil (avg/round)
185.7
Asysty na mapie
114.3808
Obrażenia (total/round)
41873
Wynik gracza (runda)
35731011
Informacja
Map Analysis of EYEBALLERS vs The Witchers by the Bo3.gg Team
EYEBALLERS on Inferno Analysis
EYEBALLERS demonstrated their prowers on Inferno, securing 13 out of 22 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 EYEBALLERS on Inferno were Peppzor, who contributed 18 kills, and HEAP, who added 15 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 8443 overall damage.
On the defensive side of Inferno, EYEBALLERS held their ground firmly, successfully defending 3 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
The Witchers on Inferno Analysis
Inferno proved to be a challenging battleground for The Witchers, as they managed to secure 9 out of 22 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for The Witchers on Inferno included Sdaim, who contributed 21 kills, and SynyX, who added 19 kills. Despite their individual efforts, inflicting 8072 total damage, The Witchers couldn't prevent EYEBALLERS from securing victory on Inferno
On the defensive side of Inferno, The Witchers struggled to hold their ground, successfully defending 2 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Komentarze