Besiktas 109-93 Maccabi Tel Aviv: A Newcomer's Three-Point Storm and the Defensive Fatal Flaw of a Giant

Minute 15 in Belgrade: the moment the scoreboard said it all

When the game clock passed the fifteenth minute in Belgrade, the scoreboard displayed a ratio that made the entire arena hold its breath: Besiktas had made 7 of their 10 three-point attempts. Not seven of twenty, and not two or three lucky shots that rattled in. Seven of ten, in the EuroLeague, against a team that had spent years inside the playoff race. Maccabi Tel Aviv, the nominal home side, stood and watched their opponent turn the area beyond the 6.75-metre arc into a private practice court.

I watched this game from a small apartment in Tokyo, where I still build podcast scripts every night. And the first thing that made me sit up straight was not the final score of 109-93, but the way Besiktas built their margin. They did not score in a single burst that then died out like a summer storm. They scored steadily, layer by layer, to the point that by minute 34 they had already reached 90 points. A road team, in an unfamiliar arena, reaching 90 points before the game entered its closing stretch — that is the signature of either a smoothly running offensive machine, or a defence that had given up long before the final whistle.

But precisely because I have spent nearly a decade reading numbers for a living, I forced myself to ask the opposite question: was that three-point storm a repeatable system, or just a one-night surge that any team produces a few times a season? Data does not lie, but the people who read it do. And the way regional media is reading this game, I fear, is missing the most important thing. The Greek outlet headlined the game with a word of tempest, calling Besiktas a "raging" side, and described them as "dominating from the first minute to the last." A very dramatic reading. But it stands on a very thin foundation, and I will show you why.

Context: a newcomer, a giant, and an arena that is not a home

To understand this game, you have to place it inside the right EuroLeague frame. This is Europe's top-tier club competition, operating under FIBA rules, not NBA rules. Each game consists of four ten-minute quarters. The three-point line sits at roughly 6.75 metres, shorter than the NBA's 7.24 metres. That means, structurally, the long shot in Europe is cheaper and easier to reach, and a team with two or three capable shooters can turn the arc into a far more economical weapon than grinding everything out in the paint.

Besiktas entered this season as a EuroLeague newcomer. That is the detail I consider the most important in the entire context, and it is also the detail that most post-game reports skip. A club making its first appearance in the continent's toughest arena usually has two paths: build slowly around young talent and accept paying the price in defeats, or spend money to sign established veterans in order to build credibility immediately. Besiktas clearly chose the second path. Their roster includes names any European basketball fan would recognise: veteran shooters, players who have fought in this competition for years.

On the other side, Maccabi Tel Aviv is one of the oldest and most decorated brands in European basketball. But there is a variable that very few people mention when discussing them: Maccabi is currently playing its "home" games in Belgrade, rather than in its actual arena in Israel. This is a league-governance adaptation, born from security reasons outside the game itself. Competitively, the consequences are cruel and silent: a team losing its true home-court advantage, losing its familiar stands, losing the rhythm of competitive life it had built over decades.

I once wrote that Japan taught me the treasure is always there, you simply have to be patient enough to dig. In this game, the treasure lies in the very detail the reports skim over: Maccabi is no longer itself, and Besiktas is in the phase where its competitive window is opening. When a rising team meets a team losing its structural advantage, the result can look like a storm, but its essence is a very logical reordering of the hierarchy.

The flow of the game, read carefully, shows this clearly. Besiktas built a double-digit lead inside the first quarter. At one point the score was 25-41. The peak margin reached 57-76. And by minute 34, they had 90 points. This is a pattern of sustained separation, not a single burst that faded. But right here, I must plant a warning flag: the source data for this game contains no offensive rating per 100 possessions, no defensive rating, no pace. We have only the score and qualitative descriptions. For someone who works with data, that is a situation that demands downgrading confidence to a medium level, and I will say that plainly rather than pretend I have a full statistical set.

Dissecting the three-point storm

