siuhy Leaves Team Liquid as Free Agent: The 0.87 Rating and the Death of a 16-Month Project

On July 15, 2026, a short announcement appeared on Team Liquid's official channel. There was no three-minute farewell video, no emotional "thank you for everything" post. Just one cold sentence: Kamil "siuhy" Szkaradek was benched, and Johnny "JT" Theodosiou would take over as in-game leader. Sixteen months earlier, in April 2026, this same team had posted an announcement that was the complete opposite — welcoming a Polish commander from MOUZ as a loan signing expected to reshape the entire tactical system of one of America's most storied esports organizations.

I was sitting in front of my screen that night, and what made me stop was not the news itself. It was the number that came with the stat sheets the community began sharing: a 0.87 HLTV rating across 185 maps played. A number that is neither loud nor shocking, but it tells the entire story that a polished farewell announcement would try to hide. Data doesn't need a megaphone, but it shakes an empire — and this time, the empire being shaken was a team I had followed for nearly two decades.

This is not the story of a man being fired. This is the story of an organization that tried three times in a row to find its tactical soul, and failed all three times.

CONTEXT: THE CAROUSEL OF COMMANDERS

To understand why siuhy's departure matters more than an ordinary transfer, we need to place it in proper context. Team Liquid, historically, is the most successful North American esports organization in terms of multi-title diversity — they are present in Dota 2, in Counter-Strike, across many different arenas, and their brand is tied to stability. But that very stability has been shaken in the in-game leader role of their Counter-Strike 2 team.

Before siuhy, the role belonged to Casper "cadiaN" Møller — a Danish commander famous for his calling ability and a strongly characterized leadership style. When cadiaN left, the team handed responsibility to Russel "Twistzz" Van Dulken, one of the greatest wing shooters in Counter-Strike history, who tried to carry the extra burden of command on his shoulders. That was a questionable decision from the start — you don't turn a world-class fragger into a caller by simply assigning him more work. Then came siuhy, brought in with the expectation that a professional commander, with European roots, trained in the MOUZ system, would be the missing piece.

Three names. Three philosophies. Three failures. And now a fourth name — JT — is pushed up in a move I read as reactive, not planned. An organization that has made three commander changes in such a short span is not searching for a solution. They are reacting to crisis, again and again, and each reaction pushes them further from the real answer.

I have followed this team since the days they were known by a simpler name, and I learned one thing from football that I apply verbatim to esports: great teams don't collapse from a lack of money. They collapse because no one dares to ask the right question. Guangzhou Evergrande didn't collapse because they ran out of money, but because no one dared to ask where they went wrong. Team Liquid is walking a similar path — not financially, but tactically. They have money, they have brand, they have good players. What they lack is honesty with themselves about where their system is broken.

And the regional context makes this story more serious. North America, as a Counter-Strike region, is in a prolonged structural decline. While Europe produces commanders from its own youth development systems — people raised in academies, trained from a very young age — North America increasingly depends on importing talent from outside. siuhy's arrival, a Pole from MOUZ, at Liquid is precisely an expression of that trend. And when even such a top-tier import signing fails to take the team to Major playoffs, the problem is no longer individual.

The context also has a second, less noticed layer: 100 Thieves, another North American organization, was also restructuring their Counter-Strike team in the same period. When two leading organizations in the same region simultaneously shuffle their rosters, it is not a coincidence. It is a wave — a region-wide restructuring occurring in a compressed time window. And in that wave, siuhy is just a grain of sand swept away, but the way that grain was swept reveals the direction of the current.

CORE ANALYSIS: READING THE 0.87 ACROSS 185 MAPS

Let's start from the most important number, and let's start slowly, because this number is misunderstood many times.

A 0.87 rating across 185 maps. In the HLTV rating system, 1.00 is considered average. A professional player at the tier-1 level typically hovers around 1.05 to 1.15 if a shooter, and can be somewhat lower if a commander — because the commander role carries a "stat discount": they must spend time and focus on calling, on reading the game, on managing team economy, rather than focusing solely on eliminating opponents. That is why an in-game leader rarely has a rating equal to the shooters on the team, and that is entirely normal.

But there is a threshold. And that threshold lies somewhere around 0.90. When a commander drops below that over a large sample — and 185 maps is a large sample, not dismissible as luck — the question is no longer "is he playing badly". The question becomes "is the system placing him in a position to fail".

