Match context

The upcoming match between Pobeda Nizhniy Novgorod and Khimik Dzerzhinsk is scheduled for 13.09.2026 13:00 in Second League - Group 4. The analysis uses only stored statistics, form, head-to-head records, trend percentages and active Premium market signals. It does not guarantee a particular result.

Standings and season form
Pobeda Nizhniy Novgorod are in position 3 with 43 points after 22 matches. The season record is 13 wins, 4 draws and 5 losses. The goals record is 51 scored and 33 conceded. The stored form sequence is WWDLL. Khimik Dzerzhinsk are in position 1 with 56 points after 22 matches. The season record is 18 wins, 2 draws and 2 losses. The goals record is 57 scored and 16 conceded. The stored form sequence is WWLWW.

Recent results

Pobeda Nizhniy Novgorod recorded 4 wins, 3 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWDLLLDWWD. The averages are 1.70 goals scored and 1.90 goals conceded per match. Both teams scored in 70% of those matches, while 50% finished with over 2.5 goals. Khimik Dzerzhinsk recorded 7 wins, 1 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWLWLWWWWD. The averages are 2.40 goals scored and 0.80 goals conceded per match. Both teams scored in 50% of those matches, while 70% finished with over 2.5 goals.

Head-to-head

Across the last 2 head-to-head matches, Pobeda Nizhniy Novgorod recorded 0 wins, there were 1 draws, and Khimik Dzerzhinsk recorded 1 wins. The average total was 2 goals per match. Both teams scored in 50% of those matches, while 0% finished with over 2.5 goals.

Trend indicators

The highest stored values are: Over 0.5 first-half goals — 80%; Over 1.5 goals — 80%; Over 2.5 goals — 70%; Both teams to score — 60%; Under 3.5 goals — 60%. They are statistical indicators and are not automatically converted into a prediction.

Discipline profile

The discipline profile for Khimik Dzerzhinsk away from home is based on 1 matches. The team averages 0.00 yellow cards, 1.00 red cards and 1.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 0.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 100.0%. Season card data is available for 2 of 24 completed matches (8.3% coverage).

What happened in the match

The match between Pobeda Nizhniy Novgorod and Khimik Dzerzhinsk ended 0-1. The game produced 1 goal in total. The first half contained 1 goal. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.

Which pre-match trends were confirmed and which were not

Before kickoff, the stored trend indicated BTTS at 60%. The actual outcome was No BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 80%. The actual outcome was Under 1.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 2.5 at 70%. The actual outcome was Under 2.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 60%. The actual outcome was Under 3.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 80%. The actual outcome was Over 0.5 HT. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 1.5 HT at 70%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.

Discipline profile review

Before kickoff, the discipline profile for Khimik Dzerzhinsk away from home was based on 1 matches, with averages of 0 yellow cards, 1 red cards and 1 total cards per match. In this game, Khimik Dzerzhinsk received 1 yellow cards and 1 red cards, 2 in total. That was 1 cards above the stored average. In the pre-match sample, 3+ cards occurred in 0% of matches, 5+ in 0%, and a red card in 100%.

Summary

Of 6 verifiable pre-match indicators, 3 aligned with the final result and 3 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.