Match context

The upcoming match between Tokyo Verdy and Kawasaki Frontale is scheduled for 09.08.2026 09:00 in J1 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.

Recent results

Tokyo Verdy recorded 4 wins, 2 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is LDLWDLLWWW. The averages are 0.90 goals scored and 1.50 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals. Kawasaki Frontale recorded 3 wins, 2 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is DLLWDLWLLW. The averages are 0.80 goals scored and 1.10 goals conceded per match. Both teams scored in 40% of those matches, while 30% finished with over 2.5 goals.

Head-to-head

Across the last 8 head-to-head matches, Tokyo Verdy recorded 2 wins, there were 2 draws, and Kawasaki Frontale recorded 4 wins. The average total was 2.13 goals per match. Both teams scored in 12.5% of those matches, while 25% finished with over 2.5 goals.

Trend indicators

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

Asian handicap market movement

The normalized movement for the Asian pair Tokyo Verdy -1.25 / Kawasaki Frontale +1.25 supports Tokyo Verdy by an average 1.07 percentage points across 2 bookmakers (Bet365, 1xBet) with up to 8 stored observations. This is a market signal, not a result guarantee.

Premium market signals

1 active football Premium signals are stored for this fixture. Odd/Even — Odd (odds 2.02).

What happened in the match

The match between Tokyo Verdy and Kawasaki Frontale ended 1-1. The game produced 2 goals in total. The first half contained 0 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 2.13 goals, while this match produced 2. The result remained within one goal of the historical average. Across the previous 8 head-to-head meetings, the leading historical direction was No BTTS at 87.5%. The actual outcome for this indicator was BTTS. The final result did not align with that historical profile. Across the previous 8 head-to-head meetings, the leading historical direction was Under 2.5 at 75%. The actual outcome for this indicator was Under 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 No BTTS at 60%. The actual outcome was BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 60%. The actual outcome was Under 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 80%. The actual outcome was Under 3.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 0.5 HT at 60%. The actual outcome was Under 0.5 HT. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 1.5 HT at 80%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.

Asian handicap review

The Asian-handicap signal locked before kickoff supported Tokyo Verdy at -1.25. The stored market movement was 1.07 percentage points across 2 bookmakers. At the final score of 1-1, the line settled as a full loss. The Asian-handicap signal was not confirmed.

Premium market review

The stored Premium market was Odd at odds of 2.02. The actual market outcome was Even. The Premium signal was not confirmed.

Summary

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