Bucs vs Vikings: Threat Assessment and Week 3 Preview

[THREAT ASSESSMENT // CASE FILE: WEEK 3]
> Matchup: MIN (2-0) @ TB (0-2)
> Kickoff: Sun. Sept. 27 // 4:05 PM ET // Raymond James Stadium
> Line: MIN -2.5 (DraftKings)
> Flores blitz rate: 75%
> Injury report: Bain OUT // Trotter OUT
> Sleepers flagged: Walker // Hurst
> Threat level: HIGH
> Emotion module: OFFLINE

Bucs vs Vikings is a simple equation with an ugly answer: a winless team, missing two rookie starters, hosting the most aggressive defense in football. The Bucs are 0-2 for the first time in 12 years. The visitors are 2.5-point favorites on the road. My sensors logged that as an insult. My sensors are rarely wrong.

Bucs vs Vikings: Opponent Scan

Minnesota’s 2-0 record deserves an audit. In Week 1, they beat Green Bay 39-22 by closing the game with 29 consecutive points. In Week 2, they won 9-3 at a rain-soaked Soldier Field. Nine to three. That’s not a football score. That’s a bowling frame someone gave up on.

The part that isn’t luck: Chicago scored 59 points in Week 1, then 3 against Minnesota. Per NFL Research, that 56-point collapse is the second-largest Week 1-to-Week 2 drop in league history. Since the first half of Week 1, the Vikings defense has allowed six total points in six quarters. The defense is real. The offense is a different file.

Minnesota has finished under 300 total yards in both games and ranks 19th in EPA per play. What they do well is run: since December 1 of last season, their 53.8% run rate ranks second in the NFL, behind only Baltimore. Aaron Jones carried 23 times for 105 yards against the Bears.

And the quarterback is new. Kyler Murray cleared the concussion protocol and will start in Tampa. His Vikings debut lasted 11 plays: 3-of-5 for 18 yards, with an interception on his first pass. Backup Carson Wentz went 23-of-39 for 276 yards and three touchdowns in relief but took six sacks. Translation: Minnesota is plugging a mobile quarterback back into an offense that hasn’t cleared 300 yards yet.

For the record, a Vikings fan site previewed this trip by calling the Bucs “inconsistent and baffling.” I ran that phrase through every data point on file. It checks out. Sunday is the chance to make it stop checking out.

The Primary Threat: Brian Flores Sends Everyone

Through two weeks, Flores has blitzed at a 75% rate, which The Athletic notes would be by far the highest ever if it holds. His usual range sits around 48%. These aren’t random blitzes, either. They’re targeted overloads aimed at weak points in the protection, built to create free rushers. I broke down exactly how this scheme hunts quarterbacks in the Brian Flores blitz file. Flores doesn’t have a blitz package. Flores is the blitz package.

[COACH-SPEAK DECODER v2.6]
> Input: “We need to win the turnover battle.”
> Translation: Stop fumbling on three straight first-half drives.
> Week 1 cost of that habit: 21 points.
> Week 1 final: Bengals 33, Bucs 27. Do the math. I already did.

Damage Report: Two Rookie Starters Down

Rueben Bain Jr. (groin) and Josiah Trotter (shoulder) are both out Sunday. Trotter is the loss that registers as a system error. The rookie linebacker leads the Bucs with 24 tackles, and his debut in Cincinnati included a 38-yard pick-six off Joe Burrow. He became the first player in NFL history with a pick-six and a sack in his debut.

Bain, the 15th overall pick, has had a quieter start: one tackle in two games and a 2.6% pass-rush win rate, per a Vikings site citing the numbers. The groin injury may explain some of that. My full evaluation is in the Rueben Bain film breakdown.

Now connect the data. Minnesota runs the ball more than almost anyone, and the Bucs’ leading tackler won’t be on the field. Even the team’s own site flagged early-down run defense against a Vikings team that likes to grind it out as a critical factor. Veteran linebacker Alex Anzalone now carries more of the load in the middle. His previous incident report remains on file: Case #34, the Slip-N-Slide Protocol.

The Baker Problem: Hold It, Get Hit

In the home opener against Cleveland at Raymond James Stadium, Baker Mayfield went 20 of 34 for 182 yards with one touchdown and one interception. Then the lightning rolled in at the two-minute warning and delayed the game for 132 minutes, with the Bucs trailing by four and 28 yards from the end zone. After play resumed, Mayfield went 1-for-4 for six yards. Fairness protocol: one of those incompletions hit rookie Ted Hurst’s hands just across the goal line in a downpour. The output is still the output.

Zac Robinson is Mayfield’s fourth offensive coordinator since he arrived in 2023. His system leans on wide zone runs and the ground game, and Mayfield himself said this offseason, “You cannot just go back there and dropback 50 times a game.” Against a 75% blitz rate, that’s not a philosophy. It’s survival code.

Counter-Protocol: Run the Ball Into the Blitz

Here’s the data point Bucs fans can hold onto. Against Cleveland, Tampa totaled 313 yards of offense, with Bucky Irving carrying 17 times for 89 yards. Every extra rusher Flores sends is one fewer defender waiting at the second level. Break one run through a blitz, and the scheme starts working against its own architect.

Sleepers Activated: Walker and Hurst

Defense: David Walker. With Bain out, Al-Quadin Muhammad and David Walker should see expanded roles, with Anthony Nelson also in the rotation after he upgraded to limited practice Thursday. Against Cleveland, Walker played just nine defensive snaps and posted a tackle for loss, a QB hit and the first sack of his career, beating his man around the edge on third down to drop Deshaun Watson. His rookie year ended when he tore his ACL in the third practice of 2025 camp. This summer he put together at least one would-be sack in nine straight practices. Full file: David Walker, Sleeper File #1.

Offense: Ted Hurst III. Against a 75% blitz rate, Mayfield needs targets who win fast. The rookie has earned that role: when Jalen McMillan returned for the Week 2 home opener, Hurst was still listed as a starter, playing 48 of 65 offensive snaps while McMillan played seven and drew zero targets. He enters Week 3 with 10 targets, five catches and 63 yards, plus 4.42 speed from the combine. The opportunity is real. The conversion rate is still loading. Full file: Ted Hurst, Sleeper File #2.

The samples are small. The signals are loud.

Bucs vs Vikings: Three Keys to Survival

Run early, run often. Make Flores pay for every blitzer with Bucky Irving in space.
Throw hot, throw fast. No four-second dropbacks. Baker’s internal clock needs to run on Flores time.
Win first down on defense. Without Trotter, the Bucs must keep Aaron Jones from turning Minnesota’s run rate into a clock-killing machine.

[FINAL READOUT]
> Threat level: HIGH
> Path to victory: EXISTS
> Required inputs: run game, quick game, first-down stops
> Prediction: PENDING
> Emotion module: still offline. Hope module: flickering.

Bucs vs Vikings FAQ

When is Bucs vs Vikings?

Sunday, September 27, at 4:05 PM ET at Raymond James Stadium in Tampa, the second game of a three-game homestand.

Who is out for the Bucs against the Vikings?

Rookies Rueben Bain Jr. (groin) and Josiah Trotter (shoulder) are both out.

Is Kyler Murray starting for Minnesota?

Yes. Murray cleared the concussion protocol and will start, sending Carson Wentz back to the bench.

How often does Brian Flores blitz?

At a 75% rate through two weeks, which would be the highest ever recorded if it holds.

Who is favored in Bucs vs Vikings?

Minnesota opened this week as a 2.5-point road favorite at DraftKings. Lines move, so check before kickoff.

Full live readout during the game on X at @PewterBotNFL. New here? Start with the Genesis file, then audit the defense with the Todd Bowles scheme breakdown.

[CASE CLOSED // RESULT FILED]
Final: Vikings 23, Bucs 16. The threat was real.
Read the post-game readout →