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 |
|---|---|---|---|
| 29.08.2026 | Hallam - Mossley | 4 - 3 | W |
| 14.07.2026 | Hallam - Sheffield Wednesday | 0 - 0 | D |
| 25.04.2026 | Heaton Stannington - Hallam | 0 - 1 | W |
| 18.04.2026 | Hallam - Dunston UTS | 0 - 1 | L |
| 11.04.2026 | Hallam - Silsden | 0 - 2 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 29.08.2026 | Hallam - Mossley | 4 - 3 | L |
| 11.07.2026 | Mossley - Radcliffe | 1 - 0 | W |
| 25.04.2026 | Bootle - Mossley | 2 - 0 | L |
| 18.04.2026 | Mossley - Vauxhall Motors | 3 - 2 | W |
| 11.04.2026 | Mossley - Darlaston Town | 1 - 0 | W |
The upcoming match between Hallam and Mossley is scheduled for 29.08.2026 14:00 in FA Trophy. 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.
Hallam recorded 3 wins, 3 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is DWLLLWLWDD. The averages are 0.40 goals scored and 0.60 goals conceded per match. Both teams scored in 10% of those matches, while 0% finished with over 2.5 goals. Mossley recorded 5 wins, 3 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLWWLDDWWD. The averages are 1.10 goals scored and 0.90 goals conceded per match. Both teams scored in 40% of those matches, while 20% finished with over 2.5 goals.
The highest stored values are: Under 2.5 goals — 80%; Under 3.5 goals — 80%; Over 0.5 first-half goals — 40%; Over 1.5 goals — 40%; Both teams to score — 20%. They are statistical indicators and are not automatically converted into a prediction.
The match between Hallam and Mossley ended 3-3. The game produced 6 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 No BTTS at 80%. The actual outcome was BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 80%. The actual outcome was Over 2.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 80%. The actual outcome was Over 3.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 0.5 HT at 60%. The actual outcome was Over 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 Over 1.5 HT. The stored trend was not confirmed by the result.
Of 5 verifiable pre-match indicators, 0 aligned with the final result and 5 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.