Teams advantage Vertigo (M1)
Lineups
Lineup
Historical Maps winrate Last 6 months
Inferno
65%
Anubis
54%
Vertigo
C
47%
Dust II
38%
Ancient
35%
Mirage
26%
Nuke
0%
Last 5 maps
Inferno
0%
0
0
Anubis
0%
0
0
Vertigo
100%
1
0
Dust II
0%
0
0
Ancient
0%
0
0
Mirage
0%
0
0
Nuke
0%
0
0
Last 5 maps
Inferno
65%
34
5
Anubis
54%
48
1
Vertigo
53%
30
8
Dust II
38%
8
3
Ancient
35%
34
25
Mirage
26%
27
33
Nuke
0%
3
46
Last results
Head to head
Past matches
Info
Map Analysis of Clock Gaming vs ALTERNATE aTTaX by the Bo3.gg Team
Clock Gaming on Vertigo Analysis
Clock Gaming demonstrated their prowers on Vertigo, securing 13 out of 23 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 Clock Gaming on Vertigo were Quality, who contributed 21 kills, and hey044, who added 17 kills to the team's efforts. Their exceptional skills and coordination were instrumental in securing the map win. Throughout the match on Vertigo, the team inflicted a total of 8820 overall damage.
On the defensive side of Vertigo, Clock Gaming held their ground firmly, successfully defending 9 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
ALTERNATE aTTaX on Vertigo Analysis
Vertigo proved to be a challenging battleground for ALTERNATE aTTaX, as they managed to secure 10 out of 23 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for ALTERNATE aTTaX on Vertigo included ArroW, who contributed 21 kills, and PerX, who added 16 kills. Despite their individual efforts, inflicting 8478 total damage, ALTERNATE aTTaX couldn't prevent Clock Gaming from securing victory on Vertigo
On the defensive side of Vertigo, ALTERNATE aTTaX struggled to hold their ground, successfully defending 8 bomb plants. Their defensive coordination faced challenges on this map, making it difficult to maintain site control.
0 Comments