Match context

The upcoming match between Kansas City W and Racing Louisville W is scheduled for 30.07.2026 00:00 in NWSL Women. 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
Kansas City W are in position 6 with 25 points after 16 matches. The season record is 8 wins, 1 draws and 7 losses. The goals record is 23 scored and 23 conceded. The stored form sequence is DLWWW. Racing Louisville W are in position 16 with 8 points after 15 matches. The season record is 3 wins, 2 draws and 10 losses. The goals record is 18 scored and 28 conceded. The stored form sequence is DLLLL.

Recent results

Kansas City W recorded 5 wins, 1 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is LDLWLWWLWW. The averages are 1.60 goals scored and 1.10 goals conceded per match. Both teams scored in 30% of those matches, while 70% finished with over 2.5 goals. Racing Louisville W recorded 4 wins, 2 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDLLLWDLWW. The averages are 1.10 goals scored and 1.40 goals conceded per match. Both teams scored in 40% of those matches, while 50% finished with over 2.5 goals.

Head-to-head

Across the last 10 head-to-head matches, Kansas City W recorded 5 wins, there were 1 draws, and Racing Louisville W recorded 4 wins. The average total was 3.10 goals per match. Both teams scored in 40% of those matches, while 50% finished with over 2.5 goals.

Trend indicators

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

PMV3 model and market price

The PMV3 model classifies the leading outcome as Kansas City W 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 Kansas City W. 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.

What happened in the match

The match between Kansas City W and Racing Louisville W ended 5-1. The game produced 6 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 previous 10 head-to-head meetings averaged 3.1 goals, while this match produced 6. The final scoring profile differed by more than one goal from that average. Across the previous 10 head-to-head meetings, the leading historical direction was No BTTS at 60%. The actual outcome for this indicator was BTTS. The final result did not align with that historical profile.

Which pre-match trends were confirmed and which were not

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 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 60%. 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 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 60%. 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.

Summary

Of 8 verifiable pre-match indicators, 3 aligned with the final result and 5 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.