siuhy Becomes Free Agent After Team Liquid Exit: Inside a 16-Month IGL Project Without a Single Major Playoff Run

In July 2026, Team Liquid handed the Counter-Strike 2 captaincy to Johnny "JT" Theodosiou and moved Kamil "siuhy" Szkaradek to the bench. Shortly afterwards, the Los Angeles-based organisation confirmed that the Polish in-game leader was leaving the team as a free agent. No transfer fee. No third party buying out the contract. No announcement of a replacement.

The record left behind after sixteen months: 5 wins and 11 losses at the most important Counter-Strike 2 events. Three Majors, not a single playoff appearance. The best result of the entire period was a top-four finish at FISSURE Playground #2, a third-party event outside Valve's Major system.

That is how a sixteen-month project ends. Not with a crushing defeat in front of the cameras, but with a short administrative statement published while most fans were discussing a different transfer window.

I have followed professional Counter-Strike since 2026, when I was still on the other side of the stage as a player and tournament organiser. Twenty-one years later, I keep the same habit: whenever a major team parts ways with an in-game leader, I do not read the farewell post. I read the statistics sheet, the match schedule, and the contract structure. Farewell posts are always written to protect both sides. Data has no such need.

And the data in this case says something very clearly, something nobody in Team Liquid's leadership wants to say out loud: this team's problem was never one individual.

Context: an in-game leader from MOUZ

In April 2026, Team Liquid announced the loan signing of Kamil "siuhy" Szkaradek from MOUZ. It was a deal rated highly at the time, and the reason was easy to understand.

Siuhy was not an unknown quantity. He came from MOUZ, one of the organisations with the best talent development and tactical operating systems in Europe over the past half-decade. There, he was forged in an environment where the in-game leader role is valued as highly as the star rifler role, where every mid-round decision is turned into data after the map ends. An in-game leader raised at MOUZ carries a very specific skill package: the ability to read match tempo, the ability to build round structure, and the ability to turn a loose collective into a disciplined unit.

For Team Liquid, this was seen as the missing piece. The North American team possessed a group of players rated by experts as high quality. Dust2.us, in the original report on the matter, described Liquid as having "several strong pieces around siuhy". That is a diplomatic phrasing, but it is also a weighty assessment: if the pieces around him were strong enough, then the failure must be attributed to structure, not to personnel.

But before going into the structural question, the wider context needs to be set. Team Liquid is not a young organisation. It is one of the oldest and best-resourced brands in Western esports, operating across multiple titles, present at the biggest events of several different games. An organisation like that does not lack resources to build a roster. What it has lacked, consistently over many years in Counter-Strike, is stability in the in-game leader position.

And this is the crux I want to spend most of this article analysing.

The captaincy carousel: cadiaN, Twistzz, siuhy, JT

Before siuhy arrived, Team Liquid had already gone through two in-game leader eras with Casper "cadiaN" Møller and Russel "Twistzz" Van Dulken. After siuhy was benched in July 2026, the captaincy passed to Johnny "JT" Theodosiou, an internal solution.

Four captaincy names in one competitive cycle. Four different command philosophies. Four different tactical systems. Four different ways of allocating round resources.

In Counter-Strike, the in-game leader role is not merely the person who calls the strategy before a round starts. It is the person who decides tempo, who decides when the team plays fast and when it slows down, who decides how the economy is allocated across rounds, and who is responsible for adjusting the plan in the ten seconds between rounds. A team that changes in-game leaders four times in a few seasons is like an orchestra changing conductors four times mid-performance. Each new conductor brings a new interpretation, a new tempo, a new way of phrasing. The musicians may play well, but the overall sound will never reach maturity.

I have watched this pattern many times over two decades of covering competitions. When an organisation repeatedly changes in-game leaders without changing the coaching structure, the analytics department, or the recruitment process, that is a sign of a problem at the sports-management level, not in the individual wearing the armband. People change in-game leaders because it is the easiest change to make, the easiest to communicate, and the easiest to sell to sponsors. Changing the coaching staff is harder. Changing the roster-building philosophy is much harder.

