Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 10.07.2023 | Yate Town - Chippenham Town | 0 : 1 |
| 14.09.2013 | Yate Town - Chippenham Town | 3 : 2 |
| Date | Match | Score | Res |
|---|---|---|---|
| 08.08.2026 | Uxbridge - Chippenham Town | 2 - 0 | L |
| 14.07.2026 | Swindon Town - Chippenham Town | 0 - 1 | W |
| 10.07.2026 | Paulton Rovers - Chippenham Town | 1 - 2 | W |
| 25.04.2026 | Horsham - Chippenham Town | 3 - 2 | L |
| 18.04.2026 | Chippenham Town - AFC Hornchurch | 1 - 3 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 08.08.2026 | Yate Town - Gosport Borough | 1 - 0 | W |
| 01.08.2026 | Leamington - Yate Town | 3 - 1 | L |
| 24.07.2026 | Yate Town - Bristol Rovers | - | |
| 11.07.2026 | Yate Town - Barry Town | 0 - 1 | L |
| 25.04.2026 | Havant & Wville - Yate Town | 1 - 3 | W |
The upcoming match between Chippenham Town and Yate Town is scheduled for 11.08.2026 18:45 in Non League Premier - Southern 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.
Chippenham Town recorded 4 wins, 1 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is LWWLLDWLLW. The averages are 1.40 goals scored and 1.40 goals conceded per match. Both teams scored in 50% of those matches, while 40% finished with over 2.5 goals. Yate Town recorded 6 wins, 2 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLLWWWWDWD. The averages are 1.80 goals scored and 1 goals conceded per match. Both teams scored in 50% of those matches, while 60% finished with over 2.5 goals.
Across the last 2 head-to-head matches, Chippenham Town recorded 1 wins, there were 0 draws, and Yate Town recorded 1 wins. The average total was 3 goals per match. Both teams scored in 50% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Both teams to score — 80%; Over 0.5 first-half goals — 80%; Over 1.5 goals — 80%; Over 2.5 goals — 70%; Under 3.5 goals — 60%. They are statistical indicators and are not automatically converted into a prediction.
3 active football Premium signals are stored for this fixture. Odd/Even — Odd (odds 2). Goals Over/Under — Over 1.5 (odds 1.23, score 83/100, 82.80% bucket win rate across 93 observations). Both Teams Score — Yes (odds 1.55).
The match between Chippenham Town and Yate Town ended 1-1. The game produced 2 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.
Before kickoff, the stored trend indicated BTTS at 80%. The actual outcome was 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 70%. The actual outcome was Under 2.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 60%. 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 70%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
The stored Premium market was Odd at odds of 2. The actual market outcome was Even. The Premium signal was not confirmed. The stored Premium market was Over 1.5 FT at odds of 1.23. The actual market outcome was Over 1.5 FT. The Premium signal was confirmed. The stored Premium market was BTTS Yes at odds of 1.55. The actual market outcome was BTTS Yes. The Premium signal was confirmed.
Of 9 verifiable pre-match indicators, 7 aligned with the final result and 2 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.