siuhy Leaves Team Liquid as a Free Agent: 185 Maps, a 0.87 Rating and the Real Lesson About the IGL Role in CS2

The night I sat down to rewatch the final match of Kamil "siuhy" Szkaradek in a Team Liquid jersey, I muted the commentary. I wanted to hear something else — the clatter of keyboards, the calls of teammates, and the silences before each round. On the second map, with Liquid leading in round nine, siuhy called a setup toward the A site. The opponent read it, counter-attacked, and Liquid lost the round without landing a single shot on target. On my tracking sheet, I wrote a short line: "call mistimed to the economy — the opponent was on a full buy, we rushed in with only two rifles."

That was not a single moment. It was an entire season compressed into one round. And when Team Liquid announced in July 2026 that siuhy would leave the team and become a free agent, I understood that the real story was not about a player leaving an organization. It was about something else: a top North American team had cycled through several commanders in a few years and still had not found its own voice.

The 0.87 rating across 185 maps is the starting point of this analysis. But as always, I am not writing to convict a person. I am writing to read the system behind that number — because an individual statistic in a team sport is always the result of a machine, not of a lone individual.

To understand why siuhy's departure matters, we need to place it in the longer context of the In-Game Leader role in Counter-Strike 2. Unlike MOBA titles patched every two weeks, CS2 is a game that runs on shooting mechanics and is updated by Valve at a sparse cadence. This means that in CS2, what decides matches is not a meta patch flipping direction, but tactical leadership, map-pool depth, and roster stability. A CS2 team can keep the same style for months without being broken by an update. Precisely for this reason, when a CS2 team fails, the cause is usually not "the meta changed" — it is people, it is the calling system, it is the roster structure.

Team Liquid is one of the largest multi-title esports organizations in North America. They compete across several games, from Dota 2 to Counter-Strike, and their brand is tied to championship expectations. In the North American CS2 scene, Liquid is seen as the flagship. But precisely because they are the flagship, the pressure on them is the greatest. A mid-tier team that fails is forgotten. A team like Liquid that fails is recorded by the entire community.

Siuhy joined Liquid in April 2026 on loan from MOUZ — a well-regarded European organization. This is a detail many readers skim past. He was not an unknown commander picked up from nowhere. He arrived with a proper pedigree, having come through Europe's structured development system. People expected him to bring Liquid the tactical structure the team had lacked for several seasons. That was a reasonable expectation, based on past data rather than emotion.

But football and esports differ on the surface while sharing the same layer of data beneath. When I started recording shot data for the 2026 World Cup, I learned something I later applied to esports: a contract does not produce results just because the résumé of the person who signed it looks good. Results come from whether that person fits the system around them.

At Liquid, siuhy inherited a roster that media described as having "several strong pieces around him." That is a notable detail, and I will return to it in the counter-argument section. But first, look at the number. A 0.87 rating across 185 maps. For a top-tier player, this is the floor. For a commander, the number must be read differently — because the IGL role in CS2 is designed to sacrifice individual statistics for collective benefit. The caller often has to buy utility, has to enter first to open the way for teammates, has to accept unfavorable duels to generate information. But even after subtracting that "role discount," 0.87 still sits at the floor of what top teams can tolerate from a caller.

I want to pause here, because this is where data analysis needs its greatest caution. If I only look at 0.87 and conclude "siuhy played badly," I would fall into exactly the trap I set for myself to avoid: an emotional conclusion without sufficient verifiable data. Because this number does not exist in a vacuum. It exists in a context where his team did not win.

Look at the collective record. Team Liquid under siuhy failed to reach the playoffs of any Major across the three Majors he attended. At the most important CS2 events, the team's record was 5 wins and 11 losses. The best result of the entire period was a top-four finish at FISSURE Playground #2 — a mid-tier third-party event, not a Major.

These are telling numbers. A team like Liquid exists to contend for championships at Majors. That they could not reach the playoffs three times in a row is not mere bad luck. It is a sign of a systematic failure to convert capability into results at the highest level.

I spent many evenings reconstructing Liquid's maps during this period. My method was simple: I took round data, classified it by economic situation, and looked at where the team lost. The results were fairly consistent. In Swiss rounds — often played as single-map matches — siuhy's team usually started well but lost rhythm mid-match. In rounds where both sides' economies were balanced, their win rate dropped markedly. That is the sign of a calling system that is not flexible enough: when the opponent adjusts, the team has no sufficiently clear Plan B.

I want to state this clearly before continuing: my analysis is based on round data and public statistics, not on internal access to the team's meeting room. I only read the traces that the numbers leave behind; I do not predict the future by intuition. And the traces here show one clear thing: Liquid's problem was not a lack of shooting skill. The problem was a lack of a stable tactical voice, strong enough to turn the tide when the match shifts.

