Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 10.08.2026 | Mika - Pyunik II | 2 : 4 |
| 23.03.2026 | Pyunik II - Mika | 0 : 0 |
| 28.10.2025 | Mika - Pyunik II | 0 : 0 |
| 21.04.2025 | Mika - Pyunik II | 0 : 2 |
| 29.11.2024 | Pyunik II - Mika | 3 : 2 |
| 05.12.2023 | Pyunik II - Mika | 5 : 0 |
| 05.08.2023 | Mika - Pyunik II | 1 : 3 |
| 16.04.2023 | Pyunik II - Mika | 0 : 1 |
| 31.10.2022 | Mika - Pyunik II | 0 : 1 |
| 14.08.2022 | Pyunik II - Mika | 4 : 0 |
| Date | Match | Score | Res |
|---|---|---|---|
| 10.08.2026 | Mika - Pyunik II | 2 - 4 | L |
| 04.08.2026 | Noah II - Mika | 2 - 3 | W |
| 25.05.2026 | Mika - Noah II | 0 - 0 | D |
| 18.05.2026 | Hayq - Mika | 0 - 0 | D |
| 12.05.2026 | Mika - Shirak II | 0 - 0 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 10.08.2026 | Mika - Pyunik II | 2 - 4 | W |
| 04.08.2026 | Pyunik II - Ararat-Armenia II | 1 - 0 | W |
| 26.05.2026 | Van II - Pyunik II | 0 - 0 | D |
| 19.05.2026 | Pyunik II - Bentonit Ijevan | 2 - 0 | W |
| 11.05.2026 | Syunik - Pyunik II | 2 - 3 | W |
The upcoming match between Mika and Pyunik II is scheduled for 10.08.2026 13:00 in First 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.
Mika recorded 2 wins, 6 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDDDDLLWDD. The averages are 0.70 goals scored and 0.70 goals conceded per match. Both teams scored in 30% of those matches, while 30% finished with over 2.5 goals. Pyunik II recorded 4 wins, 4 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDWWLDWDDL. The averages are 1.20 goals scored and 1.10 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals.
Across the last 9 head-to-head matches, Mika recorded 1 wins, there were 2 draws, and Pyunik II recorded 6 wins. The average total was 2.44 goals per match. Both teams scored in 22.2% of those matches, while 44.4% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 70%; Both teams to score — 60%; Over 0.5 first-half goals — 60%; Over 2.5 goals — 60%; Over 3.5 goals — 50%. They are statistical indicators and are not automatically converted into a prediction.
The match between Mika and Pyunik II ended 2-4. The game produced 6 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.
The previous 9 head-to-head meetings averaged 2.44 goals, while this match produced 6. The final scoring profile differed by more than one goal from that average. Across the previous 9 head-to-head meetings, the leading historical direction was No BTTS at 77.8%. The actual outcome for this indicator was BTTS. The final result did not align with that historical profile. Across the previous 9 head-to-head meetings, the leading historical direction was Under 2.5 at 55.6%. 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 60%. The actual outcome was BTTS. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 70%. 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 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 70%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
Of 8 verifiable pre-match indicators, 5 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.