Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 12.02.2022 | Norwich - Manchester City | 0 : 4 |
| 21.08.2021 | Manchester City - Norwich | 5 : 0 |
| 26.07.2020 | Manchester City - Norwich | 5 : 0 |
| 14.09.2019 | Norwich - Manchester City | 3 : 2 |
| 12.03.2016 | Norwich - Manchester City | 0 : 0 |
| 09.01.2016 | Norwich - Manchester City | 0 : 3 |
| 31.10.2015 | Manchester City - Norwich | 2 : 1 |
| 08.02.2014 | Norwich - Manchester City | 0 : 0 |
| 02.11.2013 | Manchester City - Norwich | 7 : 0 |
| 19.05.2013 | Manchester City - Norwich | 2 : 3 |
| Date | Match | Score | Res |
|---|---|---|---|
| 07.11.2026 | Nottingham Forest - Manchester City | 3 - 1 | L |
| 04.11.2026 | RB Leipzig - Manchester City | 2 - 3 | W |
| 31.10.2026 | Manchester City - Brighton | 0 - 1 | L |
| 28.10.2026 | Manchester City - Brighton | 2 - 2 | D |
| 24.10.2026 | Aston Villa - Manchester City | 2 - 1 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 07.11.2026 | Bristol City - Norwich | 0 - 5 | W |
| 03.11.2026 | Derby - Norwich | 0 - 4 | W |
| 31.10.2026 | Norwich - Watford | 3 - 2 | W |
| 24.10.2026 | Charlton - Norwich | 1 - 3 | W |
| 17.10.2026 | Norwich - Portsmouth | 0 - 1 | L |
The upcoming match between Manchester City and Norwich is scheduled for 17.09.2026 18:30 in League Cup. The listed venue is Etihad Stadium, Manchester. 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.
Manchester City recorded 7 wins, 1 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWWWWLWWDL. The averages are 1.80 goals scored and 1 goals conceded per match. Both teams scored in 60% of those matches, while 60% finished with over 2.5 goals. Norwich recorded 5 wins, 1 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is LWWLWWLLWD. The averages are 1.90 goals scored and 1.50 goals conceded per match. Both teams scored in 70% of those matches, while 80% finished with over 2.5 goals.
Across the last 10 head-to-head matches, Manchester City recorded 6 wins, there were 2 draws, and Norwich recorded 2 wins. The average total was 3.70 goals per match. Both teams scored in 30% of those matches, while 80% finished with over 2.5 goals.
The highest stored values are: Over 0.5 first-half goals — 90%; Over 1.5 goals — 80%; Over 2.5 goals — 70%; Under 3.5 goals — 70%; Both teams to score — 60%. They are statistical indicators and are not automatically converted into a prediction.
The PMV3 model classifies the leading outcome as Manchester City to win with 84% confidence. The stored fair probabilities for home, draw and away are 84.01%, 10.45% and 5.53%. The model momentum difference is 78.48 points in favour of Manchester City. The input data quality score is 100/100. The stored price for the selected market is 1.12 with Bet365. The stored estimated EV is -5.91%. Despite the model probability, the price is marked NO_VALUE. The signal is therefore not treated automatically as a value bet.
1 active football Premium signals are stored for this fixture. At least one goal in the match (quota 29, score 83/100, 83.11% group success rate across 521 observations).
The discipline profile for Norwich away from home is based on 1 matches. The team averages 1.00 yellow cards, 0.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 0.0%. Season card data is available for 2 of 2 completed matches (100.0% coverage).
The match between Manchester City and Norwich ended 5-0. The game produced 5 goals in total. The first half contained 2 goals. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
The previous 10 head-to-head meetings averaged 3.7 goals, while this match produced 5. The final scoring profile differed by more than one goal from that average. Across the previous 10 head-to-head meetings, the leading historical direction was No BTTS at 70%. The actual outcome for this indicator was No BTTS. The final result aligned with that historical profile. Across the previous 10 head-to-head meetings, the leading historical direction was Over 2.5 at 80%. The actual outcome for this indicator was Over 2.5. The final result aligned with that historical profile.
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 Over 1.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 2.5 at 70%. The actual outcome was Over 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 70%. The actual outcome was Over 3.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 90%. 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 60%. The actual outcome was Over 1.5 HT. The stored trend was not confirmed by the result.
Before kickoff, the discipline profile for Norwich away from home was based on 1 matches, with averages of 1 yellow cards, 0 red cards and 1 total cards per match. In this game, Norwich received 1 yellow cards and 0 red cards, 1 in total. The total was effectively equal to the stored average. In the pre-match sample, 3+ cards occurred in 0% of matches, 5+ in 0%, and a red card in 0%.
The stored Premium market was At least one FT goal with quota 29. The actual market outcome was At least one FT goal. The Premium signal was confirmed.
Of 10 verifiable pre-match indicators, 6 aligned with the final result and 4 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.