Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 22.08.2026 | Pirin Razlog - Oborishte | 2 : 4 |
| 16.05.2026 | Oborishte - Pirin Razlog | 3 : 1 |
| 01.11.2025 | Pirin Razlog - Oborishte | 1 : 1 |
| 24.05.2025 | Pirin Razlog - Oborishte | 2 : 5 |
| 09.11.2024 | Oborishte - Pirin Razlog | 2 : 0 |
| 17.02.2024 | Oborishte - Pirin Razlog | 0 : 1 |
| 05.08.2023 | Pirin Razlog - Oborishte | 1 : 3 |
| 16.11.2022 | Pirin Razlog - Oborishte | 1 : 3 |
| 06.08.2022 | Oborishte - Pirin Razlog | 2 : 0 |
| 09.04.2022 | Oborishte - Pirin Razlog | 4 : 2 |
| Date | Match | Score | Res |
|---|---|---|---|
| 22.08.2026 | Pirin Razlog - Oborishte | 2 - 4 | L |
| 15.08.2026 | Bansko - Pirin Razlog | 3 - 1 | L |
| 08.08.2026 | Pirin Razlog - FK Minyor Pernik | 0 - 3 | L |
| 01.08.2026 | Pirin Razlog - Belasitsa | 1 - 3 | L |
| 30.05.2026 | Pirin Razlog - Strumska Slava | 2 - 1 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 22.08.2026 | Pirin Razlog - Oborishte | 2 - 4 | W |
| 15.08.2026 | Oborishte - Natsional Sofia | 3 - 1 | W |
| 08.08.2026 | Chavdar Etropole - Oborishte | 1 - 1 | D |
| 01.08.2026 | Oborishte - CSKA Sofia III | 1 - 1 | D |
| 30.05.2026 | Oborishte - Germaneya | 5 - 1 | W |
The upcoming match between Pirin Razlog and Oborishte is scheduled for 22.08.2026 15:00 in Third League - Southwest. 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.
Pirin Razlog recorded 3 wins, 0 draws and 7 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLLWWLLLWL. The averages are 1.20 goals scored and 2.10 goals conceded per match. Both teams scored in 60% of those matches, while 70% finished with over 2.5 goals. Oborishte recorded 4 wins, 3 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDDWDWLLLW. The averages are 1.70 goals scored and 1.20 goals conceded per match. Both teams scored in 80% of those matches, while 50% finished with over 2.5 goals.
Across the last 10 head-to-head matches, Pirin Razlog recorded 1 wins, there were 1 draws, and Oborishte recorded 8 wins. The average total was 3.30 goals per match. Both teams scored in 60% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 100%; Both teams to score — 80%; Over 0.5 first-half goals — 80%; Over 2.5 goals — 60%; Under 3.5 goals — 60%. They are statistical indicators and are not automatically converted into a prediction.
The match between Pirin Razlog and Oborishte ended 2-4. The game produced 6 goals in total. The first half contained 0 goals. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
The previous 10 head-to-head meetings averaged 3.3 goals, while this match produced 6. 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 60%. The actual outcome for this indicator was BTTS. The final result aligned with that historical profile.
Before kickoff, the stored trend indicated BTTS at 80%. The actual outcome was BTTS. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 100%. 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 60%. The actual outcome was Over 2.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. Before kickoff, the stored trend indicated Over 0.5 HT at 80%. The actual outcome was Under 0.5 HT. The stored trend was not confirmed by the result.
Of 7 verifiable pre-match indicators, 4 aligned with the final result and 3 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.