0 Komentarze
Przewaga drużyn Inferno (M0)
Rekordy Inferno
Rekord/Czas/Mapa
W/Ś
Ustaw według
Rywal
Obrażenia od granatu (avg/round)
16.83.4
Zabójstwa za pomocą USP na mapie
11.6074
Zabójstwa HE na mapie
11.1227
Obrażenia od granatu (avg/round)
15.23.4
Zabójstwa za pomocą GLOCK na mapie
21.4456
Obrażenia od GLOCK (avg/round)
37.74
Zabójstwa za pomocą AK47 na mapie
56.5888
Obrażenia od AK-47(śr./runda)
58.525.3
Zabójstwa za pomocą GLOCK na mapie
31.4456
Obrażenia od GLOCK (avg/round)
354
Informacja
Map Analysis of Metizport vs EYEBALLERS by the Bo3.gg Team
Metizport on Inferno Analysis
Metizport demonstrated their prowers on Inferno, securing 4 out of 6 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 Metizport on Inferno were nilo, who contributed 11 kills, and Jackinho, who added 8 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 2807 overall damage.
On the defensive side of Inferno, Metizport held their ground firmly, successfully defending 4 bomb plants. Their defensive coordination and site control on this map proved to be crucial in their victory.
EYEBALLERS on Inferno Analysis
Inferno proved to be a challenging battleground for EYEBALLERS, as they managed to secure 2 out of 6 rounds on this map. Adapting to their opponent's strategies on this particular map presented difficulties for them.
The standout players for EYEBALLERS on Inferno included HEAP, who contributed 8 kills, and Golden, who added 3 kills. Despite their individual efforts, inflicting 1812 total damage, EYEBALLERS couldn't prevent Metizport from securing victory on Inferno
On the defensive side of Inferno, EYEBALLERS 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 Komentarze