0 Komentarze
Przewaga drużyn Mirage (M3)
Rekordy Mirage
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Szybkie podłożenie bomby (sec)
00:31s01:30s
Obrażenia od koktajla Mołotowa (śr./runda)
9.32
Zabójstwa za pomocą AK47 na mapie
156.732
Obrażenia od AK-47(śr./runda)
66.125.3
Obrażenia od GLOCK (avg/round)
11.43.8
Rzucenie dymówki na mapie
2015.0371
Zabójstwa za pomocą AK47 na mapie
136.732
Wynik gracza (runda)
35161012
Multikill x-
4
Clutch (przeciwnicy)
2
Informacja
Map Analysis of EYEBALLERS vs Movistar Riders by the Bo3.gg Team
EYEBALLERS on Mirage Analysis
EYEBALLERS demonstrated their prowers on Mirage, securing 16 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 Mirage were Peppzor, who contributed 24 kills, and flusha, who added 18 kills to the team's efforts. Their exceptional skills and coordination were instrumental in securing the map win. Throughout the match on Mirage, the team inflicted a total of 8979 overall damage.
On the defensive side of Mirage, EYEBALLERS held their ground firmly, successfully defending 4 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
Movistar Riders on Mirage Analysis
Mirage proved to be a challenging battleground for Movistar Riders, as they managed to secure 6 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 Movistar Riders on Mirage included Martinez, who contributed 20 kills, and mopoz, who added 14 kills. Despite their individual efforts, inflicting 7281 total damage, Movistar Riders couldn't prevent EYEBALLERS from securing victory on Mirage
On the defensive side of Mirage, Movistar Riders struggled to hold their ground, successfully defending 3 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Komentarze