PAOK Falls to Lietkabelis 86-95: An Unbeaten Run Ended by a Perimeter Hole

At Panevėžys, Lithuania, PAOK touched control of the game exactly once. A 15-2 run in the third quarter cut a 13-point deficit to one (63-62), and it looked as though the visitors had found a way to break the game open. Lietkabelis answered with a 14-2 run immediately after, restored a 10-point lead by the end of the third, pushed it to 13 at the start of the fourth, and closed out a 95-86 win. PAOK's unbeaten start in the EuroCup ended in the hardest possible place: a Lithuanian arena, against an opponent that hit 6 of 9 three-pointers in the first half alone.

The problem lies in a repeating mechanism. A perimeter-defense hole clear enough for the next opponent to note down and reuse.

The EuroCup is Europe's second-tier continental club competition, played under FIBA rules rather than the NBA's CBA. The differences are not small: FIBA has no defensive three-second rule, a shorter three-point line, and smaller courts. That means packed, help-heavy defenses are permitted to exist far more than in the NBA. It also means that when a team still concedes 6 of 9 threes in a half, it is not bad luck.

PAOK entered this game unbeaten. Lietkabelis, a mid-tier side in the competition, had nothing to lose at home. The balance before tip-off tilted toward the visitors, and that is exactly why this result deserves more than a routine post-mortem.

Based on my experience covering EuroCup games across multiple seasons, I split this one into two clear halves.

The first half is a perimeter-defense story. Lietkabelis hit 6 of 9 threes in the first half. Two of their players, Schumacher and Jaramaz, scored 23 of the team's 50 first-half points. PAOK ran into difficulties, played slowly, and trailed. The main problem was identified clearly: perimeter defense. Not offense. Not rebounding. Perimeter defense.

The second half is an adjustment story. In the third quarter, PAOK looked completely different. The 15-2 run cut a 13-point gap to one. That is a real signal: Trinchieri can fix a game while the ball is live. But then Lietkabelis countered with a 14-2 run, and PAOK had no Plan B. That was the decisive tactical event of the game, not a shot, but the fact that the visitors ran out of answers once the opponent stabilized.

The fourth quarter is the Marcus Foster story. He scored 14 of his 21 points in that quarter alone, pulling the game back to nine. But every time PAOK closed in, Schumacher answered. PAOK's comeback had one source, and therefore one dimension.

On the numbers: PAOK had four players score 21, 17, 15 and 13 points. Even distribution. But even scoring distribution does not mean even functional distribution. Foster carried the late scoring, Calathes ran the offense with 13 points, 6 rebounds and 8 assists, Osman and Tyree added more. The thing that lost the game sat at the other end of the floor.

This is where I have to stop on time. The box score offers counting stats only, no efficiency. No FG%, no TS%, no PER, no +/-, no On/Off. A 23-point game on poor efficiency is entirely different from a 23-point game on elite efficiency. Data does not lie, but the people reading it do. In this case, the reader lacks the raw material to draw efficiency conclusions. I will only speak to volume, and to mechanism.

For Lietkabelis, Jaramaz was the true two-way engine with 18 points, 5 rebounds, 4 assists and 3 steals. That balanced line, plus his defensive work, explains the win better than any scoring figure.

For PAOK, the most important data point is not the leading scorer. Donatas Motiejūnas debuted with 6:49 and 2 points. A player of his caliber used that sparingly points to a deliberate integration and conditioning process, not panic. That is a watchpoint, not a verdict.

Here I want to push against the current a little, because the story being told is a touch too tidy.

The common telling goes: PAOK lost their unbeaten run, the perimeter defense has a problem, end of story. But the structure of the result deserves closer scrutiny. Lietkabelis hit 6 of 9 threes in the first half, roughly 67%. The final margin was only nine. If that holds, then for most of the rest of the game PAOK played level with or better than its opponent in every category that was not three-point shooting and not Schumacher. In other words, a meaningful share of this loss came from a burst of long-range variance, not from a total systemic collapse.

I am not using that as an excuse. I am using it to separate two kinds of risk. Variance risk fades after one night. Systemic risk stays and gets exploited by the next opponents. The real question is whether those 6 of 9 threes came because Schumacher and Jaramaz had a hot night, or because PAOK let them shoot comfortably from the start. The available data cannot answer that. But the way Lietkabelis countered with a 14-2 run the moment PAOK closed in, while still targeting the same shooters, leans toward the second explanation.

There is another blind spot in the telling: the "brave defeat" frame. Foster exploded in the fourth, PAOK repeatedly got back to nine, the game looked tense. That framing softens the perceived severity for viewers, and can mask the defensive problem that had existed since the first half. The fall of a giant is a gift to the observer, but only if the observer is willing to read the hard part.

One more point: a late-game offense dependent on Foster is a regression-prone mechanism. A player carrying 14 of 21 points in a single quarter means the half-court system is not generating a second option when Calathes is locked up or load-managed. That is a structural concern, independent of one result.

For PAOK, this loss is not alarming in the standings. A road game in Lithuania against a home side that shot well, in a group format, is a low-severity hit. But it is a high-signal event for scouting: from now on, their perimeter defense sits in every opponent's notebook.

Three variables I will track over the next one to three games: whether opponent three-point percentage against PAOK stays above 40%, whether Motiejūnas' minutes ramp toward 15 or more, and whether PAOK adjust their close-out rules and screen navigation, or keep letting shooters fire comfortably.

For Lietkabelis, this win is a boost to their domestic profile. For PAOK, it is a test of error correction. Empires are not built in a night, but data can build them in a season. The season is long, and one road loss says nothing about the destination, unless it repeats.