2010 NFL Week 5 Beatpaths Power Rankings

Hey folks! Kenneth here, with more rankings coming at ya! Lots of weird stuff in the graph this time, leading to some interesting movement. The season is now at the point where stuff happens, so let’s get to it!

You can see the graph generating these rankings here.

Rank Team Notes Last Week EdgePower

1

(Beat DEN) Another win for the number one team changes little. It makes their position stronger, but when you’re #1 already how much stronger can you get? (I know, a lot.)

1

96.08

(47 – 0) / 51

#1 – #6

2

(Bye) Pittsburgh spent their bye staying strong as well. The rematch with Baltimore is going to be very interesting, beatpaths-wise.

2

82.35

(34 – 1) / 51

#2 – #11

3

(Beat KC) Now we get to some interesting stuff. Indy sheds its only remaining beatloss not by anything they did, but because the Giants beat Houston, creating a 3 team loop (IND=>NYG=>HOU=>IND). This would have blown up the 6 team beatloop from last week (GB=>PHI=>JAC=>IND=>NYG=>CHI=>GB) as well, which would give Indy back its’ loss to Jacksonville. But here the Colts helped themselves–their win over Kansas City created a replacement 4 team beatloop (KC=>SD=>JAC=>IND=>KC), which helped stave off the beatloss. Of course, it also cost the Colts a beatwin over the previously undefeated Chiefs, but you can’t have everything, now, can you?

6

68.63

(19 – 0) / 51

#1 – #17

4

(Lost to BAL) Broncos rising even on the loss, mainly by the rise by the Colts giving them room to breathe. What is causing this ascent? It’s a specific team rising–that both horsies have a path too–that is giving them a better edgepower. Who could it be? (CLIFFHANGER!)

7

65.69

(18 – 2) / 51

#3 – #18

5

(Beat DAL) I’ll tell you this much–the path is being maintained by the Titans win over the mystery team. Meanwhile, I feel like the Titans were making a lot of mistakes to let the Cowboys back in that game. In one sense, they shouldn’t have had that much trouble with Dallas; on the other hands, part of being a good team is not doing that.

12

61.76

(17 – 5) / 51

#5 – #19

6

(Beat CLE) Atlanta drops not so much because of anything they did, but because other teams look more impressive. Admit it–you weren’t very impressed by the way they limped over Cleveland.

4

59.80

(12 – 2) / 51

#3 – #23

7

(Beat MIN) Jets coming down with a case of what the Falcons had. Beating Minnesota doesn’t even really matter so much–they already had a beatpath to them. Not surprising, really, given how badly the Vikes have looked–but that’ll come later.

5

59.80

(11 – 1) / 51

#2 – #25

8

(Bye) Well, the Pats sure have changed themselves over the bye, haven’t they? I would not have guessed that the moves that have happened would have. I can kind of get behind trading Moss for essentially a younger dominant receiver. But…well, guess which word in “younger dominant reciever” doesn’t fit Deion Branch.

8

54.90

(7 – 2) / 51

#3 – #26

9

(Beat NO) Arizona moves up a bit mostly due to shifting graph dynamics underneath them giving them some more beatpaths. I usually try to avoid wishing bad for players but if Max Hall ends up being anything fans of pretty much every team without a franchise QB are going to have to listen to morons complain about how other teams can find QBs without even drafting them! Ugh.

13

54.90

(8 – 3) / 51

#4 – #25

10

(Beat HOU) If you guessed the big riser causing all the trouble was the Giants, congratulations! You win nothing! Yes, the Giants win over Houston created that aforementioned 3 team beatloop with Indy, which broke up the 6 team beatloop that was taking away their win over the Bears. The restoration of that path (and ones underneath it) gave New York a lot more teams underneath them. That benefits them and, of course, the teams above them.

23

54.90

(11 – 6) / 51

#6 – #23

11

(Lost to NYG) Of course, for every big winner there is a big loser. And losing a beatwin over the Colts is very big indeed.

3

53.92

(4 – 0) / 51

#1 – #28

12

(Lost to IND) Little changes for the Chiefs–they have 1 fewer beatwin over an unimpressive team now. Beating Houston this week would probably help.

