0 Kommentare
Teamvorteil Inferno (M1)
Datensätze Inferno
Rekord/Zeit/Karte
Wert/D
Setzen durch
Rivael
Flash Dauer auf der Karte (sec)
01:16s00:39s
Flash geblendet auf der Karte (opp)
6030
Tec-9 Schaden (avg/round)
13.23.4
Molotov Kills auf der Karte
31.0849
Molotov Schaden (avg/round)
12.12
Flash Dauer auf der Karte (sec)
02:18s00:39s
Flash geblendet auf der Karte (opp)
8530
HE Schaden (avg/round)
13.73.4
Tötungen auf der Karte
29.9217.5558
Schüsse (total/round)
8816
Info
Map Analysis of Movistar Riders vs Sangal by the Bo3.gg Team
Movistar Riders on Inferno Analysis
Movistar Riders demonstrated their prowers on Inferno, securing 16 out of 22 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 Movistar Riders on Inferno were SunPayus, who contributed 30 kills, and DeathZz, who added 18 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 9144 overall damage.
On the defensive side of Inferno, Movistar Riders held their ground firmly, successfully defending 12 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
Sangal on Inferno Analysis
Inferno proved to be a challenging battleground for Sangal, as they managed to secure 6 out of 22 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for Sangal on Inferno included ScrunK, who contributed 13 kills, and S3NSEY, who added 12 kills. Despite their individual efforts, inflicting 6119 total damage, Sangal couldn't prevent Movistar Riders from securing victory on Inferno
On the defensive side of Inferno, Sangal struggled to hold their ground, successfully defending 3 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Kommentare