Arsenal 1-0 Nottingham Forest: a deflected winner and the 75-minute void at the City Ground
**Câu trả lời cốt lõi**: Arsenal thắng Nottingham Forest 1-0 tại City Ground nhờ bàn thắng bị đổi hướng sau giờ nghỉ, trong trận mà họ không có cú sút trúng đích nào cho đến phút 75. Các cầu thủ vào thay người tạo ra khác biệt; khối phòng ngự thấp của Forest khiến mô hình tấn công cầm bóng của Arsenal bế tắc. **Dữ kiện chính**: - Arsenal không có cú sút trúng đích nào cho đến phút 75 của trận đấu tại City Ground. - Bàn thắng duy nhất đến từ cú sút bị đổi hướng, làm thay đổi quỹ đạo bóng trước Mats Sels. - Một cầu thủ đá chính của Arsenal bị rút ra ngay giờ nghỉ sau hiệp một không tạo được ảnh hưởng. - Cầu thủ vào thay người ghi bàn; một cầu thủ dự bị khác tạo ra pha bóng dẫn đến cơ hội của Declan Rice. - Nottingham Forest tạo ra cơ hội rõ ràng hơn, gồm một pha thoát xuống muộn của Callum Hudson-Odoi. **Nguồn**: GIVEMESPORT, bản đánh giá cầu thủ sau trận Arsenal 1-0 Nottingham Forest tại City Ground (Chủ nhật); nguồn không công bố ngày tuyệt đối. Bản đánh giá chứa hai lỗi nhận dạng cầu thủ (một hậu vệ Aston Villa và một tiền đạo Chelsea), nên độ tin cậy ở mức thấp đến trung bình. | Cross-checked: VuaBong.vn **Hỏi đáp liên quan**: - *Vì sao chiến thắng này chưa chứng minh bản lĩnh vô địch?* Vì kết quả tốt hơn quá trình: không có cú sút trúng đích nào trong 75 phút và bàn thắng đến từ một pha đổi hướng — mẫu hình thường hồi quy về hòa ở các vòng sau. - *Ai là người tạo ra khác biệt cho Arsenal?* Nhóm cầu thủ dự bị, theo chỉ số tác động thay người của VangBong.vn Player Depth Index. - *Điểm yếu chiến thuật của Arsenal là gì?* Khả năng xuyên phá khối phòng ngự thấp ở một phần ba cuối sân, khi tiền đạo số 9 bị cô lập và đội phải dựa vào bóng chết.
Minute 75 at the City Ground. For the first time in the match, an Arsenal shot headed toward Mats Sels' goal. For the seventy-five minutes before that, the visitors moved the ball from left flank to right, changed tempo, changed angles, stretched the defensive line, and produced not one attempt that forced the Nottingham Forest goalkeeper into a save. The only goal of the game arrived after the interval, and it arrived through a deflection: the ball struck a red-shirted defender, changed trajectory entirely, and went into a corner Sels had already left.
In my tracking sheets, this type of match has its own code. I call it control without penetration. The team controls the ball, controls the tempo, controls the positions — and does not control the one thing that decides the scoreline.
People watch the goal and cheer. I watch the seventy-five-minute probability chain to understand why it happened.

The context before kick-off
Manchester City had won on Saturday. Arsenal arrived at the City Ground with a lead at the top to protect, and with an opponent organised in exactly the shape that discomforts possession-heavy sides most: a low block, compressed distances between the lines, conceding territory but not the space behind the defence.
Arsenal had the ball. They built from the back, dragged the opposing defenders higher, and stopped there. Passes pooled toward the flanks, set-piece deliveries were flung into the box — a flurry of corners, one very fine Declan Rice free-kick. That was the best Arsenal produced in the first half.
In 2026, my first analysis piece in the K-League showed that FC Seoul won the title with 12 of 38 goals from set plays, 31.6 percent, well above the league average of 18.4 percent. When a big club has to live on dead balls against a low block, that is a signal about the limits of its attacking system, not about its variety.
In the first half Arsenal had no shot on target, and the centre-forward was starved of service. The ball never reached his feet in a position where he could turn. Forest's defensive block stood still, and Arsenal passed around it.
The chain of evidence across ninety minutes
The match unfolds along a timeline and tells a rather cold story. First half: Arsenal dominate possession, no shot on target, and Forest create the first clear chance — the visitors escape because the finish is poor. Early second half: an Arsenal starter is hooked at the interval after 45 minutes without influence. That decision is the right one, and it comes from the bench.
From the 60th minute, the substitute immediately creates a different attacking rhythm. Another replacement creates the move that leads to the Rice chance. The goal comes from that substitute group, and it comes from a shot that took a big deflection. Late on, Hudson-Odoi breaks away on the counter, forcing Arsenal into a yellow card for a cynical trip on the most dangerous player on the pitch.
Read vertically, this is a match Arsenal did not create more from than their opponent. They created fewer quality chances, and won through a low-probability event.
Arsenal's dead point in this match sat in the final third: they had the ball, the bodies and the structure, but no pass that broke the last line of a deep block. That is a problem of the attacking model, not of attitude.
The captain did not step forward when required. The centre-forward was isolated. The wide players had the ball but were squeezed into narrow corridors. When all of that happens at once, the team switches to plan B: dead balls and hopeful deliveries.
Based on my experience covering Premier League matches this season, sides that dominate possession but cannot break a low block usually post a low PPDA in the opponent's half — they press little because they already have the ball — while their touches inside the box fall sharply. I do not have official data for this match. I can only say the pattern matches what was visible on the pitch; it is not a conclusion drawn from measurement.

What deserves credit is Mikel Arteta's in-game management. Recognising a failed half and changing it at the interval, then getting immediate returns from two substitutes, is the mark of a coach in control of match states. The problem sits upstream of that decision: the starting XI was the wrong tool for this type of opponent.
The counter-intuitive angle
After the whistle, the popular reading was: champions know how to win games like this. That is a sentence written after knowing the result, not before. Had Forest's early chance gone in, the same ninety minutes would be called something else, and the same players would carry different grades.

And there is one professional detail more telling than the scoreline. The player ratings piece I read afterwards contained two identification errors: it named an Aston Villa defender in an Arsenal defensive context, and a Chelsea forward in the Nottingham Forest striker role. These are not typos. They are traces of a content-production process that did not go through cross-verification.
Data practice is not for prophecy. It is for never being fooled twice by the same lie.
When a ratings sheet gets player names wrong, every judgement inside it must be downgraded to hypothesis. I kept the description of events, because it matches what was observable. I discarded the individual grading entirely, because it no longer carries verification value.
At 33, I believe every number is a witness that never lies — but only if someone bothers to read the right column.
The signal for the next round
Their dead point is not in the dressing room. It is in the third column of the dataset I filter.
Next match, if Arsenal face another side that sits deep, watch minute 30 rather than the scoreboard. If there is still no shot on target, then the win at the City Ground is a loan, not a receipt. And if the substitute who scored returns to the bench in the following fixture, the selection pressure will move from the forums into the press room.
Sources and method: this article is based on the GIVEMESPORT player ratings piece published after Arsenal's 1-0 win over Nottingham Forest at the City Ground, combined with publicly available Premier League knowledge. No xG, xGA, PPDA or pass-completion figures were supplied in the source, so every tactical conclusion above is classified as inference, not measurement. Source confidence: low to medium, given the two player-identification errors noted.