The most important thing to understand about modern Counter-Strike 2 is that the in-game leader role has been pushed toward "fragging-capable leadership" — someone who can both call and contribute damage. In the early era of professional Counter-Strike, a commander could just call and let teammates do the rest. Today, that is nearly impossible to sustain at the highest level. CS2's tactical economy — with its money system, weapon management, and round-by-round game reading — demands the commander participate in firefights to a certain degree. If he just stands back and calls, the team plays as if down a man.

At 0.87, siuhy sits at the lower edge of the threshold that tier-1 teams can accept from a caller. This number does not say he is a bad commander tactically. It says that, however good his tactics were, the benefit he brought in calling was not enough to offset the loss in fragging. That is a balance equation, and at Liquid, the balance tipped the wrong way.

But here is where I want to pause and warn about a trap. We tend to read rating as a verdict. We see 0.87 and we conclude: this person plays badly. But rating does not measure tactical value. It measures damage, survival, combat efficiency. A commander can have a low rating because his system requires him to sacrifice — playing heavy utility, opening for teammates, accepting death to trade for information or to secure position. Those contributions do not appear on the scoreboard.

However — and this is the crux — even accounting for that sacrifice, 0.87 across 185 maps is still a number at the bottom of the acceptable spectrum. When you combine this number with the team's results, the picture becomes clearer: this is not a commander sacrificing for collective victory. This is a commander sacrificing while the collective still doesn't win.

And this is when we must talk about results, because results are what shape the real story.

THREE MAJORS, NOT ONE PLAYOFF APPEARANCE

Over a 16-month period, Team Liquid competed at three Majors — Counter-Strike's highest arena, Valve-backed and considered the gold standard for every team. In all three, they did not reach the playoffs even once. Not once.

To understand the severity of this number, one must understand the structure of a Major. The group stage is usually run in Swiss format — where teams play based on record, winners meet winners, losers meet losers. Most group-stage matches are BO1 — a single map decides win or loss. Only decisive elimination or advancement matches switch to BO3. The playoffs are BO3, and the final is BO5.

The Swiss format with BO1 has one characteristic: it amplifies variance. A team can win a match through luck, or lose one due to a single bad individual play. In BO1, variance is high. So if Liquid failed at just one Major, you could blame variance. If they failed at two, you might begin to worry. But failing at three Majors in a row, without a single playoff appearance — that is no longer variance. That is a pattern. That is a systematic failure to convert potential into results at the biggest tournaments.

And if you want an even more brutal number, look at the record at the most important events: 5 wins, 11 losses. A win rate below one-third. At the tournaments where this team was expected to shine, they won fewer than one in three matches.

The best result of the entire 16-month project was a top-four placement at FISSURE Playground #2 — a third-party mid-tier event. Let that settle for a moment. The peak of sixteen months of work together, the peak of a signing expected to reshape the team, was a top-four at a non-Major event. For an organization with world-championship ambitions, that is a clear failure of expectations.

I have seen cracks like this before. I saw the champion's crack before the whole world heard it — not because I am smarter than anyone, but because I have a habit of looking at the numbers others overlook. And the pattern at Liquid is a familiar one: a team with individual talent, with resources, with brand, but unable to convert those into results under the highest pressure. That is a sign of a system problem, not an individual one.

STRONG PIECES AROUND A COMMANDER

This is the point I want to give special attention to, because it is the only piece of data in the entire story that favors siuhy, and I believe it matters more than the community usually acknowledges.

An analysis from Dust2.us described Liquid as having "several strong pieces around siuhy". Read that sentence again. Several strong pieces. If that is true — and I believe it is, because Liquid's roster genuinely has quality individuals — then the question is not "why couldn't siuhy leverage those pieces", but "why didn't those pieces form a whole greater than their sum".

When a team has talent but no results, the blame is usually placed on the commander. But in many cases, that is a mistaken oversimplification. The commander is the most replaceable, the easiest to blame, because their role is the least tangible. You can see a shooter miss. You can hardly see a bad tactical call in round 23, when the whole team is tired and the opponent has read the pattern. But when the team loses, people look at the caller.

