Match context

The upcoming match between Clermont Foot and Grenoble is scheduled for 01.08.2026 15:00 in Friendlies Clubs. 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

Clermont Foot recorded 4 wins, 4 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is LWDWWWDLDD. The averages are 1.30 goals scored and 0.90 goals conceded per match. Both teams scored in 50% of those matches, while 40% finished with over 2.5 goals. Grenoble recorded 3 wins, 5 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is DLWDWWDLDD. The averages are 1.20 goals scored and 0.90 goals conceded per match. Both teams scored in 50% of those matches, while 30% finished with over 2.5 goals.

Head-to-head

Across the last 10 head-to-head matches, Clermont Foot recorded 3 wins, there were 4 draws, and Grenoble recorded 3 wins. The average total was 2.30 goals per match. Both teams scored in 40% of those matches, while 60% finished with over 2.5 goals.

Trend indicators

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

Asian handicap market movement

The normalized movement for the Asian pair Clermont Foot -0.75 / Grenoble +0.75 supports Grenoble by an average 1.22 percentage points across 2 bookmakers (Pinnacle, 1xBet) with up to 2 stored observations. This is a market signal, not a result guarantee.

Premium market signals

1 active football Premium signals are stored for this fixture. Goals Over/Under — Over 1.5 (odds 1.22, score 79/100, 79.40% bucket win rate across 233 observations).

What happened in the match

The match between Clermont Foot and Grenoble 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.

Comparison with the head-to-head history

The historical profile from 10 head-to-head meetings averaged 2.3 goals, while this match produced 2. The result remained within one goal of the historical average. Across the previous 10 head-to-head meetings, the leading historical direction was No BTTS at 60%. The actual outcome for this indicator was 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 60%. The actual outcome for this indicator was Under 2.5. The final result did not align with that historical profile.

Which pre-match trends were confirmed and which were not

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

Asian handicap review

The Asian-handicap signal locked before kickoff supported Grenoble at +0.75. The stored market movement was 1.22 percentage points across 2 bookmakers. At the final score of 1-1, the line settled as a full win. The Asian-handicap signal was confirmed.

Premium market review

The stored Premium market was Over 1.5 FT at odds of 1.22. The actual market outcome was Over 1.5 FT. The Premium signal was confirmed.

Summary

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