Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|
| Date | Match | Score | Res |
|---|---|---|---|
| 08.08.2026 | Ümraniyespor - Mardin BB | 0 - 0 | D |
| 09.05.2026 | Mardin BB - Muş Menderesspor | 2 - 1 | W |
| 04.05.2026 | Mardin BB - Kahramanmaraş İstiklalsp | 0 - 0 | D |
| 30.04.2026 | Kahramanmaraş İstiklalsp - Mardin BB | 0 - 0 | D |
| 25.04.2026 | Mardin BB - Fethiyespor | 0 - 0 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 08.08.2026 | Antalyaspor - Keçiörengücü | 4 - 3 | W |
| 17.05.2026 | Antalyaspor - Kocaelispor | 1 - 0 | W |
| 09.05.2026 | Galatasaray - Antalyaspor | 4 - 2 | L |
| 03.05.2026 | Antalyaspor - Alanyaspor | 0 - 0 | D |
| 25.04.2026 | Göztepe - Antalyaspor | 2 - 0 | L |
The upcoming match between Mardin BB and Antalyaspor is scheduled for 16.08.2026 18:30 in 1. 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
Mardin BB are in position 13 with 1 points. The stored form sequence is D. Antalyaspor are in position 6 with 3 points. The stored form sequence is W.
Mardin BB recorded 5 wins, 4 draws and 1 losses across the last 10 completed matches. The newest-to-oldest result sequence is DWDDDWWLWW. The averages are 1 goals scored and 0.60 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals. Antalyaspor recorded 3 wins, 2 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWLDLLLWDL. The averages are 1.30 goals scored and 1.90 goals conceded per match. Both teams scored in 40% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Under 3.5 goals — 80%; Under 2.5 goals — 60%; Both teams to score — 40%; Over 1.5 goals — 40%; Over 2.5 goals — 40%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Mardin BB -1.25 / Antalyaspor +1.25 supports Mardin BB by an average 1.79 percentage points across 2 bookmakers (Bet365, 1xBet) with up to 7 stored observations. This is a market signal, not a result guarantee.
2 active football Premium signals are stored for this fixture. Both Teams Score — Yes (odds 1.78). Goals Over/Under — Under 2.5 (odds 1.90).
The match between Mardin BB and Antalyaspor ended 2-0. The game produced 2 goals in total. The first half contained 1 goal. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
Before kickoff, the stored trend indicated No BTTS at 60%. The actual outcome was No BTTS. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 60%. 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 70%. 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 100%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
The Asian-handicap signal locked before kickoff supported Mardin BB at -1.25. The stored market movement was 1.79 percentage points across 2 bookmakers. At the final score of 2-0, the line settled as a full win. The Asian-handicap signal was confirmed.
The stored Premium market was BTTS Yes at odds of 1.78. The actual market outcome was BTTS No. The Premium signal was not confirmed. The stored Premium market was Under 2.5 at odds of 1.9. The actual market outcome was Under 2.5. The Premium signal was confirmed.
Of 8 verifiable pre-match indicators, 6 aligned with the final result and 2 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.