This does not mean siuhy bears no responsibility. He does. As in-game leader, he is the architect of the system, and the system did not work. But it means the story is far more complex than an individual verdict. If Liquid replaces a fourth commander and still fails, then the problem lies somewhere deeper — in how the organization builds rosters, how it evaluates talent, how it sets expectations and support for the commander role.

And this is why I am concerned about JT's elevation. Not because JT lacks ability. But because elevating an internal figure to the commander role after a top-tier import failed carries a whiff of desperation. That is not a carefully planned plan. That is a move made under duress, when the transfer window has closed and external options have dried up.

My first-person experience following matches has shown me that great teams are built on stability in the commander role, not on individual talent alone. Look at the historically dominant Counter-Strike teams. They don't change their caller every season. They build a system, stick with it, accept early failures, and reap the rewards when the system matures. Liquid, with three commander changes in a short span, is doing the opposite. They are seeking a quick fix for a problem that needs time.

THE ECONOMICS OF A FAILED LOAN

There is another aspect of this story that esports media often overlooks, yet is crucially important: the economic aspect. And it reveals a great deal about how a major organization operates.

siuhy arrived at Liquid in April 2026 on a loan from MOUZ. This is an important detail, because it speaks to Liquid's level of commitment to the deal. A loan, unlike a permanent transfer, is a time-limited experiment. Liquid did not buy siuhy outright. They borrowed him, paid his salary during the playing period, and retained the right to decide whether to buy him out at the end of the term.

Now look at how the story ends. siuhy leaves as a free agent. That means Liquid recouped no transfer fee. They did not sell him to another team to recover capital. They let him go without any financial compensation.

This is an economic structure I call "the failed rental": a short-term, low-commitment deal that ends without creating asset value. Liquid bore the costs — loan fee if any, salary, logistics — for 16 months, and at the end, they had nothing to realize. No player, no transfer fee, no asset. Just a hole in the roster and a story of failure.

From a pure cash-flow standpoint, releasing siuhy is a mild positive. You remove a significant salary from the books, and you do it without incurring a buyout penalty. That is a financially sensible move.

But here is where economics meets tactics. The savings from releasing siuhy are real, but small compared to the opportunity cost of an open roster spot. When you release a commander without an identified replacement, you are accepting the risk that the team enters the next competition cycle with a patchwork, makeshift roster. And in Counter-Strike, where roster cohesion and understanding each other's moves in every play are decisive factors, a patchwork roster is a losing roster.

The announcement of siuhy's departure came with no statement about who would fill the gap. No new commander was announced. That means, at the time this article was written, the position remains open. JT was elevated, but JT was elevated as an internal solution, not as a strategic signing. And while the team waits, the clock is running.

I recall the pandemic period of 2026, when all leagues were suspended and I had to excavate historical data to understand football. I analyzed 104 English Premier League matches played in empty stadiums between June and July 2026. Home win rate dropped from 46 percent to 36 percent. Fouls per match rose 12 percent. Away possession rose by an average of 5.3 percent. Those numbers taught me that environment — home ground, crowd, pressure — changes results systematically, and sometimes we blame individuals while the problem lies in the environment.

A stadium can be empty of spectators, but history never lacks a chronicler. And in Liquid's case, history will record that this was the third consecutive failed project in the commander position.

IMPORT DEPENDENCE: WHEN NORTH AMERICA MUST BORROW ITS OWN SOUL

There is a deeper layer to this story, and I believe it is the most important layer most analyses overlook. It is the story of the region.

siuhy is Polish. He came from MOUZ, a European organization. He was brought to North America to solve a problem for a North American team. This is an inverted model of what we once saw in Counter-Strike history, when North America produced its own world-class commanders and shooters.

North America's dependence on importing talent is not merely a personnel problem. It is a symptom of structural decline in the youth development system of an entire region. When a region cannot produce commanders of sufficient caliber to compete at the highest level, they must import. And when they import, they create a dependence — a loop in which importing reduces the incentive to invest in domestic development, and the lack of investment in domestic development increases the need to import.

This is something I observe in football, and it applies nearly verbatim to esports. In football, the academies of big clubs are often praised as talent-producing machines. But the truth is that under 10 percent of youth players in those academies actually get a path to the first team. Most of them are talent inventory — stockpiled, trained, but never given a genuine opportunity. And when a youth development system works that way, it doesn't solve the talent shortage at the top. It merely creates a reserve layer of talent that is never used.