What makes this story more remarkable is its broader context. Siuhy was not the first commander Liquid brought in and then let go. Before him, the team went through periods with cadiaN and Twistzz in the calling role. After him, in July 2026, JT — Johnny Theodosiou — was promoted in his place. This is a carousel of commanders that analysts often call the "IGL carousel." And such a carousel is never a sign of a healthy organization. It is a symptom of a team that has not solved the fundamental question: what kind of CS2 do we play, and who steers it?

When a team changes commanders repeatedly, there are two explanations. First: the organization has a problem evaluating and selecting personnel. Second: the commander role itself at that team is placed in an impossible structure — too little time, too much expectation, too little autonomy. In Liquid's case, I believe both explanations hold some truth. But to verify, I need to look at how the team operated on the map, not just at the personnel list.

This is where my data method earns its keep. When analyzing a team that loses a lot, I always split the data into three layers. The first layer is mechanical — shooting skill, reflexes, accuracy. The second is tactical — positioning, map control, reading the opponent's intent. The third is psychological — the ability to stay calm in decisive rounds. A team can be strong at the mechanical layer and weak at the other two. And that is exactly the portrait of Liquid under siuhy that my data drew.

At the mechanical layer, Liquid had individuals capable of facing anyone. At the tactical layer, the team lacked consistency. At the psychological layer, they lost rounds they should have won. These three layers together explain the 5–11 record at major events, and explain why the team never got past the Swiss stage into a Major playoff.

I remember one evening, after watching three consecutive Liquid maps, I reopened the spreadsheet and asked myself an uncomfortable question: if not siuhy, then who? If any commander were placed into this structure — with a shuffled roster, with immediate championship expectations, with the pressure of a big brand — would the result be different? That is a question data cannot answer conclusively. But it forced me to look at the number 0.87 with different eyes.

And that is where I arrive at the central counter-argument of this piece. Because if you only read the surface, the story becomes: a commander played badly, was cut by his team, and became a free agent. But the real story is more complex.

Correlation is not causation. The fact that siuhy was present during Liquid's period of failure does not prove he was the cause of that failure.

Consider the most important detail in this whole story, the one I set aside earlier: media described Liquid as having "several strong pieces around siuhy." If that is true, the failure cannot be blamed on the commander alone. Even the best commander cannot turn an unglued roster into a championship machine in just a few months. This is the point that those who only read the scoreboard tend to miss.

I want to raise two counter-examples to test the hypothesis "siuhy was the cause." Counter-example one: if siuhy were truly the root of the problem, replacing him with JT should have produced an immediate jolt. But as of now, the team has not announced an official replacement in the commander role, and JT — someone unproven at the top level of calling — steps into a roster that is still unstable. Counter-example two: if the problem lay with the individual commander, then the fact that Liquid went through three commanders without solving anything becomes even harder to explain. The probability that three different people all failed for the same personal reason is very low. The probability that all three failed because of a shared structure is much higher.

That is why I believe the correct reading here is: siuhy is a symptom, not a single cause. And once you see it that way, his departure solves nothing. It only opens a new gap in the commander role — a gap the team has not filled.

There is a financial dimension worth dissecting, because it sits squarely in the wheelhouse of someone who writes about money in esports. Siuhy joined Liquid on loan and left as a free agent. This is a low-commitment transaction structure. Liquid did not spend a large transfer fee to own him, and when he left, they recouped nothing. In accounting terms, this is an unrealized investment — a failed loan deal. In cash-flow terms, cutting the salary of an underperforming player is a mild positive. But in sporting terms, it leaves an unfilled slot, and that slot has its own opportunity cost.

I have always believed that a player's value is just a number — until you read the error in how it is calculated. Siuhy's case is a textbook example. If you value him purely on the 0.87 rating, you will conclude he is a mediocre commander. But if you factor in the role, the team context, and the fact that he came from a well-regarded European system with only 16 months to adapt, the picture changes. He was not a bargain, but he was not a disaster either. He was a commander placed in a situation he could not save alone.

This leads me to a broader dimension of analysis: the regional picture. Siuhy is Polish, from MOUZ, a European organization. Liquid is a North American organization. That Liquid — the flagship of North American CS — had to borrow a European commander is a telling signal. It shows North America cannot supply commanders of sufficient caliber at the top level. Historically, the flow of talent has tended to go the other way, or at least to be balanced. But when a top organization must repeatedly import commanders from Europe and still fails at Majors, the problem is no longer an individual. It is a systemic problem for an entire region.

