Skip to content
View in the app

A better way to browse. Learn more.

TalkBears Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

All Activity

This stream auto-updates

  1. Today

  2. Bears are a top 10 team, Packers are a bottom 10 team. Packers are closer to the Jets than they are to either the Eagles or Panthers. The Bears can't lose this game. Most simulations are saying Bears 24-17 at the worst. Others say 27-13 or 14.
  3. Only 3 undefeated teams left, KC, SF, and MIN. MIN is a paper tiger. KC has two 3pt wins. SF is the most legit team so far. Bears should be right there with them.
  4. Funny thing is, I'm not going to fault him for any of those three. The TD was not easy. Sure, he had it in his hands, but got broken up before he could secure it to his body. I'm not sure what important data would say on success, but I would guess 60/40 in favor of TD. On the punt, I call that an effort related brain fart. The field goal thing was widely scrutinized. People analyzed the play and said Cole didn't move either, leading them to text slower. On that outside position, they can't see the ball or their fellow linemen. The most important thing I see is his early involvement in 13 personnel. BJ is trusting him to make key blocks and he is succeeding. Our TE's are massive in the run game. We have a gross display of options on offense.
  5. Good point. I don't know how much he interacted with the defensive players, but Hutchinson cap hit grows to $54M in 2029. They backloaded it to go all in the next two years. After that, they will have to shed salary. Goff goes to $62M next year, then $69M in 2028. Half their cap next year is in Goff, St. Brown, and Sewell already.
  6. adam replied to adam's topic in Bearstalk
    His mistakes have just been magnified because they have been so noticeable. Drops an easy TD, jumps on a perfect punt for no reason causing a touchback, not even attempting to block on FG try, not following blockers on designed screen, etc.
  7. Rookies are gonna make mistakes and hopefully learn. He will be a big contributor on this team for years to come.
  8. Agreed. Watch the Baldy video I posted this morning. He's really good in the run game.
  9. I dont think Rousch has been all that bad. People are over analyzing his every play. He has played about as equal as Kmet and has only played 4 games.
  10. I'll propose we trade for Jeffrey Simmons. We send them Grady Jarrett, for their locker room, and next year's first...
  11. AZ54 replied to adam's topic in Bearstalk
    True. After years searching for one QB we can win games with we now have 3.
  12. adam replied to adam's topic in Bearstalk
    Bears QBR so far this season, week by week: 1 - Williams 92.3 2 - Williams 70.3 3 - Keenum 74.1 4 - Bagent 75.1 4 straight games with the primary QB with a QBR over 70 is impressive. 3 out of 4 weeks with a QB in the top 10 in QBR. Coaching matters.
  13. adam replied to adam's topic in Bearstalk
    Definitely, Thieneman was the correct pick, so was Muhammad. Actually he probably should've been the Rousch pick. That one is looking like a whiff.
  14. The only return would be possible Cap trade off. I would never expect the Bears to do that with how important a backup QB is. Does Keenum return next season? He was going to retire until BJ called him.
  15. AZ54 replied to Mongo3451's topic in Bearstalk
    With Caleb under repair I don’t see anyway they trade Bagent mid season. First off the trade value won’t change between now and the offseason but you can’t get your ROI until next year regardless. Unless it’s a trade for a player.
  16. adam replied to Mongo3451's topic in Bearstalk
    I don't think the Bears will be sellers at the deadline. I could see an Edge or CB. Jaylon and Stevenson have been really bad.
  17. Cronin said Caleb not expected to practice this week, so hopefully next week.
  18. Yesterday

  19. I haven't seen the article, but Brad Biggs believes the Bears will be in play for a defensive player. Other news, Marcus Davenport requested to be released from the practice squad.
  20. I am always thinking both today and tomorrow, which is sometimes too much. Right on. I've been mocking just that.... DE, DT, CB, OT, RB, and QB. RB probably don't happen with Swift extended and the 3rd back needs to be ST stud first and good all around in run, catch, and blocking. Things can change if they carry 4 RBs.
  21. Just saw that Monongai is ruled ‘day to day’ with his thumb. So no real issues there. Been seeing some speculation about Swift and his knee/leg(?) and aside from his fumble maybe why he sat out the rest of the game yesterday?
  22. The trade deadline is November 10th. Ideas and rumors are already beginning. I believe we will be a player somehow. Maybe Bagent to a team, in contention, with a QB issue. Perhaps a new talent for the D. Maybe Braxton, if he comes back healthy. (His timeline may be iffy) Bring it!
  23. The funniest thing ever would be Bagent taking the first snap and then Caleb runs out on the field to takeover.
  24. If he's not starting, it's highly doubtful he plays.
  25. Game first, but trade value is what it is. Bagent can start in this league and has already been told that he'll get his shot somewhere. Your team begins to become special when you afford to trade your UDFA QB for a second round pick. It shows that you are developing your players and coaches. (Note: Declan Doyle and Randal El) I can honestly see us drafting all the levels of the defense in the first two days. Add a RB and OL. Also, add QB due to Bagent leaving to be a starter.
  26. adam replied to adam's topic in Bearstalk
    Mission Accomplished!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.