Crvena zvezda vs Partizan: reading two Belgrade derby records

The 174th derby: Ndiaye leads the scoring

Crvena zvezda's September 2024 away victory featured a hat-trick from Šerif Ndiaye and a goal from Silas. It was the 174th senior football derby in the club's report. The numbering helps identify this particular meeting, but the date and competition remain necessary because the clubs also meet in other sports and age groups.

The scoring pattern gives the game a clear centre: one forward converted three times while another player added the remaining goal. That is a stronger historical description than a vague claim of dominance without identifying what happened. It also creates useful questions for a replay. Did the goals arise from similar positions? Did the defensive response change after the first? The report establishes the scorers and result; any deeper tactical answer should be checked against the actual sequences rather than assumed from the size of the margin.

Two official records and two home settings

The club reports provide the results, dates and grounds for the selected matches. The first row places Partizan at home; the second places Crvena zvezda at home. That change must be respected when mapping goals to each club and when interpreting a venue comparison.

The table records the score after normal playing time. It does not combine results from the two grounds into a fictional knockout tie. Unlike a two-leg European tie, these league fixtures should remain individual observations with their own context. A sum of their goals is only a descriptive aggregate for this sample, not a qualification result or an official trophy outcome.

What the displayed scorelines establish

Crvena zvezda won both selected matches, scoring six goals and conceding one. It kept one clean sheet in the pair. Partizan did not keep a clean sheet in these rows. Those are straightforward calculations from the stated sample, and their limited denominator should remain visible wherever they are reused.

The two winning margins are different, which matters when describing the games. A single label such as “two victories” removes information about how close the score was. Keep both the result category and the actual goals. If the archive is expanded, calculate distributions and rates from all eligible rows rather than choosing only encounters that fit a narrative of dominance or recovery.

A first-half lead at Partizan’s ground

Ndiaye's opening goal came from a penalty, and Silas scored before halftime. Further Ndiaye goals after the interval completed the 0–4 result. The division across the halves matters because the away side already had a two-goal advantage before the second period began.

The later goals therefore expanded an established lead rather than creating a comeback. This gives the September game a different structure from the April meeting in the same selection. A reader can compare how a team plays when already ahead with how it responds when trailing. The penalty also needs its proper category: it was taken during the match and forms part of the playing score. It was not a shoot-out attempt. Keeping that distinction clear allows a straightforward comparison of normal match goals without introducing a separate tie-breaking contest that did not occur.

The 176th derby: Partizan lead until the closing phase

In April 2025, Aldo Kalulu put Partizan ahead before halftime at the Rajko Mitić stadium. Crvena zvezda's goals arrived late, through Andrija Maksimović and Bruno Duarte. The official report records a 0–1 halftime score followed by a 2–1 home victory.

This is not the same story as September's four-goal away win. For much of the April match, Partizan were the side protecting the advantage and Zvezda were the side seeking a reply. The final result does not erase that earlier position. Duarte's contribution after entering as a substitute also puts the bench into the account. A starting eleven alone cannot explain the eventual scorers. These details make the second game a comeback narrative, rather than another interchangeable example of a Zvezda victory in a small selected table.

Two late goals can overturn a long period of advantage

Maksimović equalised in the 84th minute and Duarte scored in the 87th. Those late events changed both the immediate result and the way the match would be remembered. Partizan's lead had lasted far longer than the final margin suggests, but the winner was determined by the score at the end.

For a football reader, the useful question is how the final phase was played, not whether the previous lead somehow ceased to exist. Review where the ball was recovered, which players occupied the area and how the defensive line reacted. Such observations can support a concrete account of the comeback. The timing alone cannot diagnose fatigue, panic or a permanent psychological weakness. The selected matches show two different successful routes for Zvezda: establishing a substantial lead away, and recovering late at home. Their mechanisms should remain separate even when the winner is the same.

Look up current fixtures and viewing arrangements separately

A numbered historical derby is not an announcement of the next match. Check the official competition and club fixture pages for the current date, kickoff and venue. If a schedule is provisional, preserve that status. For stadium access, use the organiser's current guidance rather than an old match report or a map attached to a different event.

Live television rights also depend on season, competition and viewing territory. Confirm the authorised broadcaster through official information and then check the programme for the actual fixture. A club highlights page is valuable historical evidence but does not establish a legal live stream for a later match. Separating that service lookup from the stable results table keeps this guide useful after schedules and distribution agreements change.

Keep the Belgrade archive reproducible

Use stable Latin-script identifiers internally even when an official source also appears in Cyrillic. Preserve the original display name in a separate field, so transliteration does not create two copies of the same club. Store the source URL, match date, competition and team level together.

Before publishing a new row, compare it against existing identifiers and confirm that it is not the same fixture in another language. Recalculate goals and clean sheets from the rows rather than editing summary numbers manually. This approach allows a multilingual archive to grow without multiplying matches, mixing sports or making an incomplete selection look like the entire history of the derby.

1. Confirm senior men’s football before importing a derby result.
2. Store the derby number separately from the unique match identifier.
3. Normalise Latin and Cyrillic name variants without duplicating teams.
4. Keep halftime, full-time and goal-timing fields separate.
5. Show the sample size beside home-away or clean-sheet statistics.
6. Use current official notices for the next fixture and stadium access.

Sources and verification

• 174. večiti derbi: match report — FK Crvena zvezda — 2026-10-23
• 176. večiti derbi: match report — FK Crvena zvezda — 2026-10-23