← All games

Cubs @ Reds

Cubs
46
Final
Reds
Sat, May 24, 2025, 4:10 PM ET · MLB
Closing · ML -115 · SPR +1.5 · O/U 9

Archived game: the closing market as it stood at kickoff, kept permanently at this URL. Live odds, picks and the confluence table only run on games still on the slate.

Matchup summary

Final: Reds beat the Cubs 6-4 at home. The market closed with Cubs at -115 on the moneyline and the total at 9. The closing betting splits (tickets vs money), the opening line and the movement into kickoff are below.

Market data captured (closing state as of ) · source: Action Network's closing consensus for this game · permanent record at this URL

More on this matchup: Cubs betting trends · Reds betting trends · all MLB games

Cubs vs Reds betting splits

Where was the money on Cubs vs Reds?

MarketSideTicketsMoneyClosing line / odds
SpreadCubs78%83%-1.5 (+140)
Reds22%17%+1.5 (-163)
TotalOver46%47%O 9 (-120)
Under54%53%U 9 (-101)
MoneylineCubs68%69%-115
Reds32%31%-105

78% of spread tickets and 83% of spread money were on the Cubs, so the average Cubs bet was larger than the average Reds bet.

54% of total tickets and 53% of total money were on the under, so the under drew more tickets than money and the average over bet was larger.

68% of moneyline tickets and 69% of moneyline money were on the Cubs, so the average Cubs bet was larger than the average Reds bet.

Line movement

What was the closing line for Cubs vs Reds?

MarketOpeningClosingMove
Spread (Reds)+1.5+1.50
Total990

The Cubs opened -1.5 and closed -1.5: the spread has not moved.

The total opened 9 and closed 9: it has not moved.

Why the line moved

Why did the Cubs vs Reds line move?

The spread did not move from its opening number (Reds +1.5) even with 83% of the spread money on the Cubs. The total did not move from its opening number (9) even with 53% of the total money on the under. Splits describe where the money sits, not what will happen.

Splits describe where the money sits, not what will happen; there is no historical dataset for this sport yet.

Read more