siuhy Free Agent After Liquid Exit: An Audit Report on a Failed 16-Month Experiment

185 maps. A 0.87 rating. If the entire Team Liquid chapter of Kamil "siuhy" Szkaradek could be compressed into two numbers, those are the two. In August 2026, Liquid confirmed that the Polish in-game leader is no longer part of the team. He has been released as a free agent — no transfer fee, no buyout clause. The decision did not arrive suddenly. From the promising name that arrived on loan from MOUZ in April 2026 to the failed import benched in July 2026 — those sixteen months form an audit trail of sequential failure.

I begin this piece with numbers, because in this story a receipt matters more than an opinion. Two competing narratives surround siuhy. The first: he was a good IGL whom the team failed to use. The second: he was overhyped, his MOUZ form never translated. If both can be true, then the real question is not "good or bad" — the real question is which data sustains which claim, and which claim is merely narrative pressure. In my two decades of industry observation I follow one rule here: the back-test came first; the byline was just a receipt. Today that receipt is issued in Liquid's name.

Context: CS2's calendar and Liquid's IGL roulette

CS2 is a mechanics-driven tactical FPS. It lacks Riot-style biweekly patch culture; Valve ships a few large updates per year. One major consequence follows — in CS2, team failure generally cannot be explained by "the patch broke our playstyle." The causes must be sought inside shot-calling, individual form, and team chemistry. In siuhy's case, the source material contains no patch, map-pool, or meta context. So a meta-based explanation is unsupported here; that is a limitation of the source, and I am flagging it explicitly.

At the centre of the calendar sits the Valve-sanctioned Major. In CS2 the Major is the highest-prestige championship, and its Swiss format is unforgiving. In Swiss rounds, teams with identical win-loss records face each other, and early series are often BO1. That means the format is a trap for unstable rosters — one or two bad maps and the playoff door shuts. Mid-tier third-party events such as FISSURE Playground #2 offer a softer environment. The difference between these two tiers is the key to understanding Liquid's story.

Liquid's biggest structural problem is not siuhy — it is the constant turnover of the shot-calling role. In a short span the team cycled through at least four IGLs: Casper "cadiaN" Møller, Russel "Twistzz" Van Dulken, then siuhy, and now Johnny "JT" Theodosiou. In CS2, frequent IGL turnover is a classic marker of strategic identity collapse. Each new caller rebuilds systems from scratch, chemistry erodes, and the team spins in a cycle without end. siuhy's exit is not the end of that cycle — it is probably the start of the next lap.

Core analysis: the receipts, one by one

Let me lay out the timeline first. In April 2026 siuhy arrived at Liquid on loan from MOUZ — a top-down Europe-to-North-America talent flow, where a top European organisation lends surplus talent and an NA organisation buys in. In July 2026 he was benched. The team then tested a new direction internally — installing JT as caller — before ending the sixteen-month tenure and releasing him to free agency. This is not a panic move; it is a phased reset, where an alternative was tried first and the cut came second.

Now the sharpest claim. Liquid played three Majors, and reached the playoffs in none of them. The Major map record is 5-11, a 31 percent win rate — far below the "competitive band" expected of a Liquid-tier roster. Zero playoffs across three separate Majors is not an incidental event; it signals a structural problem. And that zero-playoff record implies the team repeatedly exited in the early rounds — where BO1 volatility is highest, and where survival without strong calling is hardest.

What was the team's best result? A top-four at FISSURE Playground #2 — a lower-tier third-party event. Here the classic pattern emerges: decent at mid-tier, exposed at the top tier. In football terms this is a "flat-track bully"; in CS2 it means the team functions in practice and low-pressure matches but collapses under Major pressure. When your best result at a top event is a top-four, the claim stays modest — little room to inflate, and limited backlash risk.

The source says there were "several strong pieces around siuhy" — an important claim, because it shifts the weight of failure away from a talent deficit and toward leadership and cohesion. The roster was not a talent-deficit rebuild; it was an integration failure. If the pieces really were strong, the question is no longer "whose skill is low" — it is whether anyone could correctly direct those pieces together.

Still, the numbers do not stop. A 0.87 rating across 185 maps — low even by IGL standards, and sitting in a band better matched to underperformance than elite calling. Here is the cruellest accounting: when low output and team failure coexist, explanation becomes hard. Whether it is calling (the invisible contribution) or frags (the visible one) — he delivered neither. So siuhy ends as someone who could not hold on in either metric, not just one.

