89
58
18
+31
412
11:12
24
0
+15%
Przewaga drużyn Anubis (M2)
Rekordy Anubis
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Szybkie podłożenie bomby (sec)
00:26s01:30s
Szybkie podłożenie bomby (sec)
00:29s01:30s
Szybkie podłożenie bomby (sec)
00:29s01:30s
Szybkie podłożenie bomby (sec)
00:21s01:30s
Zabójstwa za pomocą AK47 na mapie
146.7327
Rzucenie dymówki na mapie
2715.0373
Zabójstwa za pomocą USP na mapie
41.6158
Obrażenia od USP (avg/round)
13.74.6
Obrażenia (total/round)
41273
Wynik gracza (runda)
38841012
Informacja
Map Analysis of Question Mark vs 500 by the Bo3.gg Team
Question Mark on Anubis Analysis
Question Mark demonstrated their prowers on Anubis, securing 16 out of 23 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 Question Mark on Anubis were Ganginho, who contributed 24 kills, and nifee3, 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 Anubis, the team inflicted a total of 9480 overall damage.
On the defensive side of Anubis, Question Mark held their ground firmly, successfully defending 14 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
500 on Anubis Analysis
Anubis proved to be a challenging battleground for 500, as they managed to secure 7 out of 23 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for 500 on Anubis included KalubeR, who contributed 16 kills, and REDSTAR, who added 14 kills. Despite their individual efforts, inflicting 7198 total damage, 500 couldn't prevent Question Mark from securing victory on Anubis
On the defensive side of Anubis, 500 struggled to hold their ground, successfully defending 6 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Komentarze