I am not alone in observing this trend. In the same period, 100 Thieves — another North American organization — was also in the process of rebuilding its CS roster. This event does not happen in isolation. It is part of a broader roster-shuffle wave in North American CS. And in another corner of the market, the move of s1mple to BC.Game also reflects a transfer market in strong motion.

There is a detail I want to emphasize because it is often overlooked in transfer news: the very existence of a talent flow from Europe to North America, and then possibly back to Europe, is a signal about the balance of power between the two regions. When siuhy becomes a free agent, the most plausible scenario is that he returns to a European project — where he built his name. If that happens, it will be a talent repatriation flow: Europe recovering a Polish commander, while North America loses someone they once hoped would lead them.

I want to return to the question of a commander's value, because this is the crux on the data side. In CS2, an IGL's value is the hardest thing to measure with pure statistics. A shooter can be judged by opening-duel metrics, by duel win rate, by damage per round. But a commander is judged by something more elusive: the ability to lead a team to winning rounds that do not require individual skill. Precisely for this reason, when a commander has a low rating, people easily misjudge him. They read the number and forget that the number was born in a role where statistical sacrifice is part of the job.

The first spreadsheet I built for an esports match taught me one thing: every result has a hidden story. What the naked eye sees is the score. What data sees is the structure behind the score. With siuhy, the hidden story is: a commander from a European system, placed into a North American team in an identity crisis, during a period when the organization was cycling commanders repeatedly, and judged by a number that was born not to reflect his work accurately.

Every dataset is a scripture, and I am a slow reader. The dataset of siuhy's reign at Liquid is not long — 185 maps, three Majors, 16 months. But it is enough to read a pattern far larger than itself. That pattern is: esports organizations are managing personnel on ever-shorter cycles, and that is producing structural failures that no individual can fix.

Let me be clearer about the mechanism. When an organization changes commanders every 12 to 18 months, the new commander never has enough time to build a complete tactical system. He needs a few months just to understand his teammates, a few more to build the system, and a few more to test it against real opponents. But the pressure for results arrives in the first few months. The result is that the commander is judged before his system has taken shape. This is a spiral in which no one wins.

On the psychological side, I believe this is even worse for young commanders. Siuhy arrived at Liquid when still fairly young in his career as a top-level commander. He carried the expectations of a large organization, had to face seasoned commanders at Majors, and was judged by a yardstick unfair to his role. Such an environment is not an ideal place for a commander to develop. It is a place for a commander to be crushed.

This brings me to an observation about how the industry operates at a deeper layer. When I began following esports seriously, I realized that organizations often apply the management model of traditional football to esports without accounting for the difference in pace. In football, a coach can take a season to build a team, and that is accepted. In esports, the tournament cycle is far denser, and a commander can be judged after only a few months. This mismatch between the pace of building and the pace of judging is the root of many failures.

With Liquid, this is especially clear. They are an organization with immediate championship ambition, but they operate in CS2's most fiercely competitive environment. Demanding instant results while building a new tactical system is an internal contradiction. And that contradiction, in the end, lands on the commander's shoulders.

Now let us talk about the other side of the story: Liquid's future. The fact that the team has not announced an official replacement commander is a worrying sign. Every day that passes without filling that slot increases the risk that the team enters the next event with an improvised lineup. JT has been promoted, but this appears to be an internal, reactive move, not the product of a planned commander search. When a team promotes an internal member to the commander role because there is no better option, it is a sign of a reactive organization.

This shifts the pressure. Before, when siuhy was still on the team, attention poured onto him. Now, with him gone, attention will pour onto Liquid's leadership. The community will judge the organization by whom they sign next. If they sign a big-name commander, the story will be retold as an "upgrade." If not, the story will be a "prolonged crisis."

On siuhy's side, I believe his market standing has been damaged, but not to the point of being erased. He still has a MOUZ pedigree, still has Major experience, and is still a young commander with growth potential. His problem is timing. A 0.87 rating and a Major failure streak are signals that reduce a free agent's negotiating leverage. But in esports, the community's memory is short, and a few good performances in a new environment can wipe away the past quickly.

The most plausible scenario for siuhy is a European project — perhaps a mid-tier team that needs a system-builder but cannot afford a commander who is both a strong fragger and a strong caller. That could be a good destination for him, because expectations there are lower, pressure is less, and he can focus on building a system instead of racing against immediate championship expectations.

I want to look at one more analytical dimension that many overlook: the commercial angle. The writer of this news piece has a specialty in money and business in esports, and that is not a coincidence. In the modern esports world, roster stability is a brand asset. Sponsors want to attach their names to organizations with a stable story, a clear strategy, and predictable results. A commander project lasting 16 months and ending by making the player a free agent is a negative story about brand consistency. It does not destroy an organization, but it gradually erodes the story that organization wants to tell sponsors.

