Karmine Corp Eliminate LCP's Last Hope at Worlds 2026, Force Swiss Decider

Karmine Corp defeated CTBC Flying Oyster 2–0 in Round 4 of the Swiss Stage at Worlds 2026 on Thursday, 29 October 2026, eliminating the last remaining team from the LCP (League of Legends Championship Pacific) region and forcing an additional Swiss decider in the 2–2 pool, which will be played on Saturday.

This report is built strictly on the match data that is actually available. It covers the scoreline and game-by-game detail, the side-selection and draft questions, the Swiss Stage arithmetic, the regional consequences, and finally the road ahead. Where data does not exist, the report says so plainly rather than filling the gap with a plausible-sounding guess — a necessary discipline at an event like Worlds, where champion-based narratives without pick/ban data are pure invention.

Scoreline and game-by-game detail

The series finished 2–0 in KC's favour. Game 1 ended in 28 minutes with a kill line of 18–3. Game 2 ran 37 minutes; the kill count for that game is not recorded in the available reporting, which means its character can only be inferred from duration.

KC played Game 1 on the blue side, because CTBC had first choice and "took first pick." That particular detail is itself contested, and it is addressed separately below.

The nine-minute gap between the two games is not trivial. In League of Legends, that kind of difference usually signals either a far closer second game or a draft on both sides that pushed victory later. But with no kill data for Game 2, "closer" is an inference from duration alone, not an established fact.

Game 1: 18–3 in 28 minutes — a snowball, not a grind

An 18–3 kill line closed out in 28 minutes is a very specific signature in League of Legends. It means KC built a decisive laning-phase lead, converted it without stalling, and turned kills into objectives. When a team reaches that kind of kill advantage but the game still drags to 35–40 minutes, it usually means the opponent bought time defensively or the lead was not converted efficiently. That did not happen here.

In other words, KC both built the lead and cashed it in quickly. This is a textbook case of tempo conversion — accumulating kills and translating them into towers, dragons, Herald, and eventually the Nexus. Finishing inside 28 minutes with 18 kills means KC kept constant map pressure and never gave CTBC a window to believe in a comeback.

The 18–3 ratio also suggests the match was lopsided in teamfights. Reaching that margin typically requires winning at least two major teamfights and gaining freedom of movement across the map afterwards. But caution is required: all of this is derived from the scoreline and duration, not from a single champion pick, ban, item build, or objective timeline.

Game 2: 37 minutes — a different story

Game 2 lasted 37 minutes, nine minutes longer than the opener. That gap points to one of two things: either the game was genuinely closer, or the drafts on both sides pushed the game long. Both are common in League of Legends, and without pick/ban data there is no way to choose between them.

What can be said is that KC won this series in two games of genuinely different shape. The first was fast and one-sided; the second was long. Winning two games of such different duration on the same day against the same opponent is weak but non-trivial evidence that the team's victory did not depend on a single repeatable trick or a single draft pattern. It can be described as multi-speed adaptability: the ability to win both a fast-tempo game and a slower one.

It is also worth remembering that dragging Game 2 out deserves some credit for CTBC. If CTBC drafted a composition built to scale late and kept the game alive, it was at least partially successful in executing its plan — even though the final result went against it.

Side selection and a contradiction that should not be ignored

According to the match report, CTBC had first choice for Game 1 and "took first pick, which put Karmine Corp on the blue side." Under standard League of Legends draft rules, that description is internally contradictory, because in the normal draft order the blue-side team holds pick one.

There are three possible explanations. First, the writer conflated "the right to choose a side" with "pick order." Second, the event used a non-standard draft order. Third, it is a straightforward reporting error.

None of this changes the result — KC won both games and the series finished 2–0. But it does affect analysis: any claim about who won the draft-side battle in Game 1 becomes unreliable. For readers and analysts alike, it is a small but useful signal that technical terminology was not handled carefully in the reporting of this match.

To understand why blue side matters, it is enough to know that the team with the first pick in the opening phase of the draft usually secures the champion at the centre of its plan, forcing the opponent into a reaction. That is why teams treat side selection seriously. But which champion went to which team in this series is nowhere recorded — and so the entire question remains unresolved.

The Swiss Stage arithmetic: the 2–2 pool and the decider

