matrisx.com
FixturesLeaguesTrack recordAccountPricing
TR·EN
TR·EN
FixturesLeaguesTrack recordAccount
Analytics platform · not a betting siteTrack recordThe last 7 daysLegal noticeRefund policyPrivacyiletisim@matrisx.comFollow on X
← Fixtures

Czech Liga · Czech-Republic · Relegation Group - 3

Zlin–Teplice

2–4

HT 2–1

Kick-off
Tuesday, 12 May 2026 at 15:30
Status
Match Finished
Venue
Stadion Letna, Zlin
𝕏Share on X

Goals and red cards

  • 5'⚽ZlinD. Machalik (assist: L. Bartosak)
  • 19'⚽ZlinTomáš Poznar (assist: Jakub Černín)
  • 25'⚽TepliceDaniel Mareček
  • 54'⚽TepliceM. Naprstek (assist: Daniel Mareček)
  • 72'TepliceB. Nyarko · red card
  • 81'⚽TepliceM. Radosta

Match statistics

Match statistics
ZlinTeplice
9Shots12
3Shots on target5
6Shots inside the box7
1Goalkeeper saves0
5Corners2
2Offsides0
52%Possession48%
385Passes355
307Accurate passes

What we expected, and what happened

  • Expected goals before kick-off: Zlin 1.34 · Teplice 1.11. On the pitch: 2-4.
  • Shots Zlin 9 · Teplice 12; on target 3 and 5.

Referee

D. Cerny→

3.81

yellows per match

0.38

reds per match

16

matches of data

Model prediction

Why this prediction?

  • ·The model puts the most likely outcome at 41.2%: “Zlin to win”. Second comes “Teplice to win” at 29.6%.
  • ·Behind that distribution are the expected goals: 1.34 for Zlin, 1.11 for Teplice.
  • ·The highest double chance value is 70.8% (12 — any result other than a draw).
  • ·These values were computed from 1,010 past matches.

This is a prediction, not a guarantee; a probability is not a certainty.

These sentences are built by a fixed template; every number in them comes straight from the model's computation, none invented while the text was written.

Zlin to win41.2%
Draw29.2%
Teplice to win29.6%

When the model has said 40–45% in the past, 2,356 of 5,296 predictions were correct (44.5%). Accuracy record →

(assist: M. Pulkrab)
  • 90'⚽TepliceM. Pulkrab (assist: M. Radosta)
  • 265
    16Fouls19
    3Yellow cards0
    0Red cards1

    The measurements our data provider sent for this match. A row that was not measured shows “—”; writing 0 into an empty field would claim we measured it and found none.

    Both teams to score
    52.5%

    When the model has said 50–55% in the past, 3,613 of 7,010 predictions were correct (51.5%). Accuracy record →

    Double chance

    1X — Zlin win or draw70.4%
    12 — any result other than a draw70.8%
    X2 — draw or Teplice win58.8%

    These three values add up to 200%, not 100% — and that is not a mistake. The options are not mutually exclusive; every outcome is counted in two of them. For the same reason 1X plus X2 exceeds 100% by exactly the probability of a draw (29.2%).

    First half

    Actual: 2–1
    Zlin lead at half-time34.5%
    Level at half-time43.0%
    Teplice lead at half-time22.5%

    First-half double chance

    1X — Zlin ahead or level77.5%
    12 — not level at half-time57.0%
    X2 — level or Teplice ahead65.5%

    These values are not a fraction of the full-match prediction; they come from a separate model trained on the first-half scores of 1010 matches. Its edge over the base rate is markedly smaller than the full-match model's — the measured figure is on the accuracy record. Read them more cautiously. First-half goal markets are not published because they failed to beat the base rate.

    Expected fouls and corners

    Fouls

    Zlin
    at least 13Actual: 16
    Teplice
    at least 14Actual: 19

    Corners

    Zlin
    at least 4Actual: 5
    Teplice
    at least 4Actual: 2

    These figures are set to hold in at least 60% of matches; in the rest the count comes in below them. No upper bound is stated — we make no "at most" claim. Yellow cards were measured and are not published: there our model did not beat the historical average.

    Goals market

    The 3+ goals prediction is not published for this match.

    The model gives a probability below the baseline (53.4%). In backtesting the model's edge in the "fewer goals" direction could not be confirmed; we don't publish an unconfirmed prediction.

    What these probabilities rest on

    Expected goals comes out of a team's attack weighed against its opponent's defence. A strong attack is damped when it meets a strong defence — which is why comparing the ratings on their own is misleading.

    How many goals Zlin score1.34

    Attack: Zlin score close to the league average.

    Opponent's defence: Teplice's defence is close to the league average (1.03×), so it doesn't move the expectation much.

    Result: These two effects give an expectation of 1.34 goals (including home advantage).

    How many goals Teplice score1.11

    Attack: Teplice score below the league average (26% fewer).

    Opponent's defence: Zlin concede 18% more than the league average, which pushes the expectation up.

    Result: These two effects give an expectation of 1.11 goals (including the away penalty).

    Most likely scorelines

    1–114.8%1–010.8%2–19.4%

    A single scoreline is always less likely than an outcome: “home win” is the sum of 1-0, 2-0, 2-1 and dozens more. So the most likely single score can be a draw while the most likely outcome is a home win; the two do not contradict each other.

    Ratings were computed from 1010 matches played in this league before kick-off; the team with fewer has 90 matches. No data from after the match was used. The model's track record is published unfiltered.

    Week 3 of the season. This prediction was computed from previous seasons. Summer transfers, budget changes and squad rebuilds aren't in the ratings yet — the model can only see that a team has been rebuilt once new results come in.

    We measured this: the bias is only pronounced in the opening week. In this week the model's overall accuracy does not separate from the rest of the season — that is, we found no measurable flaw. The one tendency across all opening weeks is that home wins are called slightly too often (said 43.0%, got 41.9%; n=583).

    This sample is small and not statistically established, which is why we do not correct the model for it. The correction we tried (pulling probabilities toward the league average) didn't win on holdout, so it wasn't added. Read opening-week predictions with a little more caution.