Misery Loves Company: Superbowl "Bad Beats"

Submitted by UNCWolverine on February 13th, 2023 at 10:53 AM

Here is your opportunity to share any of your bad beats from the game last night. I have two.

1. I only made one 'player to score first TD' bet, I mostly randomly chose Gainwell at 20 to 1.

Sanders is Philly's starting RB and I believe Scott actually came in for a play or two on the first drive before Gainwell even saw the field. But lo and behold when they got down near the goal line Gainwell comes into the game and in his first carry looked to score, the official even raised his arms. Of course upon review he was a half yard short, and Jalen scrummed in for the easy TD on the next play. 

 

2. I also thought Gainwell's over/under 21.5 yards rushing seemed pretty low. In the last 3 games he rushed for 48, 112, and 35 yards. Seemed like free money.

He had 13 at the half. Then he had a run where the boxscore briefly showed him at 22 for the game, then they frustratingly readjusted down to 21. No worries, he had the entire 4th Q to gain a yard, of course that never happened. 

I placed several other bets yesterday. But those two were by far my biggest payday opportunities, and both missed by literally half a yard. 

Ok, here's your opportunity to share your bad beat stories. Feel free to share any recent non-Superbowl stories as well. 

ThWard

February 13th, 2023 at 12:13 PM ^

I have been legit surprised by these “bad call” takes. Seems far more like people are just annoyed that a penalty was committed than that a penalty was called.

The ball being thrown 10 yards over his head isn’t relevant. The hold affected the timing of the route, etc, leaving little option other than to throw it away. 
 

I wish it hadn’t happened. Just seemed like a pretty clear call.

mi93

February 13th, 2023 at 4:32 PM ^

As a people that have been harmed (emotionally, at least, some probably financially) by the late swallowed whistle, I beg to differ with your conclusion. 

Not calling what should be called affects the outcome.  Do your best to get it right, every play, regardless of the clock/inning/chukka.

25dodgebros

February 13th, 2023 at 2:17 PM ^

Logged in just to upvote.  This type of holding occurred on virtually every pass play during the game on one receiver or another on both teams. It wasn't called until 1:50 left in the game on a crucial 3d down.  Call it the same way all game.  Don't eat the whistle at the end, just call it the same way for all 60 minutes.  Not an Eagles fan, was rooting for Chiefs to win anyway but I thought this was just a terrible job by the official who called it.  

Eng1980

February 13th, 2023 at 7:44 PM ^

I didn't get a good look on the replay but it appeared that Mahomes through the ball after he saw the hold to draw attention to hold.  Hence the delay from the refs.  Mahomes threw the ball in order to pressure the referee to call the hold.

I don't know about holding on every play, but I suspect that Mahomes knew he could get a call on that play if he threw the ball in the direction of the receiver being held.  

TheBlueAbides

February 13th, 2023 at 11:27 AM ^

Not as painful but was 20 yards short on mahomes passing yards as part of a five leg parlay that went 4/5. Maybe nearly as painful I took a prop bet that each team would have a TD and a FG in each half, missed by KC hitting the upright. Ended up winning a couple other small bets and ended up +$0.23!

ShadowStorm33

February 13th, 2023 at 12:39 PM ^

Not as painful but was 20 yards short on mahomes passing yards as part of a five leg parlay that went 4/5.

Same here, 18 yards short of hitting my parlay. Never in a million years would I have expected Mahomes not to hit 200 yards passing; Hurts hitting 200 was the one I was worried about. The fumble return TD and especially the punt return really screwed us...

bo_lives

February 13th, 2023 at 11:32 AM ^

My bad beat is the Fiesta Bowl, since watching the players slip all over the absolute garbage turf at that godforsaken stadium reminded me it's the same field.

Durham Blue

February 13th, 2023 at 1:29 PM ^

I hear you.  The half point in the betting line can be a killer.  I was getting beat a lot in NBA and college basketball this season on half points.  I said screw all that noise and lately I've been buying half point hooks.  They've been mostly worth it.

No bad beats for me in the Super Bowl.  I took the Chiefs +1 and moneyline.  But I lost my under 51 bet, which wasn't remotely close.

Ihatebux

February 13th, 2023 at 2:03 PM ^

I had "any player to score a TD on KO or Punt return".   It paid 13:1.   Ouch, why couldn't that guy dive for the last 5yds?

Also, had Kelce to get 25+ yds in 1st half and 2nd half.   Missed the second half by a couple yds.

Preacher Mike

February 13th, 2023 at 6:23 PM ^

I had the Eagles 4 and Chiefs 7 square in our squares pool, paying out every quarter. So it was 7-7 at the end of the first quarter and the fucking Eagles proceeded to score their second touchdown on the first play of the second quarter, costing me $200 for not doing it 9 seconds earlier.

jpo

February 13th, 2023 at 9:28 PM ^

I had a parlay that would have paid me $2500 on a $75 bet, and I needed Mahomes to throw for more than 225 yards as I nailed all the other legs. I thought that was the surest part of the bet. Turns out I was wrong. Didn’t help that he didn’t touch the ball in the first half…