North America, in Counter-Strike, is in a similar situation. They have a system, but that system doesn't produce enough world-class talent. And while waiting for that system to improve — a process that can take years — they import. They borrowed siuhy from MOUZ. They experimented, they failed, they let him go, and they must search for the next one again.

Parallel to this story is the restructuring of 100 Thieves' Counter-Strike team. Two leading North American organizations, in the same period, both shuffling their rosters. This is a wave, and waves usually have causes deeper than the individual decisions of each organization. It might be an upcoming transfer window. It might be an upcoming schedule change. But whatever the cause, the effect is a region-wide restructuring, and siuhy is just one of the names swept into it.

What I find most interesting in this entire story is the paradox of importing: a North American organization borrows the tactical soul of Europe, and when that soul fails to integrate, both sides are harmed. Liquid lost 16 months and a roster spot. siuhy lost part of his reputation and part of his market value. No one wins in a failed loan. That is its nature.

And there is one more regional aspect I want to address: the possibility of siuhy returning to Europe. With his MOUZ roots, with experience competing at the highest level, he is a natural candidate for European projects seeking a system-builder. This would be a talent repatriation — Europe recovering a Polish commander rather than letting North America keep him. And if that happens, it will be one more sign that Counter-Strike's talent flow still runs from East to West, from Europe to North America, and never the reverse.

THE CONTRARIAN ANGLE: WHERE I COULD BE WRONG

Now comes the part I always reserve for intellectual honesty. I have presented a fairly strong argument that siuhy's departure is the result of a system problem at Liquid. But I could be wrong. And I want to be clear about where I could be wrong.

First, I may have overestimated the impact of organizational structure and underestimated the importance of the individual commander. In esports, unlike many traditional sports, an individual can change the fate of an entire team. An excellent commander can turn a mediocre roster into a championship roster, and a poor commander can destroy a talented roster. If that is true, then replacing siuhy with a better fit could be all Liquid needs. I cannot rule out this possibility.

Second, I may have misread the 0.87. I argued that it sits at the bottom of the acceptable spectrum, even accounting for the role's sacrifice. But if I am wrong, and if 0.87 genuinely reflects a pure skill decline — not system-driven, but siuhy himself losing form — then the story is entirely different. In that case, Liquid was right to let him go, and the problem is not the system but that they chose the wrong person from the start.

Third, I may have focused too much on North America and overlooked a simpler possibility: perhaps Liquid is simply an organization going through a normal difficult period, and every major organization goes through such periods. Not every failure is a sign of a deep structural problem. Sometimes a string of failures is just a string of failures — a bad combination of timing, personnel, and luck. I tend to look for deep patterns, but there is not always a deep pattern to find.

Fourth, and perhaps most importantly, I must admit that I am analyzing from the outside. I am not in Liquid's meeting room. I don't know the conversations that took place, the agreements made, the plans drawn up. I only have the numbers and the public announcements. And numbers, however powerful, never tell the whole story.

I do not oppose tradition; I am only giving tradition new evidence. And the new evidence, in this case, points to a system problem. But new evidence can also be misread. That is the nature of analyzing a sport from outside.

THE RISK ON BOTH SIDES

Let me sketch the risk on both sides after this deal, because I believe how we assess risk reveals a great deal about how we understand the story.

For Liquid, the main risk is not in this deal. The release of siuhy is itself clean on the rules, financially sensible, with no sign of violation. The risk lies in the fact that it is the latest symptom of an unresolved problem. If Liquid cannot solve their commander problem, they will continue to cycle through different names, and each cycle further erodes roster stability, player confidence, and fan trust. The competitive risk here is high, with high probability and high impact.

For siuhy, the main risk is market timing. A 0.87 rating and a Major failure streak are precisely the signals teams look for to undervalue a free agent. And the problem is compounded for a commander, because a commander's value is inherently hard to measure with raw stats. Teams may look at 0.87 and conclude he is no longer good enough, without understanding that the number may be influenced by the system he played in.

But here is where I want to make a testable prediction, because I believe baseless predictions are irresponsible. I predict siuhy will find a new team within three months, and that team will be a European project at the tier-1 or tier-2 level — not another North American organization. The basis for this prediction is his MOUZ roots, his understanding of the European system, and the fact that a European team needing a system-builder, but unable to afford a top-tier commander, may see him as a value bargain.

