BC.Game have officially withdrawn from ROG JOURNEY Spring 2026, set to take place in Stockholm from March 23–28. Tournament organizers confirmed that the team will forfeit all scheduled matches, which will be recorded as walkovers. The decision further damages BC.Game’s position in the Valve Regional Standings (VRS), where they are already far from contention for upcoming top-tier events.
A string of poor results continues

Following the high-profile acquisition of the SAW core at the start of 2026 — reportedly for around $2.5 million — expectations around BC.Game were significant. The return of Oleksandr Kostyliev to the Tier-1 scene only added to the hype. However, results have fallen well short:
- last-place finish in the IEM Rio Europe qualifier
- inconsistent run at IEM Kraków (eliminated in Stage 2)
- losses to ECSTATIC and illwill at Parken Challenger
- disappointing 1-3 group stage exit at Roman Imperium Cup VI
The team has repeatedly struggled against opponents they were expected to beat, highlighting deeper issues.
Reason behind the withdrawal: chemistry issues
In a statement to HLTV, a BC.Game representative addressed the situation:
We’ve been strong in practice, but we haven’t delivered in officials. We’ve lost games we shouldn’t be losing.
The organization has decided to prioritize fixing internal synergy ahead of key upcoming events, including PGL Bucharest and IEM Atlanta.
Our full focus now is to fix our chemistry and make sure we deliver in the future.
Community reaction: frustration and doubt

The move sparked a wave of negative reactions across the CS2 community:
- “dead team… just disband”
- “s1mple era might actually be cooked”
- “what’s the point???”
Some fans are already calling the project a failure, while others question whether the roster can recover at all.
read more
What’s next?
With forfeited matches and additional VRS losses, BC.Game’s path to major tournaments becomes even more uncertain. The upcoming events — PGL Bucharest and IEM Atlanta — may define the future of this roster. If results don’t improve quickly, this ambitious project risks becoming another costly failure on the Tier-1 CS2 scene. For now, the key question remains: is this just a temporary setback — or the beginning of the end?

