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 |
|---|---|---|---|
| 19.08.2026 | Dangjin Citizen - Jeonbuk Motors | 2 - 2 | D |
| 29.07.2026 | Yeoju Sejong - Dangjin Citizen | 0 - 1 | W |
| 25.07.2026 | Dangjin Citizen - Mokpo City | 6 - 1 | W |
| 18.07.2026 | Dangjin Citizen - Jeonbuk Motors II | 2 - 0 | W |
| 15.07.2026 | Yongin City - Dangjin Citizen | 0 - 2 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 19.08.2026 | Dangjin Citizen - Jeonbuk Motors | 2 - 2 | D |
| 16.08.2026 | Bucheon FC 1995 - Jeonbuk Motors | 3 - 2 | L |
| 08.08.2026 | Jeonbuk Motors - Jeju United FC | 1 - 3 | L |
| 01.08.2026 | Jeonbuk Motors - FC Seoul | 0 - 0 | D |
| 25.07.2026 | Pohang Steelers - Jeonbuk Motors | 0 - 2 | W |
The upcoming match between Dangjin Citizen and Jeonbuk Motors is scheduled for 19.08.2026 10:00 in FA Cup. The listed venue is Jeonju World Cup Stadium, Jeonju. 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.
Dangjin Citizen recorded 7 wins, 2 draws and 1 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWWWDWWDLW. The averages are 2.40 goals scored and 0.80 goals conceded per match. Both teams scored in 60% of those matches, while 40% finished with over 2.5 goals. Jeonbuk Motors recorded 3 wins, 3 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLDWDLWLWD. The averages are 1 goals scored and 1 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals.
The highest stored values are: Under 2.5 goals — 80%; Under 3.5 goals — 80%; Over 0.5 first-half goals — 70%; Over 1.5 goals — 60%; Both teams to score — 30%. They are statistical indicators and are not automatically converted into a prediction.
The PMV3 model classifies the leading outcome as Dangjin Citizen to win with 72% confidence. The stored fair probabilities for home, draw and away are 72.19%, 17.19% and 10.62%. The model momentum difference is 61.58 points in favour of Dangjin Citizen. The input data quality score is 96/100. The stored price for the selected market is 1.25 with Bet365. The stored estimated EV is -9.76%. Despite the model probability, the price is marked NO_VALUE. The signal is therefore not treated automatically as a value bet.
1 active football Premium signals are stored for this fixture. At least one goal in the match (quota 17, score 81/100, 81.47% group success rate across 1905 observations).
The match between Dangjin Citizen and Jeonbuk Motors ended 2-2. The game produced 4 goals in total. The first half contained 2 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 70%. The actual outcome was BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 60%. The actual outcome was Over 1.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 80%. The actual outcome was Over 2.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 80%. 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 70%. 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.
The stored Premium market was At least one FT goal with quota 17. The actual market outcome was At least one FT goal. The Premium signal was confirmed.
Of 7 verifiable pre-match indicators, 3 aligned with the final result and 4 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.