9

51.96

(2 – 0) / 51

#1 – #30

13

(Beat CAR) You would think that a 6/16 for 32 yards and 4 INTs would pretty much damn a QB. But I am serious when I say that Collins looked even worse than those numbers. When he wasn’t making flat-out bad decisions, he was completely unable to hit the receivers with passes. There were several easy throws that he just couldn’t make. I think it’s time for retirement, Todd. Oh, and the breakup of the big 6 team beatloop means CHI=>GB comes back which boosts the Bears somewhat but gives them back a lot of beatlosses so it all evens out.

11

51.96

(9 – 7) / 51

#7 – #24

14

(Beat CIN) Beating the Bengals boosts the Bucs a bit. I am enjoying the Bucs, mainly because I picked them to do well before the season (in my head, at least) and it makes me feel smart in my own little universe.

16

51.96

(4 – 2) / 51

#3 – #29

15

(Lost to OAK) Seriously, Chargers? Really? Anyway…this loss creates a 3 team beatloop with the Cardinals (ARI=>OAK=>SD=>ARI). That busts up a 4 team beatloop from last week of (SD=>ARI=>STL=>SEA=>SD), but it’s okay because another 4 team beatloop (JAC=>DEN=>SEA=>SD=>JAC) holds off the loss to the Seahawks. Meanwhile, as you might remember from above the Colts’ win creates another 4 team beatloop (KC=>SD=>JAC=>IND=>KC), which loops away the loss to the Chiefs. Carry the 3, and…the Chargers have no relationships to any other team in the graph. Fair enough, but ask the Jaguars how that worked out for them this week.

19

50.00

(0 – 0) / 51

#1 – #32

16

(Beat GB) Beating GB is nice, but the big deal for the Redskins is the Lions’ win over St. Louis. That creates 2 separate 4 team beatloops (DET=>STL=>WAS=>PHI=>DET & DET=>STL=>WAS=>GB=>DET), which takes away the loss to the Rams but also takes away two of their wins. Add in the WAS=>DAL=>HOU=>WAS beatloop that carried over from last week, and the Redskins are also floating on their own with no relationships to any team. That let them jump 13 spots in these rankings. But the ties to those teams down near the bottom can easily come back; I’d guess that next week sees them drop back down there.

29

50.00

(0 – 0) / 51

#1 – #32

17

(Lost to ARI) Arizona and New Orleans were actually pretty comparable teams in terms of the graph, so the loss doesn’t hurt a great deal. Is it just me, or are a lot of commentators not using the words “Pierre Thomas” when discussing the Saints’ woes?

14

49.02

(4 – 5) / 51

#5 – #28

18

(Bye) Dolphins didn’t play a game, so nothing happened. This is what Beatpaths would sound like if we did this stuff year round.

18

49.02

(3 – 4) / 51

#4 – #29

19

(Lost to WAS) Again, the problem isn’t with with losing to Washington–that got looped away. The problem was the Giant’s win over Houston breaking up that 6 team loop that got rid of their loss to the Bears. That forced them under Chicago, which gave them a lot of beatlosses, where before they had none.

10

47.06

(5 – 8) / 51

#8 – #28

20

(Beat SD) The win gets looped away, but takes with it a loss to the Cardinals. That helps–now the Raiders need to get some more teams underneath them.

24

46.08

(3 – 7) / 51

#7 – #29

21

(Lost to TB) I think it’s clearly time to give up on Carson Palmer being a big time QB again. I feel bad, because I like Carson Palmer. I think it helps that he was at USC before they got really annoying. I will REALLY feel bad if Mark Sanchez ends up being the most successful active USC QB.

21

45.10

(1 – 6) / 51

#6 – #31

22

(Lost to ATL) Speaking of guys who need to retire (I was, 9 teams ago!): when Seneca Wallace is clearly outplaying you–as a pocket passer, no less–it’s probably time to hang them up, Jake.

22

44.12

(0 – 6) / 51

#6 – #32

23

(Beat SF) Beating the 49ers? Meh. It’s the new 4 team beatloop from DET=>STL shedding the Eagles’ loss to the Redskins that has boosted them up.

