0 Kommentare
35
85
3
-50
222
4:15
6
1
-4%
Teamvorteil Inferno (M1)
Datensätze Inferno
Rekord/Zeit/Karte
Wert/D
Setzen durch
Rivael
Runden-Siegesserie
133
M4A1 Kills auf der Karte
104.6963
Molotov Schaden (avg/round)
7.32
Galil Kills auf der Karte
51.8064
Galil Schaden (avg/round)
26.35.6
GLOCK Schaden (avg/round)
12.33.8
HE Schaden (avg/round)
11.33.4
USP Kills auf der Karte
31.616
USP Schaden (avg/round)
17.94.6
Schaden (total/round)
40073
Info
Map Analysis of Young Ninjas vs Tricked Future by the Bo3.gg Team
Young Ninjas on Inferno Analysis
Young Ninjas demonstrated their prowers on Inferno, securing 16 out of 19 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 Young Ninjas on Inferno were maxster, who contributed 19 kills, and Adamb, 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 8674 overall damage.
On the defensive side of Inferno, Young Ninjas 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.
Tricked Future on Inferno Analysis
Inferno proved to be a challenging battleground for Tricked Future, as they managed to secure 3 out of 19 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for Tricked Future on Inferno included Ashawn2k, who contributed 11 kills, and z_nan, who added 9 kills. Despite their individual efforts, inflicting 4209 total damage, Tricked Future couldn't prevent Young Ninjas from securing victory on Inferno
On the defensive side of Inferno, Tricked Future struggled to hold their ground, successfully defending 0 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Kommentare