0 Commentaires
avantage aux équipes Anubis (M1)
Records Anubis
Record/Temps/Carte
Val/M
Établi par
Adversaire
Éliminations avec Glock en moyenne par carte
31.4482
Dégâts avec Glock en moyenne (par tour)
144.1
Dégâts avec AK47 en moyenne (par tour)
59.825.2
Éliminations avec Glock en moyenne par carte
31.4482
Dégâts avec Glock en moyenne (par tour)
14.84.1
Score du joueur (round)
36511010
Dégâts (total/round)
40073
Score du joueur (round)
38391010
As du joueur
1
Multikills x-
4
Informations
Map Analysis of CYBERSHOKE vs CPH Wolves by the Bo3.gg Team
CYBERSHOKE on Anubis Analysis
CYBERSHOKE demonstrated their prowers on Anubis, securing 13 out of 21 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 CYBERSHOKE on Anubis were lov1kus, who contributed 17 kills, and notineki, who added 16 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 8059 overall damage.
On the defensive side of Anubis, CYBERSHOKE 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.
CPH Wolves on Anubis Analysis
Anubis proved to be a challenging battleground for CPH Wolves, as they managed to secure 8 out of 21 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for CPH Wolves on Anubis included Fessor, who contributed 17 kills, and Szejn, who added 14 kills. Despite their individual efforts, inflicting 6894 total damage, CPH Wolves couldn't prevent CYBERSHOKE from securing victory on Anubis
On the defensive side of Anubis, CPH Wolves 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 Commentaires