The basics of the Swiss system are that teams with identical records play each other, teams reaching three wins advance to the knockout stage, and teams falling to three losses are eliminated. In the 2–2 pool, a single match decides who moves on and who goes home.

KC's win has forced an additional decider in that pool, to be played on Saturday. This is the structural cruelty of the Swiss Stage: a team can play well across the whole tournament, but on the final day one best-of series decides the entire campaign.

For CTBC, the arithmetic was merciless. As the last surviving team from the LCP region, it carried the weight of an entire region, and that weight is now gone — because the hope is gone too. Losing your region's final team in the Swiss Stage is a bitter experience, because the impact does not stay confined to one team.

What this means for the LCP

When a region's last team exits, the obvious question is what went wrong at the regional level. But the data available in this report cannot answer that question. All we know is that CTBC lost two games — one in 28 minutes, one in 37. We do not know which champions it picked, which side it played, which objectives it conceded, or where its plan broke.

One general conclusion can still be drawn: regional strength can no longer be assessed from a single team's performance. Worlds' format already guarantees that a tough draw or one bad day can end an entire region's representation. CTBC's exit is a direct illustration of that structural risk.

On the other hand, it is worth remembering that a loss in the Swiss Stage does not mean a team was bad. It means only that its opponent was better on the day. CTBC fought to 2–2 by winning two matches at the tournament — an achievement in itself that should not be erased by the final defeat.

Karmine Corp: what winning two different shapes of game means

The win matters for KC on several levels. First, it came in a win-or-go-home situation where the pressure is at its maximum. Second, it came against a team that was its region's last hope and had no alternative but to win — meaning the opponent's motivation and preparation were both at their peak.

Third and most interesting, KC won in two completely different game shapes. A 28-minute 18–3 game and a 37-minute game is not the repetition of a single strategy. At champion-pool level this cannot be assessed, because pick/ban data is unavailable. But at playstyle level it suggests, at minimum, that KC has more than one route to victory.

That matters for the matches ahead. In a best-of series, opposing teams look for patterns when preparing their drafts. If your opponent wins only one kind of game, stopping them is easier. KC showed in this series that it can win fast and slow — though the signal is weak and should not be inflated into a larger claim.

The absence of draft data: a reporting note

The available reporting on this match does not record a single champion pick or ban. That is a serious gap, because almost every explanation in League of Legends begins with the draft. Without pick/ban data, none of the following claims can be established: champion-pool fit, one-trick exposure, Fearless draft or global ban-pick effects, and the prevalence of any particular meta champion.

This does not mean the report is bad. It means it is a results piece, not an analytical one. Trying to extract technical conclusions from such a report and presenting them as fact is precisely the mistake to avoid. Readers are entitled to know which information is official and which is inference.

This report adopts one rule: where there is no data, it says "not available." That is honesty toward the reader and a standard for future reporting — because at an event like Worlds draft data is normally available, and its absence is itself a signal that a link in the reporting chain is missing.

Patch and meta: what can be extracted from this match

The tournament patch version is not stated in the available information. That means any patch-level conclusion would be speculation. The only signals available are game length (28 minutes and 37 minutes) and kill spread (18–3 in Game 1).

From those two signals, a limited but solid set of observations follows. First, Game 1 was a snowball, not a grind. Second, Game 2 was longer, suggesting either a closer contest or a scaling draft. Third, the series was not decided by a single repeatable pattern, because the two games had different shapes.

Beyond that, little can be said. The direction of the meta, which champions benefited, which suffered — none of this can be assessed without pick/ban data. This report deliberately leaves those questions open, because a correct question is better than a wrong answer.

Tournament patch locking: an unresolved risk

Worlds traditionally runs on a locked tournament patch, meaning changes shipped to live servers during the event do not affect matches. But no version number is given in the available information, so it cannot be confirmed that this held true this time.

This is not merely a formality. If the tournament patch differs from live, the practice-server scrim data of teams in the 2–2 pool becomes partially non-transferable. What teams practise and what works on stage can diverge. This is a real risk, but an unmeasurable one at present.

This report therefore flags the risk rather than quantifying it. For any analyst, it matters to distinguish uncertainty that comes from a lack of knowledge from uncertainty that comes from missing information. Here both are present at once.

