0 Comments
91
106
25
-15
344
12:18
23
2
-7%
Teams advantage Dust II (M3)
Records Dust II
Record/Time/Map
Val/Avg
Set by
Rival
Flash blinded on a map (opp)
8430
Smoke thrown on a map
2915.0371
Smoke thrown on a map
2715.0371
AWP kills on a map
206.5798
AWP damage (avg/round)
65.221.6
Flash blinded on a map (opp)
8230
AK47 damage (avg/round)
57.825.3
Flash duration on a map (sec)
01:58s00:39s
Flash blinded on a map (opp)
8630
Smoke thrown on a map
2815.0371
Info
Map Analysis of Bad News Bears vs BLUEJAYS by the Bo3.gg Team
BLUEJAYS on Dust II Analysis
BLUEJAYS demonstrated their prowers on Dust II, securing 16 out of 30 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 BLUEJAYS on Dust II were CacaNito, who contributed 37 kills, and aidKiT, who added 21 kills to the team's efforts. Their exceptional skills and coordination were instrumental in securing the map win. Throughout the match on Dust II, the team inflicted a total of 11181 overall damage.
On the defensive side of Dust II, BLUEJAYS held their ground firmly, successfully defending 10 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
Bad News Bears on Dust II Analysis
Dust II proved to be a challenging battleground for Bad News Bears, as they managed to secure 14 out of 30 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for Bad News Bears on Dust II included Swahn, who contributed 23 kills, and Shakezullah, who added 21 kills. Despite their individual efforts, inflicting 10328 total damage, Bad News Bears couldn't prevent BLUEJAYS from securing victory on Dust II
On the defensive side of Dust II, Bad News Bears struggled to hold their ground, successfully defending 9 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Comments