Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 19.08.2025 | Walsall - Grimsby | 0 : 1 |
| 08.03.2025 | Walsall - Grimsby | 1 : 3 |
| 19.10.2024 | Grimsby - Walsall | 1 : 4 |
| 01.01.2024 | Grimsby - Walsall | 1 : 6 |
| 26.08.2023 | Walsall - Grimsby | 1 : 1 |
| 25.03.2023 | Grimsby - Walsall | 1 : 1 |
| 27.08.2022 | Walsall - Grimsby | 1 : 2 |
| 27.03.2021 | Grimsby - Walsall | 1 : 1 |
| 12.09.2020 | Walsall - Grimsby | 1 : 0 |
| 31.08.2019 | Walsall - Grimsby | 1 : 3 |
| Date | Match | Score | Res |
|---|---|---|---|
| 15.08.2026 | Gillingham - Walsall | 0 - 3 | W |
| 06.08.2026 | Bristol City - Walsall | 0 - 1 | W |
| 01.08.2026 | Walsall - Notts County | 0 - 0 | D |
| 25.07.2026 | AFC Telford United - Walsall | 1 - 0 | L |
| 21.07.2026 | Walsall - Aston Villa | 0 - 5 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 15.08.2026 | Grimsby - Exeter City | 1 - 0 | W |
| 08.08.2026 | Grimsby - Blackpool | 1 - 3 | L |
| 04.08.2026 | Grimsby - Grimsby Borough | 3 - 2 | W |
| 01.08.2026 | Grimsby - Wigan | 2 - 0 | W |
| 29.07.2026 | Boston United - Grimsby | 0 - 0 | D |
The upcoming match between Walsall and Grimsby is scheduled for 22.08.2026 11:30 in League Two. 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
Walsall are in position 1 with 3 points. The stored form sequence is W. Grimsby are in position 9 with 3 points. The stored form sequence is W.
Walsall recorded 3 wins, 2 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWDLLDLLWL. The averages are 0.80 goals scored and 1.60 goals conceded per match. Both teams scored in 20% of those matches, while 50% finished with over 2.5 goals. Grimsby recorded 5 wins, 4 draws and 1 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLWWDWWDDD. The averages are 1.80 goals scored and 0.90 goals conceded per match. Both teams scored in 50% of those matches, while 50% finished with over 2.5 goals.
Across the last 10 head-to-head matches, Walsall recorded 3 wins, there were 3 draws, and Grimsby recorded 4 wins. The average total was 3.10 goals per match. Both teams scored in 80% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Under 3.5 goals — 70%; Over 0.5 first-half goals — 60%; Under 2.5 goals — 60%; Over 1.5 goals — 50%; Over 2.5 goals — 40%. The stored corner indicators are: average total corners — 10.10; over 7.5 corners — 100%; over 8.5 corners — 100%; over 9.5 corners — 100%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Walsall -1 / Grimsby +1 supports Grimsby by an average 2.61 percentage points across 3 bookmakers (Pinnacle, Bet365, 1xBet) with up to 13 stored observations. This is a market signal, not a result guarantee.
1 active football Premium signals are stored for this fixture. Odd/Even — Odd (odds 2).
The match between Walsall and Grimsby ended 0-0. The game produced 0 goals in total. The first half contained 0 goals. The verified final statistics recorded 2 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 previous 10 head-to-head meetings averaged 3.1 goals, while this match produced 0. 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 BTTS at 80%. The actual outcome for this indicator was No BTTS. The final result did not align with that historical profile.
Before kickoff, the stored trend indicated No BTTS at 80%. The actual outcome was No BTTS. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 60%. The actual outcome was Under 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 Under 3.5. The stored trend was confirmed by the result. The stored pre-match average was 10.1 total corners. The match recorded 2 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 100%. 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 100%. 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 Under 0.5 HT. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 1.5 HT at 80%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
The Asian-handicap signal locked before kickoff supported Grimsby at +1. The stored market movement was 2.61 percentage points across 3 bookmakers. At the final score of 0-0, the line settled as a full win. The Asian-handicap signal was confirmed.
The stored Premium market was Odd at odds of 2. The actual market outcome was Even. The Premium signal was not confirmed.
Of 13 verifiable pre-match indicators, 5 aligned with the final result and 8 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.