30

44.12

(3 – 9) / 51

#9 – #29

24

(Beat BUF) Jacksonville returns to the graph with a beatloss to the Eagles reappearing and their new beatwin over the Bills in hand. Guess what? Being under the Eagles is more bad than being above the Bills is good.

17

41.18

(1 – 10) / 51

#10 – #31

25

(Lost to TEN) I guess people are billing this week as Dallas’ last chance to salvage their championship season? I can help you out with that one–it’s not happening.

20

41.18

(0 – 9) / 51

#8 – #32

26

(Lost to DET) The loss to the Lions gets looped away but costs the win over the Redskins. This is a really confusing loss. The Rams have been playing well enough to not get blown out by anyone, much less the Lions. I can understand that the Lions were due, but wow.

28

41.18

(2 – 11) / 51

#10 – #30

27

(Bye) The OAK=>SD win creating a 3 team beatloop with Arizona busted up the 4 team beatloop of SD=>ARI=>STL=>SEA=>SD, which means that STL=>SEA reappears in the graph. That’s what pushed Seattle back down the rankings.

15

39.22

(1 – 12) / 51

#11 – #31

28

(Lost to NYJ) At some point, we’ll just have to agree that Brett Favre doesn’t have it anymore, and this team is not good.

26

39.22

(1 – 12) / 51

#9 – #31

29

(Lost to JAC) The Bills have lost to more impressive teams than the other teams to come, which is why they’re ranked higher than them. The fact that they lost more unimpressively is not taken into account by Beatpaths.

27

31.37

(0 – 19) / 51

#14 – #32

30

(Beat STL) Beating the Rams did some good, as it looped away two beatlosses (to GB and PHI). And beating the Giants this week would loop away the loss to the Bears. Slow but sure, Detroit.

32

30.39

(0 – 20) / 51

#15 – #32

31

(Lost to CHI) I just don’t see how anyone associated with management on this team is going to survive this season. Even with Steve Smith they’re not particularly good. Without him they have nothing. They weren’t even close in a game where they got 4 INTs from an awful opposing QB. Good luck Carolina.

31

29.41

(0 – 21) / 51

#15 – #32

32

(Lost to PHI) It seemed like a lot of people were picking the 49ers in this game. I don’t know why–they had lost 4 games. And it’s not like Kevin Kolb is a bad QB, people. I’d say they should get a win this week versus Oakland, but really, I can’t even claim that as likely. Good luck, Iron Mike…

25

27.45

(0 – 23) / 51

#18 – #32

4 Responses to 2010 NFL Week 5 Beatpaths Power Rankings

  1. The MOOSE says:

    Re NE and Branch vs Moss:

    While Branch may not be on Moss’s level in terms of ability, the team won 2 Super Bowls with him catching 21 passes in those games. He was named Super Bowl MVP in the second. So the offense may not be as good, but I’m guessing it’s not going to be bad. Branch will run routes that Moss wouldn’t even if Moss ran routes that Branch couldn’t.

    But again, the problem with NE this year isn’t their offense. This whole Moss thing is going to be irrelevant as long as they give up 24 points per game.

    I’m guessing NE will struggle offensively against BAL this weekend and everyone will blame it on the receivers instead of the fact that BAL has one of the best defenses in the league. Remeber that BAL crushed NE in the playoffs last year even with Moss.

  2. ThunderThumbs says:

    “Branch will run routes that Moss wouldn’t even if Moss ran routes that Branch couldn’t.” heh…

  3. The MOOSE says:

    Preview for tomorrow’s graph! Today’s graph has an incredible 4 teams detached from the graph. I believe if TEN wins tonight’s matchup, all four will stay out. If JAC wins, there will be some loops created that will break longer loops, but even so it may not bring those four teams back into the fold.

    We might have a historic graph tomorrow!

  4. The MOOSE says:

    Actually I have that backwards. If TEN wins it creates a TEN → JAC → DEN → TEN loop that removes the DEN → SEA → SD → JAC → DEN loop. This would restore DEN → SEA → SD → JAC to the graph, reattaching SEA and SD.

    If JAC wins, it looks like the win will hold up and push JAC up the graph.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>