And there is the "promise-to-decline" arc. He arrived from MOUZ with promise but never found the formula. This is a textbook case — an import whose MOUZ form did not translate into the NA structure. I emphasise "NA structure" because siuhy is Polish, a product of the European system; adaptation friction in NA orgs is a recurring theme. This is not a story of lost skill; it is a story of system fit.

Contrarian: the rating is never the whole truth

Now I stand against my own strongest claim. If you use the 0.87 rating to dismiss siuhy as "bad," you are crossing a limit of the data. An IGL's value cannot be fully measured by rating — mid-round calling, economy management, side-switch adjustments, opponent reads — much of it is invisible on the scoreboard. Judging an IGL by rating alone means throwing away half the match information and ruling on the other half.

This is where correlation and causation blur. siuhy was there when the team lost, therefore siuhy caused the decline — the argument is tempting but wrong. Liquid's IGL problem long predates siuhy. cadiaN and Twistzz — two full "eras" passed before siuhy. That is, a multi-season leadership rotation problem was born long before siuhy arrived. Blaming the last patient for a pre-existing disease is a logical trap.

Still, one real obstacle exists, and I will state it directly. My accounting suggests the team probably did not release siuhy alone — he did not suffer from a lack of talent; chemistry broke. But the biggest blind spot is the performance staff. The source mentions no head coach, analyst, or sports-psych support. After such sustained underperformance, that question remains open — how capable was the coaching and support structure, really?

One more caution. Handing calling to JT is itself a risk. Installing a new IGL carries a "honeymoon-to-adjustment" curve; early results may look good, then the real cracks surface slowly. So a sudden improvement under JT does not mean the problem is solved — it may be masking it.

There is also a data-integrity flag, which I will not hide. In one place the source dates the benching to "July 2026," yet siuhy joined in April 2026 and the same source says a "sixteen-month tenure." The dates need checking — this should be verified before being treated as settled fact. My reading rule: if the sample size or the dates do not line up, nothing is certain.

Takeaway: the next-round signal

Liquid's biggest question going forward is not siuhy — it is who fills the vacancy, and when. The source confirms the replacement is "unconfirmed"; the team is entering an unspecified window with an open spot. That is a live competitive handicap. If Liquid cannot stabilise the caller role long-term, this is not a reset — it is the fifth lap of the same cycle.

For siuhy, meanwhile, this exit is a new door. No transfer fee, MOUZ pedigree — an attractive option for budget-conscious organisations, on one condition: they accept the form risk. But his 0.87 rating is a damaged résumé; his next opportunity may be at a lower tier, or in a non-IGL role.

A bigger picture also needs watching. In this same window, 100 Thieves is rebuilding, s1mple is moving to BC.Game, and Liquid even has a Dota 2 mid vacancy. This cluster suggests a broad multi-title roster-construction wave — an active pre-season shuffle. In this environment, the free-agent market favours sellers and agents.

Model lag and "what would change my mind"

I will not pretend to certainty. What this analysis cannot capture: conference calls, practice-scrim data, dressing-room chemistry, and the internal work of the performance staff. Without these, delivering a final verdict on siuhy is nothing but an admitted model lag.

Three things would change my mind. One, if Liquid reaches the playoffs in two consecutive Majors under JT — then the problem was caller-specific, not structural. Two, if siuhy returns at a new team with a rating above 1.00 — then the "overhyped" narrative fails. Three, if Liquid signs a confirmed top-tier IGL and results still do not change — then the blame lies with the system, not with four callers.

Method and data sources

This piece rests on three information layers: player-level numbers (185 maps, 0.87 rating), tournament-level record (three Majors, zero playoffs, 5-11 maps), and transfer-level facts (April 2026 loan, July 2026 benching, free-agent exit). Source: Dust2.us report, August 2026. Every claim is tied to a specific sample and time window; there is no universal "always" or "never."

Since 2026 I have logged every Major map by map. The nights I spent watching siuhy's Liquid chapter on screen taught me one thing: when a team repeats the same mistake again and again, it is not a player's fate — it is the system's signature. The lesson of the 2026 Germany memo remains equally relevant: a timestamped forecast first, a retrospective hot take later.

siuhy's exit is merely the end of a chapter. The real question still sits on the table — will Liquid make the same mistake a fifth time, or will it finally fix the system?