Match context

The upcoming match between Barnsley and Crewe is scheduled for 25.08.2026 18:45 in 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

Barnsley recorded 3 wins, 3 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is DLDDWWLLWL. The averages are 1.10 goals scored and 1 goals conceded per match. Both teams scored in 50% of those matches, while 40% finished with over 2.5 goals. Crewe recorded 5 wins, 3 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWWDLWDWDL. The averages are 1.20 goals scored and 0.80 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals.

Head-to-head

Across the last 10 head-to-head matches, Barnsley recorded 7 wins, there were 1 draws, and Crewe recorded 2 wins. The average total was 2.50 goals per match. Both teams scored in 50% of those matches, while 60% finished with over 2.5 goals.

Trend indicators

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

Premium market signals

1 active football Premium signals are stored for this fixture. At least one goal in the match (quota 17, score 82/100, 81.75% group success rate across 1989 observations).

Discipline profile

The discipline profile for Barnsley at home is based on 1 matches. The team averages 0.00 yellow cards, 0.00 red cards and 0.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 0.0%, 0.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).

What happened in the match

The match between Barnsley and Crewe ended 3-2. The game produced 5 goals in total. The first half contained 4 goals. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.

Comparison with the head-to-head history

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

Which pre-match trends were confirmed and which were not

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

Discipline profile review

Before kickoff, the discipline profile for Barnsley at home was based on 1 matches, with averages of 0 yellow cards, 0 red cards and 0 total cards per match. In this game, Barnsley received 2 yellow cards and 0 red cards, 2 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 0%.

Premium market review

The stored Premium market was At least one FT goal with quota 17. The actual market outcome was At least one FT goal. The Premium signal was confirmed.

Summary

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