0 Commentaires
Records Inferno
Record/Temps/Carte
Val/M
Établi par
Adversaire
Plantation de bombe rapide (sec)
00:32s01:23s
Dégâts des grenades HE en moyenne (par tour)
12.83.4
Dégâts des cocktails Molotov en moyenne (par tour)
10.62
Dégâts des grenades HE en moyenne (par tour)
13.43.4
Fumigènes lancés en moyenne sur une carte
2414.2369
Fumigènes lancés en moyenne sur une carte
2214.2369
Score du joueur (round)
48051010
Score du joueur (round)
42821010
Dégâts (total/round)
38573
Score du joueur (round)
38231010
Informations
Map Analysis of FAVBET vs Viperio by the Bo3.gg Team
Viperio on Inferno Analysis
Viperio demonstrated their prowers on Inferno, securing 13 out of 24 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 Viperio on Inferno were Swicher, who contributed 18 kills, and dezt, 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 Inferno, the team inflicted a total of 8902 overall damage.
On the defensive side of Inferno, Viperio 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.
FAVBET on Inferno Analysis
Inferno proved to be a challenging battleground for FAVBET, as they managed to secure 11 out of 24 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for FAVBET on Inferno included bondik, who contributed 20 kills, and mAriX, who added 14 kills. Despite their individual efforts, inflicting 8686 total damage, FAVBET couldn't prevent Viperio from securing victory on Inferno
On the defensive side of Inferno, FAVBET 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 Commentaires