Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 03.04.2026 | KRC Genk II - Lokeren-Temse | 2 : 2 |
| 14.12.2025 | Lokeren-Temse - KRC Genk II | 2 : 2 |
| 02.03.2025 | KRC Genk II - Lokeren-Temse | 1 : 2 |
| 03.11.2024 | Lokeren-Temse - KRC Genk II | 4 : 0 |
| Date | Match | Score | Res |
|---|---|---|---|
| 21.08.2026 | Lokeren-Temse - AS Eupen | 2 - 1 | W |
| 14.08.2026 | Seraing United - Lokeren-Temse | 0 - 2 | W |
| 09.08.2026 | Roeselare Daisel - Lokeren-Temse | - | |
| 08.08.2026 | Lokeren-Temse - UMM Salal | 5 - 0 | W |
| 01.08.2026 | Lokeren-Temse - Dender | 3 - 0 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 25.08.2026 | KRC Genk II - MVV | 6 - 0 | W |
| 23.08.2026 | KRC Genk II - Liège | 2 - 3 | L |
| 19.08.2026 | Oud-Heverlee Leuven II - KRC Genk II | 2 - 2 | D |
| 15.08.2026 | AS Eupen - KRC Genk II | 4 - 1 | L |
| 08.08.2026 | Zelzate - KRC Genk II | 1 - 2 | W |
The upcoming match between Lokeren-Temse and KRC Genk II is scheduled for 28.08.2026 18:00 in Challenger Pro League. The listed venue is Daknamstadion, Lokeren. 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
Lokeren-Temse are in position 2 with 6 points. The stored form sequence is WW. KRC Genk II are in position 14 with 0 points. The stored form sequence is LL.
Lokeren-Temse recorded 7 wins, 1 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWWWLWLWWD. The averages are 2.80 goals scored and 0.70 goals conceded per match. Both teams scored in 40% of those matches, while 70% finished with over 2.5 goals. KRC Genk II recorded 6 wins, 2 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLDLWWWWWD. The averages are 3.40 goals scored and 1.70 goals conceded per match. Both teams scored in 80% of those matches, while 90% finished with over 2.5 goals.
Across the last 4 head-to-head matches, Lokeren-Temse recorded 2 wins, there were 2 draws, and KRC Genk II recorded 0 wins. The average total was 3.75 goals per match. Both teams scored in 75% of those matches, while 100% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 90%; Over 2.5 goals — 80%; Over 0.5 first-half goals — 70%; Both teams to score — 60%; Under 3.5 goals — 60%. The stored corner indicators are: average total corners — 10.30; over 7.5 corners — 100%; over 8.5 corners — 100%; over 9.5 corners — 100%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Lokeren-Temse -0.25 / KRC Genk II +0.25 supports Lokeren-Temse by an average 3.14 percentage points across 3 bookmakers (Pinnacle, Bet365, 1xBet) with up to 29 stored observations. This is a market signal, not a result guarantee.
1 active football Premium signals are stored for this fixture. At least one goal in the match (quota 19, score 81/100, 81.44% group success rate across 1417 observations).
The discipline profile for Lokeren-Temse at home is based on 1 matches. The team averages 2.00 yellow cards, 0.00 red cards and 2.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 100.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 0.0%. Season card data is available for 2 of 2 completed matches (100.0% coverage).
The match between Lokeren-Temse and KRC Genk II ended 2-4. The game produced 6 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.75 goals, while this match produced 6. 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. Across the previous 4 head-to-head meetings, the leading historical direction was Over 2.5 at 100%. The actual outcome for this indicator was Over 2.5. The final result aligned 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 90%. 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 80%. 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 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 70%. The actual outcome was Over 1.5 HT. The stored trend was not confirmed by the result.
Before kickoff, the discipline profile for Lokeren-Temse at home was based on 1 matches, with averages of 2 yellow cards, 0 red cards and 2 total cards per match. In this game, Lokeren-Temse received 0 yellow cards and 0 red cards, 0 in total. That was 2 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 0%.
The Asian-handicap signal locked before kickoff supported Lokeren-Temse at -0.25. The stored market movement was 3.14 percentage points across 3 bookmakers. At the final score of 2-4, the line settled as a full loss. The Asian-handicap signal was not confirmed.
The stored Premium market was At least one FT goal with quota 19. The actual market outcome was At least one FT goal. The Premium signal was confirmed.
Of 11 verifiable pre-match indicators, 7 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.