Match context

The upcoming match between Salisbury and Hampton & Richmond is scheduled for 08.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.

Recent results

Salisbury recorded 4 wins, 1 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLWLWDWLLL. The averages are 2.40 goals scored and 1.60 goals conceded per match. Both teams scored in 70% of those matches, while 90% finished with over 2.5 goals. Hampton & Richmond recorded 5 wins, 1 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWLDLWLWLW. The averages are 1.30 goals scored and 1.40 goals conceded per match. Both teams scored in 50% of those matches, while 50% finished with over 2.5 goals.

Head-to-head

Across the last 5 head-to-head matches, Salisbury recorded 1 wins, there were 2 draws, and Hampton & Richmond recorded 2 wins. The average total was 1.60 goals per match. Both teams scored in 40% of those matches, while 20% finished with over 2.5 goals.

Trend indicators

The highest stored values are: Over 0.5 first-half goals — 80%; Over 1.5 goals — 80%; Over 2.5 goals — 60%; Over 3.5 goals — 50%; Under 3.5 goals — 50%. They are statistical indicators and are not automatically converted into a prediction.

Asian handicap market movement

The normalized movement for the Asian pair Salisbury -1 / Hampton & Richmond +1 supports Hampton & Richmond by an average 2.24 percentage points across 2 bookmakers (Bet365, 1xBet) with up to 3 stored observations. This is a market signal, not a result guarantee.

Premium market signals

1 active football Premium signals are stored for this fixture. Goals Over/Under — Under 2.5 (odds 1.90).

What happened in the match

The match between Salisbury and Hampton & Richmond ended 5-0. The game produced 5 goals in total. The first half contained 1 goal. The following review compares the final result only with historical data, trend values and Premium signals locked before kickoff.

Comparison with the head-to-head history

The previous 5 head-to-head meetings averaged 1.6 goals, while this match produced 5. The final scoring profile differed by more than one goal from that average. Across the previous 5 head-to-head meetings, the leading historical direction was No BTTS at 60%. The actual outcome for this indicator was No BTTS. The final result aligned with that historical profile. Across the previous 5 head-to-head meetings, the leading historical direction was Under 2.5 at 80%. The actual outcome for this indicator was Over 2.5. The final result did not align with that historical profile.

Which pre-match trends were confirmed and which were not

Before kickoff, the stored trend indicated No BTTS at 60%. The actual outcome was No BTTS. The stored trend was confirmed by the result. 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 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 60%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.

Asian handicap review

The Asian-handicap signal locked before kickoff supported Hampton & Richmond at +1. The stored market movement was 2.24 percentage points across 2 bookmakers. At the final score of 5-0, the line settled as a full loss. The Asian-handicap signal was not confirmed.

Premium market review

The stored Premium market was Under 2.5 at odds of 1.9. The actual market outcome was Over 2.5. The Premium signal was not confirmed.

Summary

Of 10 verifiable pre-match indicators, 6 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.