Skip to content
View in the app

A better way to browse. Learn more.

Demonland

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.

Injured Players

Featured Replies

34 minutes ago, deanox said:

This is really insightful, thanks!

I do think that it is hard to draw conclusions without some other data too, namely our opposition's performance in the same stat each week (so we can see if we are performing above/below trend).

Its also tough because high speed distance is subject (what's high speed? Do we do lots of work just below this number). But I think it's a great proxy!

It is just a proxy.  I think it equates more closely to total power output than anything else. High speed is >18km/hr.  Burgo confirmed that last year against GC we were off the charts for total output (20% higher than any other game) and this data supports that.

Sorry but I didn’t grab opponents numbers. It’s too time consuming, but you are probably right.  Wet conditions will result in less running for both teams.

 

 
6 hours ago, BW511 said:

I don’t want to start a loading argument again, however if you can’t get the loading in, fitness will drop off.

Perhaps we went with the loading mid season and then when we went to have a second go at it we could not get enough work into the players due to injuries, hence the drop off in fitness/running power

Either this or I am of the belief that we over trained ie. overdid it with the loading this year.

It may have partly been because we pushed clearly injured players through the same program rather than not doing it. This can cause chronic fitness problems for multiple months after you mess it up. We should be a different team next year in terms of running ability.

"We were a little bit banged up at the end of the year."

Simon Goodwin

(He also reinforced what Gawn said, that it felt like two continuous years, that the players didn't get much of a break last year.)

 

 
On 9/24/2022 at 5:40 PM, Monbon said:

Hindsight, JNM. We wouldn't have finished second had we not won three crucial games: Geelong had the benefit of games up their sleeve, plus many games at Geelong. They also had a dream run with injuries. When injuries hit us like a tempest, life ain't ever going to be easy for selectors or game plan strategists.

The question isnt about injuries really , it’s more  about injury management. Hindsight is easy I agree but we did make a lot of mistakes in this regard in 22. Let’s hope they reset their approach in 23. 

15 hours ago, Watson11 said:

I posted the GPS numbers on another thread.  They are posted here for your convenience. The graph has high speed distance in km per game.,  We did not drop off at all in 2021 (in fact improved slightly).  But this year was not good.

image.png.85cd797b0b6950c0047d72cf77ceb002.png

Thanks for that. Last year was a strange one, would be more interested in comparing other top 8 teams this year. Also, different grounds likely result in different high speed outcomes, dry decks in qld and wa might also result in different outcomes. Round19 last year looks like an error/outlier also. Still very interesting, but to make conclusions from it it need a greater deep dive


On 9/24/2022 at 10:03 PM, rpfc said:

I don’t disagree but we risked Salem, Lever, Gawn, Brown and Jackson (at least) in games when they could have had longer lay offs during the middle of the year that may (emphasis on may) have meant a better September. Gawn had syndesmosis and was back in 2 weeks for example. We were losing anyway…

These are but lessons for our future. 

@Rhino Richardshave at it, RR. 

A facepalm only days so much…

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

Featured Content

  • PREGAME: Richmond

    The Dees hit the big Friday night stage for the first and only time this season when they take on the Tigers under lights on ANZAC Eve at the G. Who comes in and who goes out?

    • 223 replies
  • REPORT: Brisbane

    Before Sunday, the last time the Brisbane Lions had walked onto the turf of the Melbourne Cricket Ground, they celebrated the pinnacle of the sport - an AFL premiership secured in emphatic fashion for the second consecutive year.

      • Clap
      • Thanks
    • 1 reply
  • CASEY: Brisbane

    From the outset, the Casey Demons lacked any spring in their steps. They were out-hustled and out-bustled and finally outplayed by the Brisbane Lions by 38 points on their home turf in perfect conditions at Casey Fields.

      • Thanks
    • 0 replies
  • POSTGAME: Brisbane

    MCG magic strikes again as the Demons unleash a devastating second-half surge to edge Brisbane in a thrilling two-point statement win. Never in doubt 🍀🔴🔵😈

      • Shocked
      • Haha
      • Love
      • Like
    • 501 replies
  • PODCAST: Brisbane

    Andy is still traveling but the boys will still be bringing you a podcast this week so get your questions and comments in for Binman and George as they dissect the thrilling win over the Lions at the G.

      • Thanks
      • Like
    • 14 replies
  • VOTES: Brisbane

    Reigning Champion and Captain Max Gawn already has a healthly lead just 5 rounds in to the Demonland Player of the Year Award vote count. He leads from Kozzy Pickett, Jack Steele, Tom Sparrow & Jacob van Rooyen. Your votes please. 6, 5, 4, 3, 2 & 1.

      • Thanks
    • 63 replies

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.