JT being promoted internally, following a bench-then-promote sequence, indicates a reactive solution rather than a planned one. An organisation with a proper leadership transition plan would announce the roadmap in advance, would have a handover period, would issue a statement about both parties' roles. Here, the only information the public received was a short announcement, and an unfilled roster spot.

Data does not need a loudspeaker, but it shakes an empire. Four in-game leaders in one cycle is a number that needs no further commentary.

The data picture: a 0.87 rating across 185 maps

The single most important data point in this entire affair is siuhy's individual rating at Team Liquid: 0.87 across a total of 185 maps played.

This number needs to be placed in proper context to understand its severity.

In professional Counter-Strike, the average individual rating of a player competing at the highest level typically hovers around 1.00. A 1.05 to 1.10 is considered good. Above 1.15 is considered excellent. Below 0.95 begins to be a warning sign. Below 0.90 is the zone that top teams usually only accept for roles with a special sacrificial character, such as dedicated support players or entry players in extremely demanding systems.

A 0.87 sustained across 185 maps is not a period of poor form. It is a long-term characteristic.

But fairness is required here, and that fairness is precisely where professional analysis becomes interesting.

The in-game leader role carries a structural rating discount. An in-game leader must devote focus to reading the match, calling strategy, managing the economy, and coordinating teammates. Time and attention are finite. An in-game leader typically plays in more supportive positions, carries cheaper weapons in save rounds, and is often the first one in to open the way for teammates. All of these factors drag individual ratings down.

So judging an in-game leader purely by individual rating is a one-sided method. But equally, ignoring individual rating is a one-sided method in the opposite direction. The trend in modern Counter-Strike over many years has been to shift the in-game leader role toward a "commanding fragger" archetype — someone who calls strategy while also generating numerical advantage through individual skill. Top teams increasingly refuse to accept an in-game leader who only calls strategy and contributes nothing in terms of eliminating opponents.

A 0.87 sits at the floor of the zone top teams can tolerate. It is not outside the acceptable zone, but it is at the edge. And when an in-game leader at the lower edge of individual rating simultaneously fails to deliver team results, the sum of those two factors produces a conclusion that is very hard to argue with.

I want to be clear about this: 0.87 does not prove siuhy was the sole cause of the failure. But it does prove he was not the solution.

The data picture: 5-11 and three Majors without playoffs

If individual rating is an indirect indicator, then team results are a direct one.

At the most important Counter-Strike 2 events, siuhy's Team Liquid recorded 5 wins and 11 losses. Across three Majors — the tournament system sanctioned by Valve and regarded as the pinnacle of the discipline — the team never once reached the playoff stage.

Three Majors. Not one playoff appearance.

This is the most important data point of the whole story, and I want to spend time analysing why it matters more than the individual rating.

In elite sport, there is a big difference between losing because you are not good enough and losing because you cannot convert ability into results. A weak team loses in the group stage and nobody is surprised. A strong team losing in the group stage is a phenomenon that needs explaining. But a strong team repeatedly losing in the group stage across several consecutive tournaments, with the same roster, under the same coaching staff, is no longer a phenomenon needing explanation. It is a pattern.

Sixteen months is long enough for a professional team to build a system, test it, adjust it, and find a formula. Three Majors are three independent opportunities to prove it. None were taken.

And this is the point I believe analysts have overlooked when looking at this affair.

Most social media commentary focused on the 0.87 rating and concluded that siuhy played badly. That conclusion is correct but incomplete. The bigger problem is this: over sixteen months, this team never once demonstrated the ability to win a long series at the highest level. Winning a single map is a matter of skill. Winning a best-of-three against a top opponent is a matter of system. And the system is the shared responsibility of the coaching staff and the in-game leader.

Three Majors without playoffs is an indictment aimed at the whole structure, not just at one individual.

Major format and the statistical trap of the Swiss stage

A technical note is important here, because sports analysis without an understanding of format very easily reaches wrong conclusions.

