Match context

The upcoming match between Utrecht and AZ Alkmaar is scheduled for 15.08.2026 16:45 in Eredivisie. The listed venue is Stadion Galgenwaard, Utrecht. 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

Utrecht recorded 4 wins, 1 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLLLLDWWWW. The averages are 1.10 goals scored and 1.10 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals. AZ Alkmaar recorded 5 wins, 5 draws and 0 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWWWDWDDDD. The averages are 2.50 goals scored and 1.30 goals conceded per match. Both teams scored in 70% of those matches, while 70% finished with over 2.5 goals.

Head-to-head

Across the last 10 head-to-head matches, Utrecht recorded 3 wins, there were 5 draws, and AZ Alkmaar recorded 2 wins. The average total was 3.80 goals per match. Both teams scored in 80% of those matches, while 70% finished with over 2.5 goals.

Trend indicators

The highest stored values are: Over 0.5 first-half goals — 70%; Over 1.5 goals — 70%; Under 3.5 goals — 60%; Over 2.5 goals — 50%; Under 2.5 goals — 50%. The stored corner indicators are: average total corners — 10.70; over 7.5 corners — 100%; over 8.5 corners — 100%; over 9.5 corners — 100%. They are statistical indicators and are not automatically converted into a prediction.

What happened in the match

The match between Utrecht and AZ Alkmaar ended 1-4. The game produced 5 goals in total. The first half contained 1 goal. The verified final statistics recorded 12 corners in total. 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 3.8 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 BTTS at 80%. The actual outcome for this indicator was BTTS. The final result aligned 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.

Which pre-match trends were confirmed and which were not

Before kickoff, the stored trend indicated No BTTS at 60%. 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 60%. The actual outcome was Over 3.5. The stored trend was not confirmed by the result. The stored pre-match average was 10.7 total corners. The match recorded 12 corners in total. The result differed by more than one corner from the stored average. Before kickoff, the stored trend indicated Over 7.5 corners at 100%. The actual outcome was Over 7.5 corners. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 8.5 corners at 100%. The actual outcome was Over 8.5 corners. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 9.5 corners at 100%. The actual outcome was Over 9.5 corners. The stored trend was 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 80%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.

Summary

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