Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 20.09.2025 | Omiya Ardija - Imabari | 2 : 3 |
| 20.04.2025 | Imabari - Omiya Ardija | 0 : 0 |
| 19.10.2024 | Omiya Ardija - Imabari | 1 : 1 |
| 27.04.2024 | Imabari - Omiya Ardija | 1 : 4 |
| Date | Match | Score | Res |
|---|---|---|---|
| 09.08.2026 | Iwaki - Imabari | 2 - 1 | L |
| 22.07.2026 | Vissel Kobe - Imabari | 2 - 1 | L |
| 07.06.2026 | Vanraure Hachinohe - Imabari | 1 - 1 | D |
| 31.05.2026 | Imabari - FC Ryukyu | 1 - 2 | L |
| 24.05.2026 | Tokushima Vortis - Imabari | 1 - 1 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 08.08.2026 | Omiya Ardija - Albirex Niigata | 1 - 0 | W |
| 01.08.2026 | Urawa - Omiya Ardija | 2 - 2 | D |
| 06.06.2026 | Omiya Ardija - Kochi United | 2 - 1 | W |
| 30.05.2026 | Yokohama FC - Omiya Ardija | 2 - 1 | L |
| 23.05.2026 | FC Gifu - Omiya Ardija | 0 - 2 | W |
The upcoming match between Imabari and Omiya Ardija is scheduled for 15.08.2026 10:00 in J2 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
Imabari are in position 9 with 20 points after 20 matches. The season record is 7 wins, 0 draws and 13 losses. The goals record is 18 scored and 24 conceded. The stored form sequence is DLLLW. Omiya Ardija are in position 4 with 30 points after 20 matches. The season record is 11 wins, 0 draws and 9 losses. The goals record is 42 scored and 32 conceded. The stored form sequence is WLWLL.
Imabari recorded 3 wins, 2 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLDLDLWWLW. The averages are 1.20 goals scored and 1.30 goals conceded per match. Both teams scored in 80% of those matches, while 60% finished with over 2.5 goals. Omiya Ardija recorded 5 wins, 1 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDWLWLLWWL. The averages are 1.80 goals scored and 1.60 goals conceded per match. Both teams scored in 80% of those matches, while 80% finished with over 2.5 goals.
Across the last 4 head-to-head matches, Imabari recorded 1 wins, there were 2 draws, and Omiya Ardija recorded 1 wins. The average total was 3 goals per match. Both teams scored in 75% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Under 3.5 goals — 90%; Over 0.5 first-half goals — 80%; Over 1.5 goals — 80%; Both teams to score — 70%; Over 2.5 goals — 70%. They are statistical indicators and are not automatically converted into a prediction.
1 active football Premium signals are stored for this fixture. Both Teams Score — Yes (odds 1.70).
The discipline profile for Imabari at home is based on 3 matches. The team averages 2.33 yellow cards, 0.33 red cards and 2.67 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 66.7%, 66.7%, 33.3% and 0.0% of those matches respectively, while a red card occurred in 33.3%. Season card data is available for 8 of 21 completed matches (38.1% coverage). The discipline profile for Omiya Ardija away from home is based on 4 matches. The team averages 1.25 yellow cards, 0.25 red cards and 1.50 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 50.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 25.0%. Season card data is available for 7 of 21 completed matches (33.3% coverage).
The match between Imabari and Omiya Ardija ended 2-3. The game produced 5 goals in total. The first half contained 3 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 4 head-to-head meetings averaged 3 goals, while this match produced 5. 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 BTTS at 75%. The actual outcome for this indicator was BTTS. The final result aligned with that historical profile.
Before kickoff, the stored trend indicated BTTS at 70%. The actual outcome was BTTS. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 80%. 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 Over 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 90%. 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 Over 0.5 HT. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 1.5 HT at 90%. The actual outcome was Over 1.5 HT. The stored trend was not confirmed by the result.
Before kickoff, the discipline profile for Imabari at home was based on 3 matches, with averages of 2.33 yellow cards, 0.33 red cards and 2.67 total cards per match. In this game, Imabari received 3 yellow cards and 0 red cards, 3 in total. That was 0.33 cards above the stored average. In the pre-match sample, 3+ cards occurred in 66.7% of matches, 5+ in 0%, and a red card in 33.3%. Before kickoff, the discipline profile for Omiya Ardija away from home was based on 4 matches, with averages of 1.25 yellow cards, 0.25 red cards and 1.5 total cards per match. In this game, Omiya Ardija received 1 yellow cards and 0 red cards, 1 in total. That was 0.5 cards below the stored average. In the pre-match sample, 3+ cards occurred in 0% of matches, 5+ in 0%, and a red card in 25%.
The stored Premium market was BTTS Yes at odds of 1.7. The actual market outcome was BTTS Yes. The Premium signal was confirmed.
Of 9 verifiable pre-match indicators, 6 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.