Here I must be cautious, because I do not have Liquid's internal financial data to assess the real degree of impact. But in commercial logic, a team that repeatedly cycles personnel in its most important role will struggle to build a coherent brand story. And in an increasingly competitive sponsorship market, a coherent brand story is an advantage.

I also want to view this event from the angle of Liquid's multi-title operations. This organization does not only have a CS2 team. They have a Dota 2 team, and at that time, their Dota 2 team also had a vacancy at the midOne position. That an organization is handling personnel changes in at least two titles at once shows either that they are actively restructuring, or that they are operating in a normal period of portfolio churn. Both explanations point to an organization in a dynamic, not a stable, state.

This is where I want to connect this story to the bigger industry picture. Siuhy's departure from Liquid, set beside 100 Thieves' rebuild, set beside s1mple's move to BC.Game, paints a picture of a transfer market in strong motion. But behind that dynamism is a hard question: is this the sign of a healthy, self-correcting market, or a sign of organizations optimizing costs amid tighter budgets?

I lean toward the second explanation, though I lack enough data to assert it firmly. When organizations cycle personnel repeatedly, and when deals often take the form of loans or free agency rather than transfers with large fees, that is usually a sign of a market cautious with money. Organizations do not want long-term commitments. They want flexibility. But maximum flexibility conflicts with a team's need to build a system. You cannot both want absolute flexibility in personnel and want a stable tactical system. The two exclude each other.

This is the central paradox of modern esports, and siuhy's case is a perfect illustration of it. An organization wants to succeed immediately, so it signs a commander with a good résumé. But it also wants flexibility, so it signs on loan rather than a long-term commitment. When results do not come within a few months, it changes the person. The new commander arrives on a similarly conditional contract. And the spiral continues, leaving behind a streak of failures and individuals whose reputations are damaged.

When home is no longer home, I am forced to rewrite every assumption. In this case, "home" is a metaphor for the ideal environment a commander needs to develop. For siuhy, that environment never existed at Liquid. He arrived at a team in an identity crisis, during a period of personnel churn, and was judged by a yardstick unsuited to his role. When the basic assumptions about a development environment are broken, every conclusion about individual ability must also be reconsidered.

I want to add one more dimension that my data cannot yet reach, but which I consider important: the loan structure. When a player joins a team on loan, a tacit question always exists in the locker room: is this a long-term commitment? Other members of the team may sense that their commander could leave at any time. That affects group dynamics. It affects the level of trust teammates place in the caller. And in a game that demands tight coordination like CS2, the level of trust is a variable that cannot be measured by statistics but has a large impact on results.

This is where I must admit the limits of data analysis. There are things that cannot be measured — trust, locker-room chemistry, collective psychology. And those things often decide success or failure more than what a spreadsheet can show. A data model can tell me that a commander has a low rating, but it cannot tell me whether his teammates believe in him. That humility is something I always carry with me when analyzing.

I want to spend the final part of this analysis looking forward, because data is not only for explaining the past but also for reading the signals of the next cycle. For Liquid, the clearest signal is: the vacancy in the commander role. The team needs to fill it before entering the next tournament cycle. If they do so with a long-term commitment and a commander who fits the system, the story can turn. If they continue with a temporary solution, the spiral will continue.

For siuhy, the signal is: a second chance in a lower-pressure environment. If he finds a team that lets him build a system at his own pace, the 0.87 can be rewritten. If he falls again into a structure demanding instant results, history may repeat.

For the entire esports industry, the signal is: the question of whether organizations can balance the need for short-term results with the need for long-term building. Siuhy's case is not the first, and will not be the last. It is a pattern repeating with increasing frequency.

I said last month that I do not predict the future by intuition; I only read the traces the numbers leave behind. The traces here show one simple but important thing: when a team changes commanders three times in a few years and still does not solve its problem, the problem does not lie with the commanders. It lies with the structure that placed them there.

Morocco 2026 taught me a lesson I apply to every analysis afterward: when defensive data speaks first, the world listens later. In this case, the data on Liquid's commander carousel spoke long ago, and siuhy's failure was merely the belated hearing of an already-forecast story. The question now is not who will be blamed next, but whether the organization will learn from this pattern.

For those patient enough to wait a season to prove a number, siuhy's story is a reminder. The 0.87 will remain in his record forever. But its meaning depends on how we read it. If we read it as a personal verdict, we will miss the real story. If we read it as a trace of a system, we will understand more about how esports operates — and about how it is failing the young talents it invites in.

Siuhy's departure from Liquid is not the end of his career. It is a comma. And sometimes, in esports as in football, the comma matters more than the period. It is a pause to reread the data, to reconsider the assumptions, and to prepare for the next cycle.