The spine of this game is a three-point bombardment. Besiktas fired from beyond the arc again and again, and Maccabi's defence was breached from beyond the arc again and again. The 7-of-10 mark at minute 15 is a talking number, but what needs analysis is not the number itself, but the way it was produced.

There are two kinds of three-pointers in modern basketball. The first comes from the ball being moved continuously, creating completely open shots, and when a team has multiple shooters spread around the arc, defending it becomes an unsolvable problem without changing your approach. The second comes from difficult, heavily contested shots, and a high success rate reflects only a single night of personal brilliance. From what is described about the game, Besiktas had both: open shots born of ball movement, and difficult shots of the "off-balance" kind that Korkmaz took.

The tactical crux is this: a team can only shoot 7-of-10 from deep if the opposing defence grants them rhythm. If Maccabi had changed how they defended — switching relentlessly, or blitzing the ball handler as soon as he crossed half court — the story would have been different. The fact that they could not do this throughout the first quarter and much of the second reveals a systemic problem, not an isolated error.

I have told the listeners of my podcast many times that possession percentage in football is the most deceptive statistic, and in basketball its cousin is the three-point percentage in a single night. Both are numbers that escalate easily, impress easily, and deceive the reader most easily. A team shooting 40 percent from three across a season is a good team. A team shooting 70 percent in one night is a lucky team. The distance between those two numbers is the distance between a system and a lucky roll of the dice.

There is one very notable detail: Besiktas did not merely shoot threes well. They sustained that momentum across different phases of the game, rather than only in one quarter. In the first half they built a double-digit lead. In the third quarter, they surged again on a run of three straight Brown three-pointers, pushing the gap to 16. That is the signature of a team with multiple scoring sources, rather than one dependent on a single individual. But it is also the signature of a paradox: diverse scoring sources reduce dependence on one player, yet increase the whole team's variance. When all five of your shooters can go cold at the same time, you carry a higher risk of collective collapse than when you rely on a single star.

Maccabi and the "sequential" offence

If Besiktas attacked in continuous waves, Maccabi attacked in disjointed, sequential fragments. This is my second major finding, and also the one I consider to have more long-term value than the scoreline itself.

Look at the sequence of Maccabi's scoring. First, Sorkin scored in the paint, opening the home side's offence. When Sorkin was shut down, Tyus appeared to "unstick" the offence. Then came Clark, who scored six straight points before the halftime break. Three names, three phases, three different scoring sources. It sounds as though Maccabi had multiple options. But read carefully, this is a "sequential" offence: each time one option was figured out, they moved to the next, instead of running a layered system in which several options coexist side by side.

What is the difference between a sequential offence and a layered one? A layered offence always has at least two threats at once: a ball handler driving, a shooter waiting in the corner, a big man rolling to the rim. The opposing defence is forced to choose, and that choice creates the gap. A sequential offence has only one threat at a time. When the defence snuffs it out, the offence falls into emptiness until another individual conjures something on his own.

That is exactly what happened to Maccabi. They had no primary creator who could sustain rhythm throughout the game. Their offensive output came in episodes, in flashes, not as a current. In elite basketball, a team can survive with a sequential offence for a few quarters if its individuals are good enough to generate points on their own. But they cannot survive an entire season with that model against well-organised defences.

What is worth noting is that, at the moment Clark scored six straight before the break, Maccabi had cut the deficit to just 46-52 heading into the locker room. Six points. A fragile margin. Had Maccabi possessed a genuinely layered offensive system, they could absolutely have flipped the game in the third quarter. But they did not, and the third quarter proved it when Besiktas exploded again.

Here I must admit a limit of my analysis: I have no data on assist numbers, on pass-to-score ratios, or on the volume of open shots Maccabi created. I have only qualitative descriptions of the scoring sequence. So my "sequential offence" judgment carries medium confidence, and I state that clearly so you do not read it as an absolute conclusion. But that sequential model matches another sign: a team caught in a losing spiral usually loses its offensive structure first, because structure demands confidence and mutual trust — the things eroded fastest when you keep losing.

