Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 15.11.2025 | Horsham - Farnham Town | 2 : 0 |
| Date | Match | Score | Res |
|---|---|---|---|
| 22.08.2026 | Braintree - Horsham | 1 - 2 | W |
| 18.08.2026 | Horsham - Hampton & Richmond | 2 - 0 | W |
| 15.08.2026 | Horsham - Salisbury | 0 - 0 | D |
| 08.08.2026 | Torquay - Horsham | 1 - 1 | D |
| 01.08.2026 | Worthing - Horsham | 3 - 0 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 22.08.2026 | Farnham Town - Billericay Town | 2 - 4 | L |
| 18.08.2026 | Slough Town - Farnham Town | 0 - 1 | W |
| 14.08.2026 | Dagenham & Redbridge - Farnham Town | 2 - 1 | L |
| 08.08.2026 | Farnham Town - AFC Totton | 0 - 1 | L |
| 01.08.2026 | Farnham Town - Eastleigh | 1 - 0 | W |
The upcoming match between Horsham and Farnham Town is scheduled for 29.08.2026 14:00 in National League - South. 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
Horsham are in position 2 with 8 points. The stored form sequence is WWDD. Farnham Town are in position 19 with 3 points. The stored form sequence is LWLL.
Horsham recorded 4 wins, 2 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWDDLLLWWL. The averages are 1.20 goals scored and 1.60 goals conceded per match. Both teams scored in 50% of those matches, while 60% finished with over 2.5 goals. Farnham Town recorded 5 wins, 2 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is LWLLWDDWWW. The averages are 1.50 goals scored and 1.20 goals conceded per match. Both teams scored in 60% of those matches, while 60% finished with over 2.5 goals.
Across the last 1 head-to-head matches, Horsham recorded 1 wins, there were 0 draws, and Farnham Town recorded 0 wins. The average total was 2 goals per match. Both teams scored in 0% of those matches, while 0% finished with over 2.5 goals.
The highest stored values are: Under 3.5 goals — 90%; Over 0.5 first-half goals — 80%; Over 1.5 goals — 60%; Under 2.5 goals — 60%; Both teams to score — 40%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Horsham 0 / Farnham Town 0 supports Horsham by an average 3.98 percentage points across 3 bookmakers (Pinnacle, Bet365, 1xBet) with up to 2 stored observations. This is a market signal, not a result guarantee.
The match between Horsham and Farnham Town ended 1-2. The game produced 3 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 60%. The actual outcome was BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 60%. The actual outcome was Over 1.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 60%. 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 90%. The actual outcome was Under 3.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 80%. 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 90%. 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 Horsham at 0. The stored market movement was 3.98 percentage points across 3 bookmakers. At the final score of 1-2, the line settled as a full loss. The Asian-handicap signal was not confirmed.
Of 7 verifiable pre-match indicators, 3 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.