0 Komentarze
Przewaga drużyn Mirage (M0)
Rekordy Mirage
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Szybkie podłożenie bomby (sec)
00:28s01:26s
Obrażenia od koktajla Mołotowa (śr./runda)
10.82
Zabójstwa za pomocą M4A1 na mapie
84.491
Obrażenia od M4A1 (avg/round)
50.516.3
Zabójstwa za pomocą USP na mapie
31.6074
Obrażenia od USP (avg/round)
13.64.7
Zabójstwa za pomocą M4A1 na mapie
94.491
Zabójstwa za pomocą Galil kna mapie
41.8171
Obrażenia od Galil (avg/round)
23.55.8
Zabójstwa za pomocą GLOCK na mapie
31.4456
Informacja
Map Analysis of The MongolZ vs BLEED by the Bo3.gg Team
The MongolZ on Mirage Analysis
The MongolZ demonstrated their prowers on Mirage, securing 13 out of 17 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 The MongolZ on Mirage were mzinho, who contributed 16 kills, and 910, who added 17 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 7045 overall damage.
On the defensive side of Mirage, The MongolZ held their ground firmly, successfully defending 5 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
BLEED on Mirage Analysis
Mirage proved to be a challenging battleground for BLEED, as they managed to secure 4 out of 17 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for BLEED on Mirage included CYPHER, who contributed 13 kills, and nawwk, who added 14 kills. Despite their individual efforts, inflicting 5597 total damage, BLEED couldn't prevent The MongolZ from securing victory on Mirage
On the defensive side of Mirage, BLEED struggled to hold their ground, successfully defending 4 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Komentarze