0 Comments
Lineups
Lineup
Starter
Starter
Starter
Starter
Starter
Lineup
Starter
Starter
Starter
Starter
Starter
Last results
Head to head
Past matches
- wwwww
- wwwlw
Teams advantage
Historical Maps winrate Last 6 months
Sunset
86%
Lotus
80%
Pearl
75%
Ascent
50%
Bind
50%
Haven
40%
Split
17%
Fracture
0%
Abyss
0%
Last 5 maps
Sunset
86%
7
Lotus
80%
5
Pearl
75%
4
Ascent
50%
4
Bind
0%
1
Haven
80%
5
Split
100%
2
Fracture
50%
2
Abyss
50%
2
Last 5 maps
Sunset
0%
1
Lotus
0%
2
Pearl
0%
1
Ascent
0%
0
Bind
50%
2
Haven
40%
5
Split
83%
6
Fracture
50%
6
Abyss
50%
4
Info
Match analysis of RIDDLE ORDER vs REJECT by the Bo3.gg Team
In the Valorant match between RIDDLE ORDER and REJECT, a series of thrilling battles unfolded with a score of 3-1, on the following maps: Fracture, Pearl, Lotus, Haven, and victory was secured by RIDDLE ORDER. The MVP of this match was .
RIDDLE ORDER analytics
The team RIDDLE ORDER secured 0 out of 0 rounds, showcasing their ability to control and adapt to various situations. They won on the maps Pearl, Lotus, Haven. They also successfully set 0 bombs during the match.
The standout players for RIDDLE ORDER were contributed 0 kills and contributed 0 kills. Their exceptional skills played a pivotal role in securing the win. Thanks to coordinated effort, the team inflicted 0 overall damage.
On the defensive side, RIDDLE ORDER held their ground firmly, successfully defending 0 bomb plants. Their defensive coordination and site control proved to be crucial.
REJECT analytics
The team REJECT managed to secure 0 out of 0 rounds, but faced challenges in adapting to their opponent's strategies. Capturing 0 plants during the match did not lead the team to victory.
The standout players for REJECT were contributed 0 kills and contributed 0 kills. 0 of total damage by REJECT could not prevent RIDDLE ORDER from securing the victory
On the defensive side, REJECT struggled to hold their ground, successfully defending 0 bomb plants. Their defensive coordination faced challenges, making it difficult to maintain site control.
0 Comments