Counter-Strike Majors use a Swiss group stage combined with single-elimination playoffs. In the Swiss stage, most matches are played in a single-map format. Only the matches that decide advancement or elimination switch to a best-of-three. Playoffs are best-of-three, and the final is best-of-five.

What does this mean for a 5-11 record?

The single-map format increases variance. In a single map, one lucky play, one wrong decision in a deciding round, or one bad start can determine the entire match. Strong teams often get eliminated in the Swiss stage for this reason. So part of Team Liquid's 5-11 record can be explained by the format's characteristics.

But here is the crux: three Majors without playoffs cannot be explained by single-map variance.

If the problem were only variance, the probability of a sufficiently strong team failing at all three consecutive Majors would be very low. Three times in a row is a pattern, not a random sequence of events. And this pattern points to one thing: this team cannot peak under the highest pressure, in the longest series, against the best-prepared opponents.

The ability to peak under high pressure is a collective skill, and it is built by the in-game leader together with the coaching staff. When that skill is absent across three consecutive tournaments, the question is no longer "who played badly" but "which system is failing".

I see the champion's cracks before the rest of the world hears about them. In this case, the crack is not in a player. It is in the way this organisation builds and operates a Counter-Strike team.

The FISSURE ceiling: the best result and what it really means

Team Liquid's best result throughout the siuhy period was a top-four finish at FISSURE Playground #2.

This is an easily overlooked detail, but it is highly symbolic. FISSURE Playground is a third-party event in the mid-tier group of the Counter-Strike competition system. It is where top teams usually experiment with lineups, accumulate ranking points, and maintain match rhythm. It is not where top teams measure the success of a project.

When an organisation with Major-winning ambitions records its best result in sixteen months at a mid-tier event, the gap between ambition and reality has been quantified.

And here is what I want to emphasise: both the floor and the ceiling of this team were below the brand tier of the organisation. A low floor means unexpected losses to weaker opponents. A low ceiling means an inability to overcome equal or stronger opponents at the decisive stage. A team can accept a low floor if the ceiling is high. A team can accept a low ceiling if the floor is stable. Team Liquid in this period had both problems at once.

In professional sport, that is the worst state to be in. Because it gives leadership no foothold from which to decide whether to keep or replace.

They chose to replace. And that choice, in data terms, was reasonable.

The economics of a loan deal that ended in free agency

Now let us turn to the aspect few people discuss but which matters most in the long run: the economic structure of the deal.

Siuhy joined Team Liquid in April 2026 on loan from MOUZ. He left the team in mid-2026 as a free agent, with no transfer fee attached.

Let us analyse this sequence.

A loan deal means MOUZ retained ownership of the player's contract while he played for Team Liquid. The borrowing team pays a loan fee, pays wages, and usually has a pre-agreed buyout clause. This is a low-risk structure for the borrower, but also a low-commitment one.

When a loaned player later becomes a free agent, it means the borrowing team did not exercise the buyout clause. In other words, after sixteen months of direct observation, Team Liquid concluded that they did not want to own this player's contract.

In purely financial terms, this is a rational decision. The team removes a significant wage line from the books without paying a termination penalty. Cash flow improves.

But in asset-building terms, this is a deal that generated no return. Team Liquid invested loan fees, wages, coaching time, integration time, and competitive opportunities — all of those resources failed to convert into a saleable asset. No transfer fee received. No player retained. No value accumulated.

This is the pattern I call "a failed rental". You rent a solution, the solution does not work, you return it, and you are left with nothing but a hole in the roster.

And that hole carries its own opportunity cost. Every month the in-game leader position stays unfilled is a month the team cannot build a system. In a discipline where player synergy requires hundreds of hours of competition to form, time is an irreplaceable resource.

North America importing European in-game leaders: a structural signal

There is a detail in this story that I consider more important than the event itself.

Team Liquid is North America's flagship organisation in Counter-Strike. And it went to import a Polish in-game leader from a European organisation to solve its problem.

