Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|
| Date | Match | Score | Res |
|---|---|---|---|
| 15.08.2026 | Solihull Moors - Boston United | 0 - 2 | L |
| 08.08.2026 | Harrogate Town - Solihull Moors | 5 - 2 | L |
| 01.08.2026 | Solihull Moors - Northampton | 2 - 4 | L |
| 28.07.2026 | Solihull Moors - Burton Albion | 1 - 1 | D |
| 25.07.2026 | Hereford - Solihull Moors | 0 - 3 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 11.08.2026 | Hartlepool - Middlesbrough U21 | 0 - 10 | W |
| 25.04.2026 | Chelsea U21 - Middlesbrough U21 | 1 - 0 | L |
| 10.04.2026 | Aston Villa U21 - Middlesbrough U21 | 0 - 2 | W |
| 20.03.2026 | Derby County U21 - Middlesbrough U21 | 1 - 0 | L |
| 13.03.2026 | Middlesbrough U21 - Stoke City U21 | 6 - 1 | W |
The upcoming match between Solihull Moors and Middlesbrough U21 is scheduled for 18.08.2026 18:00 in National League Cup. 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.
Solihull Moors recorded 3 wins, 2 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLLDWWLDWL. The averages are 1.50 goals scored and 2.10 goals conceded per match. Both teams scored in 60% of those matches, while 70% finished with over 2.5 goals. Middlesbrough U21 recorded 5 wins, 1 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLWLWWLLWD. The averages are 2.50 goals scored and 1.10 goals conceded per match. Both teams scored in 50% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 80%; Over 0.5 first-half goals — 70%; Over 2.5 goals — 60%; Under 3.5 goals — 60%; Both teams to score — 50%. They are statistical indicators and are not automatically converted into a prediction.
1 active football Premium signals are stored for this fixture. At least one goal in the match (quota 17, score 81/100, 81.48% group success rate across 1901 observations).
The discipline profile for Middlesbrough U21 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 1 of 1 completed matches (100.0% coverage).
The match between Solihull Moors and Middlesbrough U21 ended 1-3. The game produced 4 goals in total. The first half contained 3 goals. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
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 60%. 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 60%. 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 70%. The actual outcome was Over 0.5 HT. The stored trend was confirmed by the result.
Before kickoff, the discipline profile for Middlesbrough U21 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, Middlesbrough U21 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 17. The actual market outcome was At least one FT goal. The Premium signal was confirmed.
Of 5 verifiable pre-match indicators, 4 aligned with the final result and 1 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.