28 Minutes at 18-3, Then 37: Karmine Corp Eliminate LCP's Last Team, But the Scoreboard Is Only Half a Record

28 minutes, 18-3. The Game 1 scoreboard carried a number that did not belong to a close contest. I watched the series with a timer running — the game was streaming on screen and two lines were filling up my notepad: 28 and 37. Game 2 ran nine minutes longer than Game 1. In League of Legends, nine minutes is not a small gap; it points to two different drafts, two different tempos, two different risk profiles. Karmine Corp won both games and CTBC Flying Oyster — the last surviving LCP team — exited Worlds 2026. Before the story had a sentence, the spreadsheet had a verdict. And that same spreadsheet is telling you which rows are missing.

Swiss Stage, Round 4 of Worlds 2026, Thursday 29 October 2026. In the 2-2 pool every series was a knockout — lose and go home, win and enter Saturday's decider. CTBC Flying Oyster carried the heavier stake because they were the last LCP team; with them gone, the entire region left the tournament. For Karmine Corp the question was different: the EMEA side had shown rhythm domestically, but its real test in an international bracket was still pending. The Grand Final is on Saturday 14 November 2026 — this win brought KC two weeks closer to the trophy, but Saturday's decider comes first.

Years of watching this beat live have given me one habit: I write duration before I write the scoreboard. Duration is the first number that says anything about a draft's intent, and it is the number result pieces almost always leave out. A game ending 18-3 at 28 minutes is a clear message — not a late-game scaling win, but a laning-phase gap converted into objectives early. Reaching 18-3 at roughly 28 minutes means map control arrived early and nothing stalled in the mid-game.

Game 2 ran to 37 minutes — exactly nine more. Unfortunately the original report carries no kill count for Game 2. So saying "Game 2 was closer" is an inference from duration, not a measured fact. That gap is the limit of this entire report, and hiding it would be the biggest error. A missing row is a louder source than a quoted one. No Game 2 kill count, no objective table, no gold differential — three absences stacked together. Without them, "KC won in two different shapes" is an observation, not a conclusion.

The second problem sits in the side-selection reporting. The article states CTBC had first choice for Game 1 and "took first pick, which put Karmine Corp on the blue side." In a standard League of Legends draft the first pick belongs to blue side — so the sentence contradicts itself. Three explanations exist: the reporter conflated "side choice" with "pick order"; the event used a non-standard order; or it is a straight reporting error. The result does not change, but any analysis of who won the Game 1 draft-side battle is now unreliable.

There is another blank to name: the patch. Events at this level are usually played on a locked tournament patch, yet no version number appears anywhere in the report. Champion picks, bans, items, objectives — not one recorded. With no pick/ban data at all, no claim about champion-pool fit, one-trick exposure or global ban-phase effects can be built. I have worked with season-long early-game conversion baselines in the Korean circuit — there, a 28-minute 18-3 is a row you immediately compare against that season's average. That average is not available here. The comparison is not a prescription, only a contrast: there the data scaffolding already exists, here I rebuild it every single time.

Now the part that will not make headlines. A two-game sample is a two-game sample. KC won a 28-minute blowout and a 37-minute long game — calling that "multi-speed adaptability" is tempting, but at n=2 it is a hypothesis, not a finding. If Game 2 stretched to 37 minutes because KC built an early lead and coasted, the shape differed but the strength did not. If it was a two-way scrap, the story changes entirely. Without kill counts, both possibilities look identical — and that is this report's real crisis.

Reading 18-3 as "one-sided" is equally wrong. 18-3 is a kill differential in one map, not a certificate of team tier. In League of Legends a single-map kill line is usually built from draft matchups and one or two early skirmish calls, not from the actual distance between rosters. CTBC held first side choice — meaning they are credited with the structural edge on map one — and still lost 18-3 in 28 minutes. That is interesting, but for now it is an anomaly with an incomplete explanation.

And tying LCP's collapse to KC's win is the easiest correlation-versus-causation trap available. A region's last team going out is a story about regional structure — visas, scrims, funding, talent pipelines. KC's series win is not the cause of that story, only a single day within it. The phrase "last LCP team" carries emotional weight in the report, but as data it is one fact: no LCP team remains in the bracket.

So the verified list is short. One, KC won the series 2-0 and CTBC are out. Two, Game 1 ended 18-3 in 28 minutes. Three, Game 2 ran 37 minutes. Four, CTBC held side choice for Game 1. Five, Saturday brings the 2-2 decider and the Grand Final falls on 14 November 2026. I rebuilt the season from receipts nobody thought to keep — in this matchup those receipts are five lines long.

The contrarian angle

The biggest illusion of the Swiss 2-2 pool is that a 2-0 series becomes a forecast for the next round. It does not. The teams you meet at 2-2 are all equally tired and equally under pressure; winning there often only means you made fewer draft errors that day. Whether the same KC wins the same kind of map on Saturday is not settled by this series.

A second inverted angle: a long game can be evidence of KC's sluggishness rather than its flexibility. Games stretch to 37 minutes when the leading team cannot close. If KC were ahead in Game 2 and still needed 37 minutes, a missing closeout is a genuine concern. The report has no kill count, so I am holding this as a possibility, not a claim — that is the difference between an audit and an opinion.

A third: the side-selection reporting error affects forecasting, not the result. If we cannot establish who was on which side in Game 1, we cannot conclude "CTBC lost the side-choice battle" — which happens to be the first comment in every post-match thread.

Forward signal

Saturday's decider is a clean test for KC, and the first question is not the draft but the first 15 minutes. If KC builds an objective lead inside 15 minutes again, the 28-minute pattern holds; if the map stretches past 35, the 37-minute pattern holds instead. For either to be proven, the full kill table from Saturday's series has to be published.

KC need one more week of wins to reach the Grand Final on 14 November 2026. The archive was incomplete, which is exactly where the story lived — when the scoreboard arrives on Saturday, my first question will not be who won. It will be how many kills fell in Game 2, and at what minute. Until that number lands, 18-3 is only a good half-sentence.