Saka out of Everton clash with thigh injury: Arsenal's right-flank problem across three games in six days

In the tenth minute in Munich, Bukayo Saka sat down in the middle of the white circle of grass. He did not roll, he did not hammer the turf. He sat with both hands behind him, eyes toward the touchline, as if calculating how many more steps were left in him. Then he stood, walked a few metres, and everyone in the stadium understood that his night had ended there. The next day, Mikel Arteta stood in front of the cameras and described that thigh in the language no manager chooses when things are comfortable: his player was struggling even to walk off the pitch, and signs like that are not good. Arsenal will be without Saka when they host Everton in the Premier League on Saturday. Nobody has given a number of weeks, least of all the man who said the most. The report carries the date 23 October and lists Saka as 25; it carries no scan result, because at the moment Arteta spoke no scan result existed. That is the entire factual base I have. I record this before writing anything else, because my working habit is to separate the verified from the narrated. In a week when every social media account already has a diagnosis, I have one sentence from a manager and one piece of date arithmetic. The match Saka left was Arsenal's 2-2 draw away at Bayern Munich in the Champions League. Three days later comes Everton, at home. Three days after that comes Fleetwood Town, a fourth-tier English club, in the fourth round of the League Cup. Three matches in six days, across three competitions, with a long European trip wedged in the middle. I checked the arithmetic three times: Wednesday, Saturday, Tuesday. There is nowhere to misread it. Arteta used that injury to talk about something larger than the injury. He called on governing bodies to give greater consideration to player load, and spoke of the need to support “the amount being put into these players”. A manager facing the press after a big European draw usually has two options: talk tactics, or talk calendar. He chose the second, and chose his moment. A concrete injury, visible, painful, is stronger evidence than any formal submission. But I have to state my limits. The only source here is the club's own press conference. There is no medical statement, no scan, no independent second source. And there is not a single performance metric: no xG, no xA, no PPDA, no minutes. Which means that if I write “Saka is worth X goals”, I am inventing. Data never lies; only the way we read it lies. Here I have no data, so I have structure and calendar — the two things that can be checked. And the structure points at exactly one place. Everton at Arsenal's home is the kind of opponent one imagines sitting deep, compact, ceding ground and sealing the middle. Against a block like that, Arsenal's main unlocking mechanism lives on the right: get the ball wide, isolate the opposing full-back in a one-versus-one, win the duel, and only then discuss the shot. What is lost is not a goal per game. What is lost is the primary tool of an entire attacking channel, in precisely the kind of match where that channel matters most. Saka is a left-footed player operating on the right. The difference is that he can beat a man in a space as tight as a phone box and still keep the ball. A replacement in the same position, if right-footed, turns the action from “go past the man on the outside” into “cut inside into traffic”. In terms of control, the team loses almost nothing. In terms of penetration, it loses a level. Tactics are only the way we legitimise our mistakes in football language — but in this case they are also the way we see where we are weak. There is a second channel the report never mentions, and I have to label it as inference. Saka is the type of player who carries a heavy dead-ball load at Arsenal: free kicks, corners, deliveries from both flanks. A thigh injury that makes walking difficult will also compromise striking a stationary ball. I have no data for his set-piece volume this season. I have one fact: a thigh problem, and difficulty moving. The rest is reasoning from role, not from the text. What is more certain is rotation. Three matches in six days is not a tactical choice, it is a constraint. The Everton XI and the Fleetwood XI will differ substantially regardless of Saka's fitness. The Fleetwood tie, against fourth-tier opposition in the League Cup, is the rational place to dump load. That protects the Saturday selection while exposing the squad-depth question. A squad deep enough makes rotation an art. A squad that is not makes rotation a gamble. The report names no replacement, so I name none. There are only two structural scenarios, and both are trade-offs. Scenario one: a right-footed winger shifted to the right, preserving width but losing the ability to beat a man on the outside, with attacks drifting into a crowded centre. Scenario two: a midfielder drifting wide, improving ball retention and rhythm but losing presence in the box. Both are a downgrade in penetration, and possibly no downgrade at all in control. Against a deep block, control without penetration is a closed loop. The more interesting geometric consequence: Arsenal's right flank is a single point of dependency in build-up, not merely in finishing. When that point disappears, the team tends to overload the left and progress more centrally. That is a shape change disguised as a personnel change. The Everton match therefore has a good chance of becoming a grind rather than a flow: slower tempo, more crosses, more second balls, more reliance on set pieces. When the pitch goes quiet, I see what a full stand never shows me: the bare truth. At a deeper level, this is a story about inventory, not about rules. More matches were created to generate more product for broadcasters, but nobody created more minutes in a player's legs. The cost of injury lands on the club; the revenue from the extra fixtures lands on the competitions and the broadcasters. The existing compensation mechanism was designed for a different scenario: players released to national teams. An injury sustained in a European club fixture stays with the employer. That is exactly what Arteta means by “the amount being put into these players”. There is a paradox worth recording: Arsenal are creating the congestion they are complaining about. Progressing to the fourth round of the League Cup means adding a midweek fixture to an already dense block. Success has a cost, and the cost is paid in minutes. Any club that goes far in every competition absorbs more high-intensity minutes than its direct rivals, the ones eliminated early. There is no villain here. Only a system that rewards winning and offers no discount for winning. I still remember why I trust this kind of analysis. In 2026, aged 19, I wrote a blog post that got 12 reads and nothing but scorn, arguing Liverpool should not buy a right-back because they already had an 18-year-old. By the end of that season he had 19 assists. In 2026 I published a comparison of two England goalkeepers' pass-completion rates and received more than 400 mocking comments. I did not argue. I went back to the footage. The lesson was not “I was right”; it was that a contrarian take needs a data foundation. People call it a curse. I call it a sentence written by hurried hands. From my own experience watching matches, there is something I have learned about how managers speak before scan results exist. A man willing to describe severity in words before imaging usually already suspects a significant injury. But there is another reading, and I must admit it may be the truer one: expectation management. Say in advance that it may be bad, so that when bad news arrives the shock is smaller, and so that the question “why wasn't he protected?” never quite forms. Where I may be wrong, I say plainly. I am assuming Everton will sit deep and compact, while my only source says nothing at all about Everton. I am applying a model to a team I have no data on, which is the exact error I keep warning myself against. It is also possible Saka misses two weeks and this entire analysis is a building erected on a minor niggle. And there is a further possibility, uncomfortable but worth stating: losing Saka may force Arsenal to diversify, reduce single-point dependency, and become less predictable within a few weeks. I have no xG to refute that. I have structure, and structure says that in the short term, losing a specialist in exactly the kind of match that demands specialism is a real loss. There is another risk few name: the Fleetwood game. With a rotated side, it is a low-reward, high-embarrassment fixture. If the result goes wrong, it will be used as evidence in the wider “squad too thin” narrative, and that narrative will attach itself to Saka in a way he does not deserve. So here is my checkable judgement. If Arsenal beat Everton comfortably, with the same tempo and the same attacking structure as with Saka, my structural-dependency argument weakens, and I will record that as a data update. If Arsenal win but do so through crosses, set pieces and second balls, the argument stands, whatever the scoreline. If Arsenal drop points, the question worth asking is not “who replaces Saka” but why a club at that level let one channel depend on one man across three games in six days. I do not write to persuade you. I write so that those who have seen what I have seen stop thinking they are mad.