Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 27.02.2021 | Galatasaray - Erzurum BB | 2 : 0 |
| 24.10.2020 | Erzurum BB - Galatasaray | 1 : 2 |
| 03.03.2019 | Erzurum BB - Galatasaray | 1 : 1 |
| 28.09.2018 | Galatasaray - Erzurum BB | 1 : 0 |
| Date | Match | Score | Res |
|---|---|---|---|
| 16.08.2026 | Amed - Erzurum BB | 3 - 0 | L |
| 17.07.2026 | Erzurum BB - Rizespor | 0 - 0 | D |
| 02.05.2026 | Yeni Çorumspor - Erzurum BB | 1 - 1 | D |
| 26.04.2026 | Erzurum BB - Bandırmaspor | 1 - 1 | D |
| 19.04.2026 | BB Bodrumspor - Erzurum BB | 1 - 1 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 14.08.2026 | Galatasaray - Yeni Çorumspor | 2 - 2 | D |
| 08.08.2026 | Galatasaray - Villarreal | 1 - 2 | L |
| 02.08.2026 | Galatasaray - Rennes | 3 - 3 | D |
| 27.07.2026 | Galatasaray - Venezia | 0 - 3 | L |
| 24.07.2026 | Galatasaray - Monza | 0 - 2 | L |
The upcoming match between Erzurum BB and Galatasaray is scheduled for 21.08.2026 18:30 in Süper Lig. 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
Erzurum BB are in position 18 with 0 points. The stored form sequence is L. Galatasaray are in position 8 with 1 points. The stored form sequence is D.
Erzurum BB recorded 5 wins, 4 draws and 1 losses across the last 10 completed matches. The newest-to-oldest result sequence is LDDDDWWWWW. The averages are 1.30 goals scored and 0.70 goals conceded per match. Both teams scored in 40% of those matches, while 30% finished with over 2.5 goals. Galatasaray recorded 3 wins, 2 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is DLDLLWLWLW. The averages are 1.90 goals scored and 2 goals conceded per match. Both teams scored in 60% of those matches, while 80% finished with over 2.5 goals.
Across the last 4 head-to-head matches, Erzurum BB recorded 0 wins, there were 1 draws, and Galatasaray recorded 3 wins. The average total was 2 goals per match. Both teams scored in 50% of those matches, while 25% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 90%; Both teams to score — 70%; Under 3.5 goals — 70%; Over 0.5 first-half goals — 60%; Over 2.5 goals — 50%. The stored corner indicators are: average total corners — 9; over 7.5 corners — 100%; over 8.5 corners — 100%; over 9.5 corners — 95%. They are statistical indicators and are not automatically converted into a prediction.
The PMV3 model classifies the leading outcome as Galatasaray to win with 62% confidence. The stored fair probabilities for home, draw and away are 14.95%, 22.78% and 62.27%. The model momentum difference is 47.33 points in favour of Galatasaray. The input data quality score is 99/100. The stored price for the selected market is 1.50 with Bet365. The stored estimated EV is -6.59%. Despite the model probability, the price is marked NO_VALUE. The signal is therefore not treated automatically as a value bet.
The normalized movement for the Asian pair Erzurum BB 0 / Galatasaray 0 supports Erzurum BB by an average 2.04 percentage points across 3 bookmakers (Pinnacle, Bet365, 1xBet) with up to 8 stored observations. This is a market signal, not a result guarantee.
1 active football Premium signals are stored for this fixture. Goals Over/Under — Over 1.5 (odds 1.20, score 78/100, 77.58% bucket win rate across 446 observations).
The match between Erzurum BB and Galatasaray ended 0-4. The game produced 4 goals in total. The first half contained 3 goals. The verified final statistics recorded 4 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.
The previous 4 head-to-head meetings averaged 2 goals, while this match produced 4. The final scoring profile differed by more than one goal from that average. Across the previous 4 head-to-head meetings, the leading historical direction was Under 2.5 at 75%. The actual outcome for this indicator was Over 2.5. The final result did not align with that historical profile.
Before kickoff, the stored trend indicated BTTS at 70%. The actual outcome was No BTTS. The stored trend was not 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 Under 3.5 at 70%. The actual outcome was Over 3.5. The stored trend was not confirmed by the result. The stored pre-match average was 9 total corners. The match recorded 4 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 Under 7.5 corners. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 8.5 corners at 100%. The actual outcome was Under 8.5 corners. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 9.5 corners at 95%. The actual outcome was Under 9.5 corners. 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 Over 1.5 HT. The stored trend was not confirmed by the result.
The Asian-handicap signal locked before kickoff supported Erzurum BB at 0. The stored market movement was 2.04 percentage points across 3 bookmakers. At the final score of 0-4, the line settled as a full loss. The Asian-handicap signal was not confirmed.
The stored Premium market was Over 1.5 FT at odds of 1.2. The actual market outcome was Over 1.5 FT. The Premium signal was confirmed.
Of 13 verifiable pre-match indicators, 3 aligned with the final result and 10 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.