The limits of the data: what is known and what is not

The known facts are limited but clear: the match took place on Thursday, 29 October 2026; KC won 2–0; Game 1 lasted 28 minutes at 18–3; Game 2 lasted 37 minutes; CTBC had first choice for Game 1; and the win forced Saturday's decider. The Grand Final is scheduled for Saturday, 14 November 2026.

The list of unknowns is far longer: both teams' picks and bans, champion selections, item builds, objective timelines, individual player statistics, the kill score of Game 2, the tournament patch version, and which teams will contest the decider.

This list exists to show readers what the analysis in this report rests on. When a media report calls a match "a draft win" or "a meta win," it is usually based on pick/ban data. That data is absent here, which is why the scope of this report is deliberately narrow.

Saturday's decider: what to expect

The decider will be played on Saturday and will settle the fate of the 2–2 pool. Which teams will face each other is not in the available information — so naming a likely opponent here would be speculation, not fact.

What can be said is that the pressure of the final day of the Swiss Stage is a factor in itself. In a best-of series, teams must prepare multiple draft plans within a single day, and the speed of adaptation becomes decisive. Teams with a wider champion pool are better placed — but applying that claim to any specific team requires that team's pick/ban data, which is not currently available.

For KC, the good news is that it won two different kinds of game under pressure, showing it does not depend on a single plan. The bad news is that one good day in the Swiss Stage guarantees nothing.

14 November: the shape of the Grand Final

The Grand Final will be played on Saturday, 14 November 2026. That leaves a two-week gap after the end of the Swiss Stage, during which the knockout matches will be played. The interval gives teams preparation time, but it also raises a question: how much of the form shown in the Swiss Stage will survive two weeks later?

History offers many examples of teams that looked excellent in the Swiss Stage and lost their rhythm in the knockout rounds, and of the reverse. The cause is not purely mental; in a best-of format, draft preparation matters far more, because opponents arrive having studied your patterns.

For KC, what matters is how much of the "two different shapes" element of its win survives into the knockout stage. If opposing teams plan to stop its fast-tempo game, does it have a second route to victory in a slower game? The 37-minute result in Game 2 is a small but positive signal on that question.

Side and pick order: a general note

Confusion around side selection is common in League of Legends, because "choosing a side" and "pick order" are two different things. In the standard arrangement, the blue-side team holds the first pick, while the red-side team gains the advantage of the last pick as a counter. That is why some teams want first pick and others want last.

This series is described as CTBC taking first choice and then "first pick," which put KC on the blue side. Under standard rules the order does not line up. Since the result was already settled, the discrepancy had no effect on the match — but it illustrates how important it is to record technical details accurately.

The practical takeaway for readers is that whenever a report speaks of "the advantage of choosing a side," it is worth asking which team was on which side and what the pick order was. These are two separate pieces of information, and conflating them confuses the analysis.

Conclusion: a clear result, a limited story

What this match establishes beyond doubt is this: Karmine Corp beat CTBC Flying Oyster 2–0, winning Game 1 in 28 minutes at an 18–3 kill line and Game 2 in 37 minutes, and the result eliminated the LCP region from Worlds 2026 entirely. It also forced Saturday's decider in the 2–2 pool.

What it does not establish is equally clear: no conclusion about patch, meta, champion priority, or draft strategy can be drawn from this match, because not a single pick or ban is recorded in the available reporting. The analysis that is available rests on duration and kill spread — and it must stay within those limits.

The biggest lesson of this series sits off the Rift: the result is clear, but a large share of the data needed to interpret it is missing. An honest report states the result firmly and limits its interpretation with equal care.

Fact box

Event: Worlds 2026, Swiss Stage, Round 4 | Date: Thursday, 29 October 2026 | Result: Karmine Corp 2–0 CTBC Flying Oyster | Game 1: 28 minutes, 18–3 kills | Game 2: 37 minutes, kill score not available | Side: KC on blue side in Game 1 | Impact: LCP's last team eliminated; decider forced in the 2–2 pool | Decider: Saturday | Grand Final: Saturday, 14 November 2026 | Unavailable data: picks/bans, champions, items, objective timeline, patch version, individual player statistics