Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 11.04.2026 | Haman - Geoje Citizen | 2 : 2 |
| Date | Match | Score | Res |
|---|---|---|---|
| 25.10.2026 | Geoje Citizen - Jungnang Chorus Mustang | 4 - 0 | W |
| 17.10.2026 | Geoje Citizen - Haman | 1 - 0 | W |
| 11.10.2026 | Geoje Citizen - Pyeongtaek Citizen | 3 - 0 | W |
| 03.10.2026 | Jinju Citizen - Geoje Citizen | 0 - 0 | D |
| 19.09.2026 | Jecheon Citizen - Geoje Citizen | 0 - 2 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 17.10.2026 | Geoje Citizen - Haman | 1 - 0 | L |
| 10.10.2026 | Jungnang Chorus Mustang - Haman | 2 - 0 | L |
| 03.10.2026 | Haman - Jecheon Citizen | 1 - 3 | L |
| 06.09.2026 | Haman - Jincheon | 3 - 1 | W |
| 29.08.2026 | Haman - Pyeongchang United | 2 - 3 | L |
The upcoming match between Geoje Citizen and Haman is scheduled for 17.10.2026 05:00 in K4 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
Geoje Citizen are in position 6 with 31 points after 20 matches. The season record is 9 wins, 4 draws and 7 losses. The goals record is 36 scored and 26 conceded. The stored form sequence is WDWWL. Haman are in position 11 with 20 points after 21 matches. The season record is 6 wins, 2 draws and 13 losses. The goals record is 23 scored and 37 conceded. The stored form sequence is LLWLW.
Geoje Citizen recorded 5 wins, 2 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDWWLLWWLD. The averages are 1.50 goals scored and 1.40 goals conceded per match. Both teams scored in 30% of those matches, while 60% finished with over 2.5 goals. Haman recorded 2 wins, 0 draws and 5 losses across the last 7 completed matches. The newest-to-oldest result sequence is LLWLWLL. The averages are 1.14 goals scored and 1.86 goals conceded per match. Both teams scored in 57.1% of those matches, while 57.1% finished with over 2.5 goals.
Across the last 1 head-to-head matches, Geoje Citizen recorded 0 wins, there were 1 draws, and Haman recorded 0 wins. The average total was 4 goals per match. Both teams scored in 100% of those matches, while 100% finished with over 2.5 goals.
The highest stored values are: Over 0.5 first-half goals — 70%; Over 1.5 goals — 70%; Over 2.5 goals — 50%; Over 3.5 goals — 50%; Under 2.5 goals — 50%. They are statistical indicators and are not automatically converted into a prediction.
The PMV3 model classifies the leading outcome as Geoje Citizen or draw (1X) with 81% confidence. The stored fair probabilities for home, draw and away are 59.78%, 21.35% and 18.88%. The model momentum difference is 40.90 points in favour of Geoje Citizen. The input data quality score is 96/100. The stored price for the selected market is 1.12 with Bet365. The stored estimated EV is -9.14%. Despite the model probability, the price is marked NO_VALUE. The signal is therefore not treated automatically as a value bet.
The match between Geoje Citizen and Haman ended 1-0. The game produced 1 goal 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.
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 Over 1.5 at 70%. The actual outcome was Under 1.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 70%. The actual outcome was Under 0.5 HT. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 1.5 HT at 90%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
Of 4 verifiable pre-match indicators, 2 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.