Wilbekin, Korkmaz, Brown: three men and a personnel philosophy

In a game where Besiktas scored 109 points, what is easily overlooked is how those points were distributed. This was not a performance of one star carrying the whole team. It was a concert of many musicians.

Korkmaz scored eight early points, found his rhythm, and hit an off-balance three — the kind of shot only a scorer with an instinct for hunting points would dare to take and could make. Brown contributed a run of three straight three-pointers in the third quarter, pushing the margin to 16 and snuffing out any Maccabi hope of a comeback. And above all was Wilbekin, who reached the milestone of his 624th career three, tying Juan Carlos Navarro to sit joint-third on the EuroLeague's all-time three-point list.

Wilbekin's milestone is the most valuable piece of information in the entire source article, and I say that deliberately. The 109-93 result will be forgotten within weeks. A historic milestone belongs to the archive. Matching the record of Navarro — a living legend of European basketball — is a marker that places Wilbekin among the most durable and outstanding shooters of his generation. That is a verifiable-class fact, independent of the game's result.

But here I must plant a second flag. Every source information point in the original article carries a "no source" label. That means I cannot independently verify that Wilbekin plays for Besiktas, that he actually reached his 624th career three in this game, or that the figure matches official EuroLeague data. In terms of roster position, the article's narrative flow places Wilbekin on the Besiktas side, but that is an inference from narrative position, not an explicit statement. As someone who works with data, I must say plainly: this milestone needs to be re-verified before it is cited as a confirmed fact.

On the personnel side, there is a very clear logic behind how Besiktas built its roster. A EuroLeague newcomer seeking to build credibility immediately usually does not bet on a long-term youth-development project. They sign established veterans — players with a name, with experience, and with the ability to deliver immediate results. This is a "win-now" strategy, and it has a financial consequence I will discuss later.

From a career-age perspective, Wilbekin is in the late-prime stage of his career. His milestone confirms a long and celebrated EuroLeague career. But his current value has become specialised: shooting and leadership, no longer peak two-way play. Decline risk on athletic tools is medium-to-high, but decline risk on shooting craft is low. Korkmaz is in his prime, but the way he "found rhythm" in this game suggests a streak-dependent profile.

There is one thing I want you, the reader, to keep in mind: Besiktas distributes its scoring across multiple shooters, which reduces dependence on a single individual but increases whole-team variance. A night when all three shooters go cold together is an entirely plausible scenario, and in that case, it is unclear how Besiktas would score. This is the biggest blind spot in the "Besiktas storm" story.

The lie of the 16-point margin

Now I want to talk about what I consider the most important thing, and also the thing regional media has misread: the 16-point final margin.

A score of 109-93 sounds very convincing. It evokes the image of a team utterly dominating, giving its opponent no chance. And indeed, the original article described Besiktas as "dominating from the first minute to the last." But there is one detail that shatters that image entirely: the halftime score was 46-52. Six points. A six-point margin after twenty minutes of play.

Let me spell out this internal contradiction. You cannot both "dominate from the first minute to the last" and enter the break with only a six-point lead, after your opponent has just produced a scoring run to cut the deficit. If Besiktas had genuinely dominated from the start, they would have led by 15 or 20 at the break. The 46-52 figure tells us the game was balanced for much of the first and second quarters, before Besiktas exploded in the third.

This is where the skill of reading data matters more than simply having it. A final score does not tell you how a game unfolded. It only tells you the last stopping point. It is like reading a book by looking only at the last page — you can draw a completely wrong conclusion about the plot. The 16-point final margin was created mainly in the third quarter, when Brown hit three straight threes and Besiktas pulled away. Before that, this was a game in which Maccabi still had a chance.

