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: Carlton

    The Demons return to the MCG next week and will be looking to atone for a dismal performance in Perth as they take on the under the pump Blues. Who comes in and who goes out for our Round 3 match against the Carlton?

    • 182 replies
  • REPORT: Fremantle

    Melbourne’s early surge of optimism came crashing back to reality in its clash with Fremantle at Optus Stadium on Saturday night. Just six days after unveiling its fun-filled, attack-minded style against the Saints, the Demons were met by a Dockers outfit determined to shut it down with a blend of speed, pressure, and physicality.

    • 0 replies
  • CASEY: Footscray

    The Casey Demons faced a tough first up task taking on reigning VFL premiers Footscray at Mission Whitten Oval. The Bulldogs, who unfurled their premiership flag pre-game, had 15 AFL-listed players and their top VFL talent available, setting them up for their 15th consecutive win.

      • Thanks
      • Like
    • 5 replies
  • POSTGAME: Fremantle

    The Demons were fumbly, inefficient, outrun and outgunned all over the field as they went down to the Dockers by 48 points at Optus Stadium in Perth.

      • Thanks
      • Like
    • 312 replies
  • PODCAST: Fremantle

    The Demonland Podcast will air LIVE on Monday, 23rd March @ 8:00pm. Join Binman, George & I as we dissect the Dees dismal loss to the Dockers in Perth.
    Your questions and comments are a huge part of our podcast so please post anything you want to ask or say below and we'll give you a shout out on the show.
    PLEASE TRY TO KEEP THE QUESTIONS/COMMENTS TO ONE SPECIFIC TOPIC/PLAYER IN ORDER TO MAKE THE PREPARATION FOR THE PODCAST EASIER.

      • Thanks
    • 29 replies
  • VOTES: Fremantle

    Coming off Back to Back Demonland Player of the Year Award wins Captain Max Gawn is already in the lead followed by Jacob van Rooyen, Jai Culley, Kozzy Pickett & Jack Steele. Your votes please. 6, 5, 4, 3, 2 & 1.

      • Vomit
      • Like
    • 43 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.