Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 01.02.2017 | Manchester United - Hull City | 0 : 0 |
| 26.01.2017 | Hull City - Manchester United | 2 : 1 |
| 10.01.2017 | Manchester United - Hull City | 2 : 0 |
| 27.08.2016 | Hull City - Manchester United | 0 : 1 |
| 24.05.2015 | Hull City - Manchester United | 0 : 0 |
| 29.11.2014 | Manchester United - Hull City | 3 : 0 |
| 06.05.2014 | Manchester United - Hull City | 3 : 1 |
| 26.12.2013 | Hull City - Manchester United | 2 : 3 |
| Date | Match | Score | Res |
|---|---|---|---|
| 15.08.2026 | Hull City - Nice | 0 - 0 | D |
| 08.08.2026 | Eintracht Frankfurt - Hull City | 2 - 0 | L |
| 01.08.2026 | Kasımpaşa - Hull City | 1 - 1 | D |
| 28.07.2026 | Rizespor - Hull City | 1 - 2 | W |
| 25.07.2026 | Konyaspor - Hull City | 0 - 3 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 15.08.2026 | Manchester United - AC Milan | 2 - 4 | L |
| 12.08.2026 | Leeds - Manchester United | 0 - 0 | D |
| 08.08.2026 | Manchester United - Paris Saint Germain | 1 - 1 | D |
| 01.08.2026 | Manchester United - Atletico Madrid | 2 - 1 | W |
| 24.07.2026 | Rosenborg - Manchester United | 0 - 5 | W |
The upcoming match between Hull City and Manchester United is scheduled for 22.08.2026 11:30 in Premier League. 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.
Hull City recorded 5 wins, 3 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is DLDWWWWDWL. The averages are 1.20 goals scored and 0.70 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals. Manchester United recorded 6 wins, 2 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is LDWWLWWDWW. The averages are 2.10 goals scored and 1.20 goals conceded per match. Both teams scored in 60% of those matches, while 70% finished with over 2.5 goals.
Across the last 8 head-to-head matches, Hull City recorded 1 wins, there were 2 draws, and Manchester United recorded 5 wins. The average total was 2.25 goals per match. Both teams scored in 37.5% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 80%; Under 3.5 goals — 80%; Over 0.5 first-half goals — 60%; Both teams to score — 50%; Over 2.5 goals — 50%. The stored corner indicators are: average total corners — 8.33; over 7.5 corners — 100%; over 8.5 corners — 98%; over 9.5 corners — 88%. They are statistical indicators and are not automatically converted into a prediction.
The PMV3 model classifies the leading outcome as Manchester United to win with 71% confidence. The stored fair probabilities for home, draw and away are 9.51%, 19.01% and 71.48%. The model momentum difference is 61.97 points in favour of Manchester United. The input data quality score is 100/100. The stored price for the selected market is 1.33 with Bet365. The stored estimated EV is -4.93%. Despite the model probability, the price is marked NO_VALUE. The signal is therefore not treated automatically as a value bet.
The normalized movement for the Asian pair Hull City 0 / Manchester United 0 supports Manchester United by an average 2.32 percentage points across 2 bookmakers (Bet365, 1xBet) with up to 8 stored observations. This is a market signal, not a result guarantee.
1 active football Premium signals are stored for this fixture. Goals Over/Under — Over 1.5 (odds 1.20, score 77/100, 77.31% bucket win rate across 454 observations).
The match between Hull City and Manchester United ended 2-0. The game produced 2 goals in total. The first half contained 2 goals. The verified final statistics recorded 5 corners in total. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
The historical profile from 8 head-to-head meetings averaged 2.25 goals, while this match produced 2. The result remained within one goal of the historical average. Across the previous 8 head-to-head meetings, the leading historical direction was No BTTS at 62.5%. The actual outcome for this indicator was No BTTS. The final result aligned with that historical profile.
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 Under 3.5 at 80%. The actual outcome was Under 3.5. The stored trend was confirmed by the result. The stored pre-match average was 8.33 total corners. The match recorded 5 corners in total. The result differed by more than one corner from the stored average. Before kickoff, the stored trend indicated Over 7.5 corners at 100%. The actual outcome was Under 7.5 corners. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 8.5 corners at 98%. The actual outcome was Under 8.5 corners. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 9.5 corners at 88%. The actual outcome was Under 9.5 corners. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 60%. 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 80%. The actual outcome was Over 1.5 HT. The stored trend was not confirmed by the result.
The Asian-handicap signal locked before kickoff supported Manchester United at 0. The stored market movement was 2.32 percentage points across 2 bookmakers. At the final score of 2-0, the line settled as a full loss. The Asian-handicap signal was not confirmed.
The stored Premium market was Over 1.5 FT at odds of 1.2. The actual market outcome was Over 1.5 FT. The Premium signal was confirmed.
Of 12 verifiable pre-match indicators, 6 aligned with the final result and 6 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.