Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 01.02.2026 | Racing de Veracruz - Tapachula | 2 : 1 |
| 16.09.2025 | Tapachula - Racing de Veracruz | 0 : 1 |
| 23.03.2025 | Tapachula - Racing de Veracruz | 0 : 0 |
| 10.11.2024 | Racing de Veracruz - Tapachula | 1 : 1 |
| Date | Match | Score | Res |
|---|---|---|---|
| 29.08.2026 | Tapachula - Racing de Veracruz | 0 - 4 | L |
| 19.04.2026 | Tapachula - Tritons Vallarta | 1 - 1 | D |
| 15.04.2026 | Tritons Vallarta - Tapachula | 1 - 0 | L |
| 12.04.2026 | Tapachula - Mexicali FC | 0 - 0 | D |
| 28.03.2026 | Cañoneros Marina - Tapachula | 1 - 2 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 29.08.2026 | Tapachula - Racing de Veracruz | 0 - 4 | W |
| 25.04.2026 | Racing de Veracruz - Tritons Vallarta | 0 - 0 | D |
| 25.04.2026 | Racing de Veracruz - Deportivo Zap | 0 - 2 | L |
| 22.04.2026 | Deportivo Zap - Racing de Veracruz | 0 - 0 | D |
| 22.04.2026 | Tritons Vallarta - Racing de Veracruz | 0 - 0 | D |
The upcoming match between Tapachula and Racing de Veracruz is scheduled for 29.08.2026 22:00 in Primera Premier. 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.
Tapachula recorded 5 wins, 3 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is DDWWWDLWWL. The averages are 2.30 goals scored and 1.40 goals conceded per match. Both teams scored in 80% of those matches, while 80% finished with over 2.5 goals. Racing de Veracruz recorded 7 wins, 2 draws and 1 losses across the last 10 completed matches. The newest-to-oldest result sequence is LDWDWWWWWW. The averages are 2.20 goals scored and 0.60 goals conceded per match. Both teams scored in 40% of those matches, while 60% finished with over 2.5 goals.
Across the last 4 head-to-head matches, Tapachula recorded 0 wins, there were 2 draws, and Racing de Veracruz recorded 2 wins. The average total was 1.50 goals per match. Both teams scored in 50% of those matches, while 25% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 80%; Under 3.5 goals — 80%; Over 0.5 first-half goals — 70%; Under 2.5 goals — 60%; Both teams to score — 40%. They are statistical indicators and are not automatically converted into a prediction.
The match between Tapachula and Racing de Veracruz ended 0-4. The game produced 4 goals in total. The first half contained 0 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 1.5 goals, while this match produced 4. 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 Under 2.5 at 75%. The actual outcome for this indicator was Over 2.5. The final result did not align with that historical profile.
Before kickoff, the stored trend indicated No BTTS at 60%. The actual outcome was No 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 2.5 at 60%. 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 Under 0.5 HT. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 1.5 HT at 70%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
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.