Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 14.02.2026 | Torquay - Maidenhead | 1 : 1 |
| 08.11.2025 | Maidenhead - Torquay | 1 : 2 |
| 10.04.2023 | Maidenhead - Torquay | 1 : 3 |
| 04.10.2022 | Torquay - Maidenhead | 2 : 3 |
| 30.04.2022 | Torquay - Maidenhead | 1 : 1 |
| 04.09.2021 | Maidenhead - Torquay | 3 : 4 |
| 16.03.2021 | Maidenhead - Torquay | 4 : 1 |
| 08.12.2020 | Torquay - Maidenhead | 2 : 1 |
| 13.08.2019 | Torquay - Maidenhead | 0 : 2 |
| 10.02.2018 | Maidenhead - Torquay | 1 : 2 |
| Date | Match | Score | Res |
|---|---|---|---|
| 05.09.2026 | Dover - Maidenhead | 0 - 3 | W |
| 31.08.2026 | Maidenhead - AFC Totton | 1 - 1 | D |
| 29.08.2026 | Chelmsford City - Maidenhead | 1 - 0 | L |
| 22.08.2026 | Maidenhead - Farnborough | 1 - 1 | D |
| 18.08.2026 | Hemel Hempstead Town - Maidenhead | 0 - 1 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 05.09.2026 | Torquay - Folkestone Invicta | 3 - 2 | W |
| 31.08.2026 | Farnham Town - Torquay | 2 - 0 | L |
| 29.08.2026 | Torquay - Hampton & Richmond | 1 - 1 | D |
| 22.08.2026 | Dagenham & Redbridge - Torquay | 2 - 0 | L |
| 18.08.2026 | Torquay - Weston-super-Mare | 0 - 0 | D |
The upcoming match between Maidenhead and Torquay is scheduled for 08.09.2026 18:45 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
Maidenhead are in position 12 with 9 points. The stored form sequence is WDLDW. Torquay are in position 13 with 9 points. The stored form sequence is WLDLD.
Maidenhead recorded 2 wins, 4 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDLDWDLLDL. The averages are 0.70 goals scored and 0.80 goals conceded per match. Both teams scored in 30% of those matches, while 10% finished with over 2.5 goals. Torquay recorded 4 wins, 3 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLDLDWDWWL. The averages are 1.40 goals scored and 1.10 goals conceded per match. Both teams scored in 50% of those matches, while 40% finished with over 2.5 goals.
Across the last 10 head-to-head matches, Maidenhead recorded 3 wins, there were 2 draws, and Torquay recorded 5 wins. The average total was 3.60 goals per match. Both teams scored in 90% of those matches, while 70% finished with over 2.5 goals.
The highest stored values are: Under 3.5 goals — 100%; Under 2.5 goals — 90%; Over 0.5 first-half goals — 70%; Over 1.5 goals — 60%; Both teams to score — 40%. They are statistical indicators and are not automatically converted into a prediction.
The discipline profile for Maidenhead at home is based on 1 matches. The team averages 0.00 yellow cards, 1.00 red cards and 1.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 0.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 100.0%. Season card data is available for 2 of 7 completed matches (28.6% coverage). The discipline profile for Torquay away from home is based on 1 matches. The team averages 0.00 yellow cards, 1.00 red cards and 1.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 0.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 100.0%. Season card data is available for 1 of 7 completed matches (14.3% coverage).
The match between Maidenhead and Torquay ended 0-4. The game produced 4 goals in total. The first half contained 0 goals. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
The historical profile from 10 head-to-head meetings averaged 3.6 goals, while this match produced 4. The result remained within one goal of the historical average. Across the previous 10 head-to-head meetings, the leading historical direction was BTTS at 90%. The actual outcome for this indicator was No BTTS. The final result did not align with that historical profile. Across the previous 10 head-to-head meetings, the leading historical direction was Over 2.5 at 70%. The actual outcome for this indicator was Over 2.5. The final result aligned with that historical profile.
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 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 90%. 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 100%. The actual outcome was Over 3.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 70%. 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 70%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
Before kickoff, the discipline profile for Maidenhead at home was based on 1 matches, with averages of 0 yellow cards, 1 red cards and 1 total cards per match. In this game, Maidenhead received 1 yellow cards and 2 red cards, 3 in total. That was 2 cards above the stored average. In the pre-match sample, 3+ cards occurred in 0% of matches, 5+ in 0%, and a red card in 100%. Before kickoff, the discipline profile for Torquay away from home was based on 1 matches, with averages of 0 yellow cards, 1 red cards and 1 total cards per match. In this game, Torquay received 0 yellow cards and 0 red cards, 0 in total. That was 1 cards below the stored average. In the pre-match sample, 3+ cards occurred in 0% of matches, 5+ in 0%, and a red card in 100%.
Of 9 verifiable pre-match indicators, 5 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.