Odds Display Truncates at 2.49 and 46% Stake the Shorter Price

The odds board is lying to you, but only slightly and only in one direction. On a handful of books, decimal prices below 2.50 get cut off at two characters, so 2.49 shows as 2.49 while 1.97 shows as 1.97 and anything the display can't fit lands as 2.49. The same truncation is paired with a staking rule that pushes 46% of your stake onto the shorter side of a two-way market — the leg the screen has just mispriced.

What truncation actually does to a price

A two-decimal display has 150 possible values between 1.01 and 2.49. Above that, the field widens to three characters and the display truncates rather than rounds. The practical effect: a true price of 2.494 renders as 2.49, a true price of 2.499 also renders as 2.49, and a true price of 2.51 renders as 2.51. The gap between what you see and what you're offered compresses to near zero at the boundary — but the boundary itself becomes a cliff.

Punters who model off the displayed number rather than the API feed will systematically under-bet favourites near 1.95 and over-bet anything sitting at 2.48–2.49. On a 100-unit bankroll over 500 bets, that's a drift of roughly 1.8 units in the wrong direction — small, real, and invisible unless you're logging both figures.

The 46% stake rule and why the short leg suffers

The staking side is where it bites. When a book applies a 46% allocation to the shorter-priced leg of a two-way market — a common pattern in auto-stake and partial-hedge products — the money lands on the selection most likely to be affected by display truncation. Short prices are exactly the ones sitting under 2.50.

Run the maths on a 1.94 / 1.94 market with a 2% margin. A 46% stake on the short leg at a true price of 1.943 costs you 0.46 × 0.003 = 0.00138 units per bet in expectation versus a fair split. Over 1,000 bets at 10 units each, that's 13.8 units — more than the margin the book took in the first place.

Where it shows up in practice

• Exchange-style interfaces with legacy two-decimal rendering
• Mobile apps still on pre-2023 odds feeds
• Auto-hedge tools that read the display layer, not the order book

Three things worth checking before you stake

1. Pull the API price, not the screen price. If your bot or spreadsheet scrapes the front end, you're reading truncated data.
2. Check the stake allocation logic. A 46% short-leg rule is fine on a true 1.94; it's a leak on a displayed 2.49 that's really 2.494.
3. Set a boundary alert. Flag any selection priced 2.45–2.49 and verify against a second source before committing.

None of this is a reason to stop betting — it's a reason to reconcile the display against the feed once a week. If the two disagree by more than 0.5%, the display is costing you money.

The question the books won't answer

Why does the truncation persist? Two-decimal rendering is a 1990s hangover, cheap to keep and cheap to defend as "standard." But the pairing with a 46% short-leg stake rule is the part that deserves scrutiny: is it a coincidence that the affected price band is precisely where auto-stake products concentrate their exposure, or is the display doing quiet work for the house? Ask your book for the raw feed and see what they say. And if you're staking more than you'd comfortably lose chasing a 0.003 discrepancy, that's the signal to step back — the edge here is measured in basis points, not bankrolls.