Match context

The upcoming match between SJK and Gnistan is scheduled for 07.08.2026 16:00 in Veikkausliiga. The listed venue is OmaSP Stadion, Seinäjoki. 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
SJK are in position 11 with 14 points after 18 matches. The season record is 4 wins, 5 draws and 9 losses. The goals record is 22 scored and 27 conceded. The stored form sequence is LLLWD. Gnistan are in position 4 with 28 points after 18 matches. The season record is 8 wins, 4 draws and 6 losses. The goals record is 27 scored and 22 conceded. The stored form sequence is WWWLD.

Recent results

SJK recorded 3 wins, 2 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLLLWDDLWL. The averages are 1.50 goals scored and 1.50 goals conceded per match. Both teams scored in 70% of those matches, while 70% finished with over 2.5 goals. Gnistan recorded 6 wins, 2 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is LWWWLDDWWW. The averages are 1.70 goals scored and 0.90 goals conceded per match. Both teams scored in 50% of those matches, while 40% finished with over 2.5 goals.

Head-to-head

Across the last 8 head-to-head matches, SJK recorded 5 wins, there were 1 draws, and Gnistan recorded 2 wins. The average total was 3.63 goals per match. Both teams scored in 62.5% of those matches, while 75% finished with over 2.5 goals.

Trend indicators

The highest stored values are: Over 1.5 goals — 80%; Over 0.5 first-half goals — 70%; Under 3.5 goals — 70%; Both teams to score — 60%; Over 2.5 goals — 50%. They are statistical indicators and are not automatically converted into a prediction.

Premium market signals

2 active football Premium signals are stored for this fixture. Odd/Even — Odd (odds 2). At least one goal in the match (quota 17, score 82/100, 81.50% group success rate across 1757 observations).

What happened in the match

The match between SJK and Gnistan ended 2-2. The game produced 4 goals in total. The first half contained 3 goals. The following review compares the final result only with historical data, trend values and Premium signals locked before kickoff.

Comparison with the head-to-head history

The historical profile from 8 head-to-head meetings averaged 3.63 goals, while this match produced 4. The result remained within one goal of the historical average. Across the previous 8 head-to-head meetings, the leading historical direction was BTTS at 62.5%. The actual outcome for this indicator was BTTS. The final result aligned with that historical profile. Across the previous 8 head-to-head meetings, the leading historical direction was Over 2.5 at 75%. The actual outcome for this indicator was Over 2.5. The final result aligned with that historical profile.

Which pre-match trends were confirmed and which were not

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 80%. The actual outcome was Over 1.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 70%. 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.

Premium market review

The stored Premium market was Odd at odds of 2. The actual market outcome was Even. The Premium signal was not confirmed. 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.

Summary

Of 10 verifiable pre-match indicators, 7 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.