This reverses the historical pattern. For many years, the flow of Counter-Strike talent ran from Europe to North America, but North American teams always retained the ability to produce world-class in-game leaders domestically. A North American flagship organisation having to borrow an in-game leader from Europe — and still failing to deliver results — is a signal of a structural gap.

Where does that gap lie?

It lies in the youth development system. It lies in the number of grassroots tournaments. It lies in the number of coaches with high-level tactical analysis skills. It lies in roster-building culture: European organisations tend to build rosters from the bottom up, while North American organisations tend to buy finished rosters from the top down.

The buying approach has the advantage of speed. But its disadvantage is that it does not accumulate. A team that buys five good players will have a good roster for one season. An academy that develops five good players will have a generation across five seasons.

And in this specific case, the buying approach failed even in the short term.

100 Thieves, s1mple and the North American restructuring wave

Siuhy's affair did not happen in a vacuum. It is part of a broader restructuring wave in the North American region.

Over the same period, 100 Thieves carried out a rebuild of their Counter-Strike roster. In parallel, the transfer market saw the movement of major names, with Oleksandr "s1mple" Kostyliev moving to play for BC.Game — a move that shifted the talent allocation map at the highest level.

When several major organisations restructure their rosters at the same time, it is usually a sign of a market cycle. It could be preparation for a new tournament phase. It could be a reaction to changes in the ranking points system. It could also be a sign that organisations are tightening budgets and seeking efficiency rather than prestige.

As someone who follows the flow of money in esports, I believe the third possibility deserves the most serious consideration.

During the growth phase, esports organisations competed by spending on the biggest names. During the maturity phase, they compete by optimising cost structure. Team Liquid moving from a loan deal with a high salary to a lower-cost internal solution fits the second pattern.

That does not mean the decision was right or wrong on competitive grounds. It only means the motive may not be purely competitive.

Liquid across titles: a signal about capital allocation

An easily missed detail: during the same period, Team Liquid was also handling a personnel gap in Dota 2, with the position of Yeik "MidOne" Nai Zheng in the roster.

Two titles. Two personnel gaps. Two restructuring waves at the same time.

For a multi-title organisation, this is a signal about capital allocation. An organisation can only handle several simultaneous restructuring waves in two scenarios: either it is undergoing a comprehensive restructuring, or it operates with frequent roster rotation as part of its strategy.

Both scenarios are meaningful for siuhy's story.

If it is comprehensive restructuring, then releasing an underperforming in-game leader is a sensible first step. If it is frequent rotation, then changing in-game leaders four times in a few seasons is the expression of an operating philosophy, not of an individual mistake.

Either way, the conclusion is the same: siuhy is a variable in an equation much larger than himself.

The counter-view: "strong pieces around siuhy"

At this point I need to present the counter-view to my own analysis, because an analysis without self-critique is an analysis not worth trusting.

The data point most favourable to siuhy is Dust2.us's assessment that Team Liquid had "several strong pieces around siuhy".

If we read this assessment in the player's favour, it means: the roster had quality, but results did not come. When a roster with quality fails to deliver, responsibility is usually shared between the in-game leader, the coaching staff, and the leadership. Blaming the armband-wearer entirely is an understandable media reflex but not professionally accurate.

Moreover, it is worth remembering that siuhy came from MOUZ — an environment with a system. An in-game leader raised in a good system can struggle when moving to an environment lacking a system. This is a common phenomenon in professional sport: coaches who succeed at well-structured clubs often fail at unstructured clubs, and vice versa.

If this hypothesis is correct, the problem is not that siuhy was not good enough. The problem is that Team Liquid could not provide the environment for his ability to flourish.

This is a reasonable hypothesis. But it has one weakness: it does not explain the 0.87 rating across 185 maps. Environment can affect calling ability, but environment does not directly reduce a professional player's ability to eliminate opponents to below 0.90 across more than one hundred and eighty maps.

I do not oppose tradition; I am only handing tradition a new piece of evidence. And the new evidence here is this: even accounting for every mitigating factor, 0.87 remains a number that cannot be fully excused.

The counter-view: the structural rating discount of the in-game leader role

