Match context

The upcoming match between Rubin and FC Orenburg is scheduled for 09.08.2026 17:30 in Premier League. 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
Rubin are in position 8 with 3 points after 2 matches. The season record is 1 wins, 0 draws and 1 losses. The goals record is 3 scored and 4 conceded. The stored form sequence is WL. FC Orenburg are in position 6 with 3 points after 2 matches. The season record is 1 wins, 0 draws and 1 losses. The goals record is 2 scored and 4 conceded. The stored form sequence is LW.

Recent results

Rubin recorded 2 wins, 3 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is LWLLWDLDDL. The averages are 1.10 goals scored and 1.90 goals conceded per match. Both teams scored in 70% of those matches, while 70% finished with over 2.5 goals. FC Orenburg recorded 4 wins, 0 draws and 6 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLWWLWLLWL. The averages are 1 goals scored and 1.90 goals conceded per match. Both teams scored in 50% of those matches, while 70% finished with over 2.5 goals.

Head-to-head

Across the last 10 head-to-head matches, Rubin recorded 4 wins, there were 3 draws, and FC Orenburg recorded 3 wins. The average total was 3 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: Over 1.5 goals — 90%; Under 3.5 goals — 80%; Over 2.5 goals — 70%; Both teams to score — 60%; Over 0.5 first-half goals — 60%. The stored corner indicators are: average total corners — 8.40; over 7.5 corners — 100%; over 8.5 corners — 99%; over 9.5 corners — 88%. They are statistical indicators and are not automatically converted into a prediction.

Asian handicap market movement

The normalized movement for the Asian pair Rubin 0 / FC Orenburg 0 supports FC Orenburg by an average 2.01 percentage points across 2 bookmakers (Pinnacle, 1xBet) with up to 14 stored observations. This is a market signal, not a result guarantee.

What happened in the match

The match between Rubin and FC Orenburg ended 1-1. The game produced 2 goals in total. The first half contained 0 goals. 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 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 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 BTTS at 60%. The actual outcome was BTTS. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 90%. The actual outcome was Over 1.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 2.5 at 70%. The actual outcome was Under 2.5. The stored trend was not 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 Over 0.5 HT at 60%. The actual outcome was Under 0.5 HT. The stored trend was not confirmed by the result.

Asian handicap review

The Asian-handicap signal locked before kickoff supported FC Orenburg at 0. The stored market movement was 2.01 percentage points across 2 bookmakers. At the final score of 1-1, the line settled as a push. The result is neutral and is counted as neither confirmed nor unconfirmed.

Summary

Of 8 verifiable pre-match indicators, 4 aligned with the final result and 3 were not confirmed, while 1 settled neutrally. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.