This completely changes how to read the result. Instead of "a newcomer team dominating a giant," we have "a newcomer team meeting a giant in crisis, holding balance through the first two quarters, then pulling away thanks to a burst of long-range shooting in the third." The second reading is far less dramatic, but it is closer to the truth.

The failure of a giant is a gift for the observer. And the gift in this game is not the shock of a newcomer beating a giant. The gift is the evidence that so-called "domination" is often an illusion created by the final score, and that those who take the trouble to read more carefully will see an entirely different story.

There is one more detail I want you to notice: the original article says Besiktas reached 90 points by minute 34. In the EuroLeague, with four ten-minute quarters, minute 34 falls within the fourth quarter. Reaching 90 points by then is not unusual for a strong offensive team, but it matches the pattern of sustained separation I described. What I want to stress is this: if we lack pace data, we do not know whether 109 points was the product of a fast game with many possessions, or of an extraordinary offensive efficiency. This is an important data gap, and anyone analysing this game without acknowledging it is selling you a confidence they have no right to.

The Besiktas defence: an unverified unknown

There is a paradox in this game that almost nobody mentions: we praise Besiktas for winning 109-93, but we do not actually know how good their defence is, because it was never seriously tested.

When an opposing offence collapses on its own — as Maccabi did in this game with its sequential offensive model and its prolonged droughts — the winning team's defence looks better than it really is. This is a classic analytical trap: we look at the defensive result and assign it a quality that has not actually been proven. Maccabi scored 93 points. That is not a low figure. On another night, 93 points might be enough to win. The original article even hinted at this subtly: 93 points might have been enough on another night.

So the right question is not "how well did Besiktas defend?" but "how well does Besiktas defend against a well-organised offence?" We have no answer to the second question from this game, and that is why I do not rush to slap the "contender" label on them the way the media is doing.

Let me connect this to a personal experience. When I was seventeen, I wrote a long analysis predicting that the Golden State Warriors could be at risk if they relied too heavily on a three-point system while neglecting defence. Many dismissed that piece as unfounded doubt. But what I learned was not "I was right," but a larger principle: a brilliant offence can conceal an average defence for a while, but when an opponent is good enough to lock down that offence, the defence is exposed. In this game, Besiktas has not yet met an opponent good enough to do that.

With Maccabi, the problem is the reverse. Their offence scored 93 points, enough to compete in many games. But their defence — especially perimeter defence — collapsed systematically. This is the key difference: a team losing because of a bad offence can fix things relatively quickly by adjusting personnel or tactics. A team losing because of a systemic defensive problem is much harder to fix, because defence demands synchronisation, discipline, and collective trust — things that cannot be bought with a single contract.

The Belgrade problem and the cost of a neutral venue

There is a variable I consider the most underrated in this whole story: Maccabi having to play its "home" games in Belgrade.

In basketball, home-court advantage is one of the most carefully measured variables. It comes from many sources: familiar crowds, a familiar arena, travel habits, daily routines, and the psychology of playing in a safe environment of one's own. When a team loses all of those, it does not merely lose a little edge. It loses part of the competitive structure of its entire season.

Maccabi plays in Belgrade for security reasons outside the game. This is a league-governance adaptation applied to Israeli clubs in recent years. Competitively, the consequence is very clear: a team that once built its reputation on an arena regarded as one of Europe's hardest fortresses now has to play on a neutral court, before a crowd that may be neither as large nor as fervent as at home.

This does not excuse Maccabi's poor defence. But it provides the context needed to understand why a decorated club is sinking into a winless run. A neutral venue erodes home-court advantage, and home-court advantage is often what helps big clubs get through difficult patches of form. When you lose that, every other problem becomes more severe.

I want to stress this is a hypothesis with medium confidence, not a firm conclusion. I have no data on Maccabi's home-and-away record across seasons to compare. But in terms of structural logic, losing home-court advantage is an accumulating factor: it does not cause one specific defeat, but it weakens the foundation on which every other success is built.

The view from Tokyo: variance, data, and the habit of misreading a game

