0 Komentarze
Przewaga drużyn Mirage (M2)
Rekordy Mirage
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Szybkie podłożenie bomby (sec)
00:31s01:26s
Obrażenia od granatu (avg/round)
12.63.4
Zabójstwa za pomocą M4A1 na mapie
94.491
Obrażenia od GLOCK (avg/round)
11.14
Obrażenia od USP (avg/round)
14.34.7
Obrażenia od koktajla Mołotowa (śr./runda)
7.72
Obrażenia od AK-47(śr./runda)
65.625.3
Zabójstwa za pomocą USP na mapie
31.6074
Rzucenie dymówki na mapie
1714.6931
Eco wygrywa pełny zakup
1
Informacja
Map Analysis of FlyQuest vs Natus Vincere by the Bo3.gg Team
Natus Vincere on Mirage Analysis
Natus Vincere demonstrated their prowers on Mirage, securing 13 out of 19 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 Natus Vincere on Mirage were iM, who contributed 19 kills, and w0nderful, who added 14 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 7341 overall damage.
On the defensive side of Mirage, Natus Vincere held their ground firmly, successfully defending 6 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
FlyQuest on Mirage Analysis
Mirage proved to be a challenging battleground for FlyQuest, as they managed to secure 6 out of 19 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for FlyQuest on Mirage included INS, who contributed 17 kills, and Liazz, who added 8 kills. Despite their individual efforts, inflicting 5837 total damage, FlyQuest couldn't prevent Natus Vincere from securing victory on Mirage
On the defensive side of Mirage, FlyQuest struggled to hold their ground, successfully defending 5 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Komentarze