Above I mentioned the structural rating discount of the in-game leader role. Now I want to push that argument one step further, because it could change the conclusion.

In some tactical systems, the in-game leader is assigned deliberate sacrificial duties. That person is the first in during opening rounds, carries smoke and flash grenades to create space for teammates, and accepts dying first so teammates gain a numerical advantage. In such systems, the in-game leader's individual rating can be deliberately low.

If siuhy was assigned that role, then 0.87 reflects a sacrifice, not a decline.

But there are two problems with this hypothesis.

First, confirming the hypothesis requires round-by-round detail: number of entries, number of deaths within the first ten seconds, utility usage, death rate in one-for-one situations. That data is not in the source. Without it, this hypothesis remains only a hypothesis.

Second, even if the hypothesis is correct, it still leads to the same organisational conclusion: if Team Liquid built a system that required the in-game leader to sacrifice to the point where his individual rating fell below 0.90, and that system still failed to produce team results, then the problem lies in the system, not in the person executing it.

Both readings lead to the same place.

The counter-view: Counter-Strike has no saving patch

There is another fundamental difference between Counter-Strike and other team games that I want to clarify, because it rules out some common explanations.

Games like League of Legends or Dota 2 operate on frequent update cycles, with patches that can completely reverse the power hierarchy of champions or heroes. In those games, a failing team can be saved by a suitable patch.

Counter-Strike 2 operates on a different principle. It is a mechanics-driven game, with a much lower Valve update cadence and far less reversal potential. There is no concept of a "power patch" that can turn a weak team into a strong one. Updates typically adjust weapon, map, and mechanic details rather than reshaping the entire tactical ecosystem.

This means: if Team Liquid failed, they cannot blame a patch. And they cannot expect a patch to solve the problem.

Throughout siuhy's sixteen months, no update was recorded as a cause of performance change. That entirely rules out an explanation based on the game environment changing.

The problem must be diagnosed at the strategy and leadership level. There is no other level to blame.

Where I could be wrong

An honest analysis must state its own limits.

First, I do not have round-by-round detail. Every conclusion about siuhy's specific role in Team Liquid's tactical system rests on inference from aggregate statistics, not direct observation.

Second, I do not know the specific structure of the loan deal. If the contract had a buyout clause and Team Liquid declined to exercise it, that is a competitive decision. If the contract expired naturally and MOUZ did not want to extend, the picture is far more complicated.

Third, I do not know who was responsible for coaching and tactical analysis at Team Liquid during this period. An in-game leader works within a specific coaching structure. If that structure was weak, the in-game leader will be underrated relative to his true ability.

Fourth, I have no data on fan reaction, on how much this affair affects both parties' brand image, or on any negotiations that may be happening behind the scenes.

These limits do not change my central conclusion, but they reduce the confidence of the secondary conclusions.

A testable prediction

I will finish with specific predictions, testable over the next twelve months.

Prediction one: siuhy will not sign with a North American organisation. With his MOUZ pedigree and European network, his most logical destination is a tier-one or tier-two project in Europe, where he can work in a system close to what he was trained in.

Prediction two: Team Liquid will not announce a big-name in-game leader before the next season begins. With the current structure, the most feasible option is to continue using JT and add a player in another position.

Prediction three: siuhy's individual rating at his new team will be higher than 0.87. Partly because of the new environment, partly because of regression to the mean. If this prediction is wrong, it means 0.87 reflected a genuine decline, not a specific circumstance.

Prediction four: Team Liquid's problem will not be solved by changing in-game leaders for the fourth time. If this team still fails to reach a Major playoff in the next two cycles, leadership will be forced to reconsider the coaching structure and the roster-building process, not just the personnel.

A stadium can be empty of spectators, but history is never short of chroniclers. In this case, the chronicler will record a very simple fact: a flagship organisation changed in-game leaders for the fourth time, and still has not answered the most basic question — what kind of Counter-Strike does it want to play?

No statistics sheet can answer that question on its behalf. And that is why the story of siuhy, in the end, is not a story about siuhy.