Match context

The upcoming match between Wealdstone and Stoke City U21 is scheduled for 08.09.2026 18:00 in National League Cup. 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

Wealdstone recorded 4 wins, 2 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is LWDLLLDWWW. The averages are 1.30 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. Stoke City U21 recorded 3 wins, 2 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is LDLLDWLLWW. The averages are 0.80 goals scored and 1.70 goals conceded per match. Both teams scored in 30% of those matches, while 50% finished with over 2.5 goals.

Trend indicators

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

Discipline profile

The discipline profile for Wealdstone at home is based on 1 matches. The team averages 2.00 yellow cards, 0.00 red cards and 2.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 100.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 0.0%. Season card data is available for 1 of 1 completed matches (100.0% coverage). The discipline profile for Stoke City U21 away from home is based on 1 matches. The team averages 5.00 yellow cards, 0.00 red cards and 5.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 100.0%, 100.0%, 100.0% and 100.0% of those matches respectively, while a red card occurred in 0.0%. Season card data is available for 1 of 1 completed matches (100.0% coverage).

What happened in the match

The match between Wealdstone and Stoke City U21 ended 6-0. The game produced 6 goals in total. The first half contained 1 goal. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.

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 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 60%. 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 60%. 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 80%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.

Discipline profile review

Before kickoff, the discipline profile for Wealdstone at home was based on 1 matches, with averages of 2 yellow cards, 0 red cards and 2 total cards per match. In this game, Wealdstone received 2 yellow cards and 0 red cards, 2 in total. The total was effectively equal to the stored average. In the pre-match sample, 3+ cards occurred in 0% of matches, 5+ in 0%, and a red card in 0%. Before kickoff, the discipline profile for Stoke City U21 away from home was based on 1 matches, with averages of 5 yellow cards, 0 red cards and 5 total cards per match. In this game, Stoke City U21 received 2 yellow cards and 1 red cards, 3 in total. That was 2 cards below the stored average. In the pre-match sample, 3+ cards occurred in 100% of matches, 5+ in 100%, and a red card in 0%.

Summary

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