This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Ground Contact Time Balance

Former Member
Former Member
I just recently started to get back into running again after a two year layoff due to a knee injury. Prior to that I would run 5 days a week for 20 years under Uncle Sam's watchful eye (retired US Army) and I would also run on my own after I left the military. I've never considered my a "runner" and never trained for any races. Anyway, with my recent purchase of my 935 and HRM-Tri, I've been following my running dynamics. To my surprise all my running dynamics have been in the green with the exception of ground contact time balance. There I'm in the red and my numbers for the past 2 months average 48-52. If I understand correctly this shows a problem with my left leg which wouldn't make sense since it was the right knee I injured. I don't notice anything out of the ordinary when I run, but this is my scoring average for GCTB every time. So, my question is, what do I need to do to correct this? Are there any drills I can perform? Thanks for any input.
  • The technology to measure running dynamics is relatively new, and I don't think there are a lot of rigorous studies into the effectiveness of training based on running dynamics. (It's a long process of introducing the technology, working out how to train with it, training with it, then measuring the performance across a range of different athletes, and finally publishing the results). At this stage, I think there is a consensus that there is a lack of evidence about the effectiveness of training with RD metrics other than cadence. That answer might be different in 2-3 years time.
  • Former Member
    0 Former Member over 7 years ago
    In a round about way, are you telling me I just spent $100+ for a HRM-Tri that I thought would make me a better runner with the running dynamics just to have a bunch of numbers that may or may not mean anything? :(
  • Yep! Just because Garmin provide numbers doesn't meant they are of any more value than any other metrics. They may help. They may hinder.

    To answer the original post, if you're running without injury then often things are best left alone. You've obviously been running for a long time. You've only had the Garmin a short time. You have no idea whether or not you've always been running 48/52 or whether it's a result of your injury. I'd leave alone and accept 48/52 as your 'norm'.
  • Yep. At the moment, it is pretty much data without a cause.

    The other thing with RD capable pods and belts is that they now allow running with power, which may potentially help with pacing for longer events. Although again, this is pretty new, and the evidence and training techniques behind it are still unproven.
  • I just recently started to get back into running again after a two year layoff due to a knee injury. Prior to that I would run 5 days a week for 20 years under Uncle Sam's watchful eye (retired US Army) and I would also run on my own after I left the military. I've never considered my a "runner" and never trained for any races. Anyway, with my recent purchase of my 935 and HRM-Tri, I've been following my running dynamics. To my surprise all my running dynamics have been in the green with the exception of ground contact time balance. There I'm in the red and my numbers for the past 2 months average 48-52. If I understand correctly this shows a problem with my left leg which wouldn't make sense since it was the right knee I injured. I don't notice anything out of the ordinary when I run, but this is my scoring average for GCTB every time. So, my question is, what do I need to do to correct this? Are there any drills I can perform? Thanks for any input.


    i would NOT try to actively try to change GCTb when looking at it during a workout. but yes a longer term aim for it to be balanced would be generally sensible.
    Garmin's GCT is quite different from RunScribe and STRYD (in my case) and so i doubt the accuracy. I midfoot strike.
    nevethless i would imagine garmin's GCT balance does broadly correctly show imbalances.

    to answer your question: i would use a combination of - plyometrics, longer aerobic runs, strength training and hill reps. I suppose that's broadly called 'training' :-) but pay specific attention to the plyo work.

    runscribe can be good to further pinpoint gait problems AND the impact of different shoes

  • There I'm in the red and my numbers for the past 2 months average 48-52. If I understand correctly this shows a problem with my left leg which wouldn't make sense since it was the right knee I injured.


    If I understand GCT balance correctly, 48-52 means that the right leg is spending more time on the ground. This would indicate that your right leg is weaker.
  • I own a RD-pod, a stryd and a HRM-run and my Rd pod says im almost a 50-50 runner but my hrm-strap give me more 48,5-51,5. An other thing is stryd metrics are the same as my HRM-run strap but the Rd pod is way off, better GC and vertical values unfortunately. For me it's hard to use because the numbers always the same depending which running dynamic source I'm using.
  • Former Member
    0 Former Member over 7 years ago
    If I understand GCT balance correctly, 48-52 means that the right leg is spending more time on the ground. This would indicate that your right leg is weaker.


    OK, that would make sense then if it's showing my right leg weaker. My concern was Garmin's statement that studies have shown an increase in injuries with bad GCTB and after my knee injury I broke my wrist. I don't want to go through another two year span of basically being restricted to stretching. Thanks for everyone's comments. I guess it is what it is and I'll go with that.
  • Does it change from 48-52 over the course of a run? I have had left Achilles problems of late and often say see 45-55 initially until I loosen out and gets more like 50-50.
  • Former Member
    0 Former Member over 7 years ago
    No. It seems the further/longer I run the worse it gets.