Post‑mortem: Polymarket “Over 235.5” — Mavericks @ Lakers (2026‑02‑12)

Result: Lakers 124, Mavericks 104 → Total = 228 (Under by 7.5).
Your “Over” share resolved at $0.00, so the loss is consistent with the market resolving the Over as No.

1) What actually happened (box score facts)

Team-level drivers (why the game stayed under)

Key scoring math: despite the Lakers’ excellent shooting volume/efficiency (and 124 points), Dallas scoring collapsed (104). For a 235.5 over, you basically needed something like 124–112 or 118–118. You got 124–104.

Impact players (high leverage performances)

Lakers

• LeBron James: 28 PTS, 10 REB, 12 AST; 10–20 FG; 6–7 FT (35.4 min)
• Rui Hachimura: 21 PTS on 9–13 FG, 3–4 3PT
• Austin Reaves: 18 PTS, 6 AST; 7–9 FT
• Jaxson Hayes: 16 PTS on 8–10 FG, plus 3 STL (transition suppression for DAL)

Mavericks

• Naji Marshall: 19 PTS on 8–13
• Max Christie: 19 PTS on 7–12 (but -28)
• PJ Washington: 18 PTS, 7–8 FT
• Klay Thompson: 9 PTS (4–8), 4 TO
• Khris Middleton: 8 PTS on 3–11
• Tyus Jones: 3 PTS (1–3), -22
• Daniel Gafford: 2 PTS in 27.9 minutes

The “miss” for an Over bettor: Dallas didn’t have enough efficient creation. Their supporting scorers were fine, but several rotation pieces were low-output, and their offense didn’t keep pace.

2) Polymarket odds arc during the game (full in-game movement)

The available Polymarket history here is for win probability (Mavericks vs Lakers), not the game total market. It still tells you when the game state broke decisively (which matters for totals because blowouts often kill late-game scoring/pace).

Here’s the full chart (86 snapshots):

Key moments (interpreting the arc):

• Tip: Lakers already priced as clear favorite (~69%).
• Early swing: Lakers push it to ~81% (3:25 AM).
• Brief reversion: odds bounce back toward 66–71% range (some Dallas push).
• Second-half separation: Lakers reach ~84–88%, then the game drifts into “near over” territory (95–99%) well before final.

Why this matters for your Over: once a game’s win probability approaches “done,” the trailing team often gets worse shot quality, rotations change, and the leading team is happy to trade clock. That’s a classic “Over killer,” especially when the trailing team is the one struggling.

3) Entry timing: was $0.53 good vs how odds moved?

Because the history we pulled is win probability (not total), I can’t directly compare your Over 235.5 entry at $0.53 to the in-game Over price path.

That said, we can reason about the game script implied by the win odds:

• Lakers were favored from the jump and got to near-certain win by late game.
• That pattern often correlates with blowout risk, and blowouts are generally bad for Overs (especially if the losing side is inefficient).

So even without the total-market chart: paying $0.53 (implying ~53% to hit) looks like you likely overpaid for the true over probability given the blowout/efficiency risk profile that actually played out.

“Optimal entry” (conceptually)

For totals, optimal entries usually come from one of these:

• Pre-game when your number disagrees with the market and you have a strong pace/efficiency reason.
• Early-game dip if there’s a slow first 4–6 minutes (misses, turnovers) but nothing structurally wrong (no injury, no foul trouble, shots are good).

In this game, the “optimal entry” would likely have been only if the first few minutes were sluggish and Dallas shot quality looked normal. Instead, the eventual game state suggests the problem was Dallas’s ability to score efficiently for 48 minutes, not just random early variance.

4) Key factors that determined the Under (from box score)

A) Dallas offensive underperformance (the main reason)

• DAL 104 points is the entire story versus a 235.5 total.
• 7–26 from three (low makes, moderate attempts)
• 15 turnovers (possessions lost + transition chances for LAL)

B) Rebound disparity reduced Dallas extra possessions

• DAL: 28 rebounds (4 OREB) vs LAL: 44 (10 OREB)
• That’s a huge swing in 2nd chance / extended possessions. Overs love offensive rebounds; Dallas didn’t generate them.

C) Lakers scored efficiently, but not at a “both teams track meet” pace

• Lakers were very efficient (48–86 FG) but only 10 made threes.
• If you’re betting a high total like 235.5, you typically want either:
  • both teams hot from 3, or
  • both teams living at the line, or
  • both teams playing fast with low turnovers.
• This game had one good offense and one struggling offense, plus turnovers/rebounding issues for DAL.

5) What you likely missed pre-game (signals to check next time)

I didn’t pull pre-game injury reports / recent form here (you didn’t request those tools), but the box score itself reveals red flags you could have hunted before locking an Over:

Signal 1: “Does Dallas have enough reliable creation tonight?”

Look at who produced for Dallas:

• No dominant high-usage scorer showed up in the leaders list.
• Several rotation players posted single-digit points (and some very inefficient lines like 3–11).

Pre-game data that would have mattered: who was available (primary creators), and whether Dallas had been generating paint pressure / rim attempts / 3PA volume recently.

Signal 2: Blowout fragility (favorite controls the game)

The market had Lakers as a clear favorite from tip (win odds ~69% immediately). When one side is strongly favored, your Over is more dependent on the underdog’s competence.

Pre-game data that would have mattered: underdog road offense, and performance vs top defenses / in losses (does their scoring crater?).

Signal 3: Possession stability (turnovers + rebounding)

Dallas had 15 TO and only 4 OREB. That combination is deadly for Overs.

Pre-game data that would have mattered: team turnover rates and offensive rebounding profile, plus matchup (does the opponent force turnovers / dominate defensive glass?).

Signal 4: Market movement you may have ignored

Even though we don’t have the total-market history in this pull, the general checklist is:

• Did the total tick down pregame (sharp Under)?
• Any late injury/limit news that typically hits offense more than defense?

Data that would have changed your mind: a clear pregame under steam (e.g., 235.5 → 233.5) or confirmation that Dallas’s main creator(s) were limited/out.

6) One concrete actionable lesson

Don’t bet high totals primarily on “one team can score.”
Before taking an Over like 235.5, require a checklist item that answers:

“If one team is favored and likely to control game script, can the underdog still produce 110+ efficiently in that matchup?”

In this game, the box score screams that the underdog (Dallas) was the weak link: turnovers, no extra possessions, modest 3PT output, and not enough top-end scoring to keep the total afloat.

If you apply just that single rule, it filters out a lot of “looks like an Over on paper” spots that actually have blowout + underdog scoring collapse risk baked in.