I have been doing this work since I was a sixteen-year-old girl, building a manual Excel spreadsheet to track the scoring efficiency and defensive effectiveness of a 1.88-metre guard named Rui Hachimura across fifteen games of Japan's U18 youth league. When he moved to the NCAA, I already had a detailed data trove that no Japanese sports outlet possessed. I realised the market was severely lacking quantitative analysis of young talent, and I decided to fill that gap.

That experience taught me something I carry into every article: data does not lie, but the people who read it do. In the Besiktas-Maccabi game, the data says Besiktas won 109-93, that they shot 7-of-10 from three by minute 15, that they reached 90 points by minute 34. But the people reading those numbers can conclude that Besiktas is a title contender, that Maccabi is finished, that this storm will continue. The data does not say those things. People say those things.

This is where the concept of "variance" becomes the analyst's most important tool. In basketball, the result of a shot is a random variable. A good shooter may have a long-run success rate of 40 percent, but on a given night he can shoot 7-of-10 or 1-of-10. Both results are entirely consistent with his true ability. A bad analyst looks at one night's result and draws a conclusion about ability. A good analyst looks at one night's result and asks: how much is ability, how much is variance?

In this game, the variance component is large. A 7-of-10 three-point rate in the first quarter is not a repeatable baseline. It is a random peak, and random peaks always tend to regress to the mean. That is why I do not rush to call Besiktas a contender. Not because they are not good. But because one game is not enough to distinguish between a good team surging and an average team enjoying a lucky night.

I once said that an empire is not built in a night, but data can build them in a season. One game is a single data point. A season is a set. How we read a single data point determines how we understand the whole set. And in this game, the way the media reads a single data point is creating a story that the data itself may refute within weeks.

In Japan, where I live and work, I learned that the treasure is always there, you simply have to be patient enough to dig. In this game, the treasure is not in the scoreline. The treasure lies in two signals: first, a EuroLeague newcomer can beat a giant on the road by shooting threes superbly; second, a giant has a systemic defensive problem, and that problem may shape its entire season. The second signal is more durable than the first, and that is what the reports are missing.

The next-game variable: three signals to track

The 109-93 result will soon become the past. What remains are the open questions this game raised, and they are precisely the variables that will shape the coming weeks of the EuroLeague.

The first signal is the Maccabi-Panathinaikos game. This is the best test of whether Maccabi's decline is a temporary slip or a season-long problem. If Maccabi loses heavily or continues to leak defensively against Panathinaikos, the "crisis" narrative will gain firm ground. If they win or lose narrowly, the entire commentary frame will reset, and the loss to Besiktas will be named more accurately: a bad night for the defence, not a collapse.

The second signal is Besiktas's capacity to regress. Watch their three-point percentage over the next three to five games. If they continue to sustain a high efficiency level, the contender story may have a basis. If they return close to the league average, the "storm" label will quickly be replaced by another. The real test is not whether they can win when they shoot hot. The real test is whether they can win on a night when the shots do not fall.

The third signal is Wilbekin's milestone. If he passes Navarro to stand alone in third place on the all-time three-point list, that will be a story independent of the game's result, a story about the durability of a shooter in a punishing competition. And if he truly plays for Besiktas — something I still need to verify — then the story of a newcomer signing a legend racing against history will carry a media pull far beyond a regular-season win.

Finally, I want to return to an idea I have pursued for years. A giant does not collapse because it is weak, but because it forgets it was once small. Maccabi did not collapse in this game because they lacked talent. They collapsed because their defence lost the synchronisation and discipline they themselves built over decades to become a giant. Besiktas, a hungry newcomer, exploited exactly that gap.

And that leaves a question I want each of us to answer: when a giant falls, should we look at the one who just won, or the one who just fell? I choose to look at the one who fell, because the real lesson of basketball is not found in brilliant victories, but in the moments when an empire forgets it once began from zero. That is where I find gold, and that is where anyone patient enough to read the data can find it too.