0 Comments
Teams advantage Mirage (M1)
Records Mirage
Record/Time/Map
Val/Avg
Set by
Rival
Historical Maps winrate Last 6 months
Dust II
64%
Vertigo
52%
Inferno
37%
Ancient
11%
Nuke
8%
Overpass
4%
Mirage
0%
Last 5 maps
Dust II
0%
1
65
Vertigo
52%
23
9
Inferno
38%
29
24
Ancient
41%
27
8
Nuke
53%
17
23
Overpass
57%
23
15
Mirage
65%
37
2
Last 5 maps
Dust II
64%
14
16
Vertigo
0%
1
56
Inferno
75%
32
1
Ancient
52%
21
20
Nuke
45%
22
17
Overpass
53%
17
20
Mirage
65%
37
0
Last results
Past matches
- wlwwl
- lwwwl
Info
Map Analysis of GamerLegion vs FORZE by the Bo3.gg Team
FORZE on Mirage Analysis
FORZE demonstrated their prowers on Mirage, 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 FORZE on Mirage were KENSI, who contributed 25 kills, and shalfey, who added 26 kills to the team's efforts. Their exceptional skills and coordination were instrumental in securing the map win. Throughout the match on Mirage, the team inflicted a total of 10692 overall damage.
On the defensive side of Mirage, FORZE held their ground firmly, successfully defending 7 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
GamerLegion on Mirage Analysis
Mirage proved to be a challenging battleground for GamerLegion, 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 GamerLegion on Mirage included Zero, who contributed 24 kills, and RuStY, who added 24 kills. Despite their individual efforts, inflicting 10816 total damage, GamerLegion couldn't prevent FORZE from securing victory on Mirage
On the defensive side of Mirage, GamerLegion struggled to hold their ground, successfully defending 6 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Comments