MLB · Baseball · Jul 19, 2026 14:10 EDT

Kansas City RoyalsvsSan Diego Padres

Royals–Padres Asian handicap: Fliff pricing sits 48.4% above sharp consensus, 1 hours to first pitch

What happened: Final score: 2–19. The edge paid: the flagged side won, returning +1.56 units on a flat 1-unit stake. The market agreed with the signal: the price closed +0.2% better than where the edge was flagged (positive closing-line value — the strongest sign the edge was real). For the record: the flagged price stayed live for about 2 hours after detection before the edge closed.
Offered at Fliff2.40Fair price1.62+48.4% above fair

Omenizer detected 14 bookmakers pricing this bet above the no-vig fair near close — this story covers one of them. Members see the full board, live.

The setup — the analysis as published at detection, written 1.5 hours before start and frozen for the record. The market it describes has since closed; the outcome is above.

As Kansas City Royals and San Diego Padres prepare for first pitch (MLB), the Asian handicap market shows a fracture: Fliff is quoting decimal odds of 2.40 on one side, a 48.4% overstatement relative to where sharp operators have anchored their pricing. The gap is live right now, not historical; odds continue to shift as this page loads.

The consensus behind this edge rests on 2 independent sharp sources, ensuring the fair value it represents isn't tied to any single operator's calculation.

This signal aligns with 3 patterns tracked in the historical Playbook, with the best-performing variant closing at +10.9% ROI on settled positions.

The segment—baseball Asian handicap, mid-range odds—has a database record: 86 settled signals have returned +31.4% ROI across our tracked bets.

Mispricings in this market category typically compress fast: data shows these edges usually persist for roughly 1 minutes before the market reprices toward consensus.

Historical, aggregate data on settled bets — not betting advice and not a guarantee. Markets adapt; edges fade; variance is real.

AN EXAMPLE OF THE MEMBER VIEW · what members see on a bet like this — shown for a different, already-settled match PRO
Cincinnati Reds vs St. Louis Cardinals · MLB · Baseball — flagged side Under 8.5 @ 2.15
79 Omen Score

This is the complete breakdown members get for every live signal. The example below is a DIFFERENT match, already settled — its market is closed, so full disclosure costs nothing. Everything is real except values marked 🔒, which are members-only (decoy digits shown).

Why this bet
+4.4%
Entry edge
+0.9%
Edge near close
+0.1%
Risk-adjusted edge
2.13
Fair price (no-vig)
2.25
Entry odds
Quality
80/100
Confidence
9
Sharp books
Prime signal
Class
Market state: Recreational consensus (no sharp anchor) · priced from: Market reference
Sizing
1.55%
Recommended stake
0.8%
Full Kelly (theoretical max)
Insights
Rec-book consensus only — no sharp anchor.High confidence + meaningful price gap — best risk-adjusted segment.
A sample of bookmakers on this betnear close — every price against the same no-vig fair
BookmakerOddsVs fair
Hard Rock2.15+0.9%
espn-bet2.10-1.4%
Hard Rock2.10-1.4%
1xBet2.08-2.3%
Matchbook2.08-2.3%
sport8882.05-3.8%
betparx1.96-7.9%
Bally Bet1.96-7.9%
BetRivers1.96-7.9%
PMU1.83-14.3%
Risk & profitability profile
Heavy favoriteFavoriteCoin flipUnderdogLongshot
2.15 odds → 47% implied win probability
47%
Fair win probability
+4.9% 🔒
Expected ROI (model)
+8.0% 🔒
Cohort realized ROI
The endingthe part only a settled signal can show
Detected Aug 17, 18:51 UTC at 2.25 (+4.4% edge) → fair price at close 2.13 → closing-line value +1.1%
✅ Settled: WON · +1.25 units
A real, settled example — not a typical-results claim (read this signal's full story). The live breakdown for Kansas City Royals vs San Diego Padres is on the member board now · unlock with Pro
See the live board — free account

The strategies behind signals like this · More stories

Record settled · last updated Jul 19, 2026 21:15 UTC · How these numbers are made: methodology · the dataset — fair prices shown are margin-free. Spotted an error? Request a correction (include this page's URL).