And I also predict Liquid will not solve their commander problem in the next transfer window. They will enter the next competition cycle with JT, or another temporary solution, and the results will not differ significantly from what we have seen. Not because JT lacks ability, but because Liquid's problem runs deeper than a mere personnel change.

INDUSTRY TRANSMISSION: A SMALL EVENT WITH LARGE IMPLICATIONS

At the macro level, siuhy's departure is a small event. It doesn't change the map of world Counter-Strike. It doesn't shake major tournaments. It doesn't affect Valve, doesn't affect streaming platforms, doesn't affect the betting market. It is a micro event, and I have no intention of exaggerating its importance.

But its significance lies in what it illustrates. It illustrates a roster-restructuring wave sweeping across Counter-Strike organizations. It illustrates North America's import dependence. It illustrates the difficulty of building a stable tactical system in an environment where performance pressure is immediate and patience is scarce.

And it illustrates something I believe is becoming increasingly true in esports: roster stability is a commercial asset. When an organization changes its commander every season, they harm not only their competitive results. They also harm their brand story — the story they tell sponsors, fans, and the market. A 16-month project ending by letting a player go free is a hard story to sell. And in an industry where sponsors increasingly demand stability and predictability, that is a real problem.

Interestingly, the original article I am analyzing comes from an author with expertise in money and business in esports — about how brands navigate sponsorship deals, about which deals last. That tells me the real story here is not "siuhy left Liquid". The real story is "organizations are restructuring rosters in a compressed window", and that may be a sign of a bustling transfer market, or of a budget tightening toward efficiency.

And I recall the story of Guangzhou Evergrande in football. That club didn't collapse because they ran out of money. They collapsed because no one in the organization dared to ask where they were going wrong. There is a lesson there for esports organizations. When you constantly change personnel without ever changing the system, you are treating symptoms instead of the disease. And while you treat symptoms, the disease continues to grow.

THE QUESTION OF A COMMANDER'S VALUE

There is a deeper question this story raises, and I want to end by posing it rather than answering it definitively.

How do we measure the value of an in-game leader? This is a question esports has not yet answered satisfactorily. We have rating, we have damage and survival stats, but we have no index that measures the quality of tactical calls, the ability to read the game, the ability to inspire teammates, or the ability to build a sustainable system.

This means we often evaluate commanders with unsuitable tools. We look at their rating, and we draw conclusions about their value. But a commander's rating is a product of the system they play in, not only of themselves. A good commander in a bad system can have a low rating. A bad commander in a good system can have a high rating. And we have no way to distinguish these two cases just by looking at the number.

This is why I hesitate to conclude that siuhy is the cause of the failure. I have enough data to say the project failed. I have enough data to say 0.87 sits at the bottom of the acceptable spectrum. But I don't have enough data to say siuhy is the primary one responsible. And in esports, where we often rush to judge individuals, that hesitation matters.

The algorithm doesn't get tired, but the fan's heart does. And the fan's heart, in this case, leans toward blaming one person. I want to propose a different reading — a slower, more complex reading, and perhaps one closer to the truth.

PROGRESSIVE THOUGHT

When I look at this story, I don't see a failed player. I see a failed system, and a player swept into it. I see an organization that tried three times to find its tactical soul, and failed all three times, and I wonder whether the fourth time will be different.

What I learned after 23 years of observing this industry is that great organizations are not organizations that never fail. They are organizations that learn from their failures. And the biggest lesson from siuhy's story is not about a specific commander. It is about patience — about building a system taking time, and about personnel change never replacing system change.

If I am right, and if Liquid's problem is structural, then signing a new commander will solve nothing. They will simply repeat the cycle. And while they repeat the cycle, a generation of North American fans will keep waiting for a team that can compete at the highest level, a team they can trust.

There is one thing I know for certain, and it does not come from data but from observing people. The most beautiful moments in esports do not come from perfect teams. They come from teams that struggle, fail, and then find a way. If Liquid can find their way — not by changing people, but by changing how they build people — then siuhy's story will become a chapter in a larger story. A story of maturation.

And if they cannot, then siuhy's story will just be another chapter in a book about missed opportunities. I hope that is not the book they are writing.