product page v1
1:1 · shot on a road, not a studio
ON-BODY
DETAIL
GUIDE
IN USE
FIT
The 30-Day Line
For the run you're about to do this Sunday — and the one after it that goes further than anything in your last thirty days.
- One pair of calf sleeves. No foot. The foot is where the fit complaints live, so we removed it.
- The 30-Day Line protocol. How to find your own number, how to spot the session that crosses it, and what to do in the 48 hours around it. This is the part that explains the cause. It is not a bonus.
- The spike log. One page. Your longest run in the last thirty days, updated weekly, so the number is never a guess.
On mmHg: we list it because buyers look for it. We don't build a claim on it. No recovery-specific evidence supports any particular pressure range, and commercial garments are documented to vary widely from their labels.
It was never the miles. It was the jump.
Your lower legs don't break down from how much you run. They break down from a single run that goes too far past your recent longest — and it arrives without the warning you were told to expect.
Everything you were told about how much to run was either untested, or measuring the wrong thing.
Not "everything you bought." Everything you were told. You're eight weeks into a block, following a plan, wearing a watch, checking a forum. Three sources of guidance, and the shin still hurts. Here's what each one actually is.
The 10% rule
The one rule almost every runner in this sport is handed. It has no documented scientific origin. It was popularised by Joan Ullyot in Running Free (1980) and by Joe Henderson.
It was tested once at scale, on people exactly like you — novice runners — and it did nothing.
Graded program 20.8% injured · Standard 20.3%
χ²=0.016 · P=.90
Your watch
It gives you a training-load number, and you have never examined what it's built from. Most are derived from acute:chronic workload ratio.
In the 5,205-runner cohort, that ratio showed no positive association with injury. You believe you're being monitored. On this specific question, you aren't.
95% CI 0.59–0.96
The plan, the forum, the club
They contradict each other, which you already know, because you've been triangulating between them since week four and you still can't answer the only question that matters: is this run too much for me, today?
None of them is built on your body. They're built on a distance and a date.
advice without a cause underneath it
Millions of runners receive incorrect guidance from their sports watches every day. Rasmus Østergaard Nielsen — lead investigator, RUNSAFE, Aarhus University
Fifty years of shoe technology. Injury rates haven't moved.
Cushioning, stability, motion control, carbon, rockers, drop. Enormous investment, decades of research, and no systematic reduction in how often runners get hurt. Researchers in the field say so themselves — the absence of any fall in injury frequency has led to the suggestion that the scientific method has so far failed on this problem.
That isn't proof of what causes injury. It's proof that the category has been answering the wrong question, expensively, your entire running life.
The step in the dark.
You didn't fall because you'd been walking too long. You fell because of one step that wasn't where your body expected it to be.
For decades nobody could answer how much running is too much, because the data didn't exist. Studies ran a hundred participants, sometimes a thousand. Then a research group at Aarhus University partnered with Garmin and watched 5,205 runners across 87 countries log 588,071 sessions over eighteen months — roughly five times the largest cohort ever assembled.
They expected to find injuries building gradually. They found the opposite. What predicted injury was not weekly volume. It was a single session that went too far past that runner's own longest run in the previous thirty days.
Injury risk, by how far one run exceeds your 30-day longest
95% CI 1.31–2.05 · p=0.01
Moderate spike · HRR 1.52 (+52%)
95% CI 1.16–2.00 · p<0.01
Large spike · HRR 2.28 (+128%)
95% CI 1.50–3.48 · p<0.01
Frandsen et al., British Journal of Sports Medicine 2025;59(17):1203–1210. Published 7 July 2025. 1,820 of 5,205 runners injured (35%).
Two numbers. That's the whole method.
Open Strava or Garmin. Find the longest single run you've done in the last thirty days. Then look at what your plan has you doing next. If the second number is meaningfully bigger than the first, that session is the one to build the week around.
You didn't ignore a warning. For most people, there isn't one.
If you're carrying a quiet suspicion that you did this to yourself — that you should have known, that you overrode your own body — the companion paper from the same cohort is worth sitting with.
11.2%
Of 1,199 overuse injuries, only 11.2% had a gradual onset. Nearly nine in ten arrived suddenly.
1,065
Injured runners who reported no problem at all in that anatomical location in the preceding 28 days.
6.9%
Reported anything at all in the seven days before the injury. The niggle you're watching for mostly doesn't come.
This is not reassurance and it isn't an excuse. The mistake was real. But it relocates where the mistake lives: not in your judgment of your own body, in the information you were handed about how to load it. You were told to watch for a warning. The warning was never the signal. The line was.
I ignored my gut and ran it anyway… Boy, was I wrong. Runner, week 9 of a block · runandgetit
Read it again knowing what the cohort found. The gut wasn't the instrument. Nobody gave her one.
A protocol built on your number, and a garment sequenced to it.
Three parts. Each one does exactly one job, and we're going to be specific about which job, because the difference matters more here than anywhere else on this page.
Carries the prevention logic
Where your longest run sits in the last thirty days. What counts as a spike against your number rather than a generic percentage. How to sequence the week so the necessary jumps happen on purpose instead of by accident. And — critically — that the absence of a warning signal is normal rather than reassuring.
Fabric cannot explain anything. Only the guide can. This is why it isn't removable from the box.
Carries the sensation
It owns the recovery window around the sessions the protocol flags, and it delivers the one benefit the evidence actually supports: reduced perceived soreness and leg heaviness.
That's the claim. It's a narrow claim. It is also precisely what runners describe when compression works for them, which is not a coincidence.
Makes the protocol stick
Runners already ritualise compression without being asked to — "I wear them while running and for up to an hour afterwards" is the market's own description, unprompted.
Here, putting them on is the act that marks a session as a spike session. The garment becomes the physical trigger for the knowledge. That's what turns a PDF you read once into a habit you keep for sixteen weeks.
Compression socks do not prevent running injuries. We're not going to tell you they do.
There is no credible peer-reviewed evidence that compression garments prevent stress fractures, shin splints, Achilles tendinopathy, plantar fasciitis or calf strain. And there is no evidence whatsoever linking compression to mitigating training-load spikes — that link does not exist in the literature.
You are one search away from finding that out. We'd rather you heard it here, because a brand that hands you a 588,071-session study and then quietly overclaims on its own product has taught you exactly the standard by which to catch it.
So the separation is permanent, and it's the whole architecture of this offer:
The protocol carries prevention
Because the cause the research identified is a training behaviour — a run that crosses your line. Only a method can address that. A garment cannot.
The sleeve carries sensation
Reduced perceived soreness in the recovery window. Nothing beyond that, in any asset we publish, ever.
Which is also the answer to the socks you already own. If you've got a pair in a drawer, or a three-pack for $13.99, or you decided years ago the whole category was placebo — you were assessing a garment sold with no cause underneath it. That assessment was correct. It just wasn't about this.
Nobody in this market has ever described a number.
Every positive report we could find — across forums, reviews and first-person write-ups — is a sensation. Not one is a measurement. So that's the standard we're held to, and it's the only one we claim.
"my calves felt hugged — as though they were being massaged"
ESPNW · first-person trial"make my legs lighter and less sore"
Reviewer · Trustpilot"I notice less soreness the day after a long run"
Forum user · SlowtwitchThe evidence agrees with them, and only with them.
Hill et al. (2014, British Journal of Sports Medicine) meta-analysed compression garments and found a moderate reduction in the severity of delayed-onset muscle soreness.
That the market's proof standard and the evidence base land on the same narrow claim is the most useful thing about this category. We're not asking you to believe something you can't check. You'll know within two long runs.
95% CI 0.236–0.569 · p<0.001
Hill et al. 2014, BJSM 48(18):1340–1346
- Négyesi et al. 2022 found no strength-sparing effect at any timepoint (all p≥0.38). We don't claim one.
- Weng et al. — 51 studies, 899 participants — found no improvement in race time or time to exhaustion. We make no performance claim of any kind.
- A 2026 review calls the soreness effect statistically imprecise and vulnerable to expectation effects. That's on the record too.
If you're going to accept an argument because of a 588,071-session study, you should know where it stops.
- The study is observational. The authors write that the design limits how robustly causal claims about injury prevention can be made. The correct phrasing is "associated with," not "causes," and we hold to it.
- Injuries were self-reported by the runners in the cohort.
- The cohort was 77.9% male, mean age 45.8, and everyone in it owned a Garmin. That is not a perfect match for a first-time half or full marathoner.
- A public data-blogger critique of one of the paper's secondary findings — the inverse weekly-load result — exists and is findable. We'd rather you found it via us.
We're telling you this because it's the same standard we're asking you to apply to our product claim, four sections up. If you hold us to one, hold us to both.
The calendar doesn't move because your shin hurts.
You told people you were doing this. Family, colleagues, the run club, Strava. That's what makes not making the start line a different kind of loss than not finishing — it isn't private.
And you are in the specific window where this is still a decision rather than a diagnosis: weeks six to twelve, long runs getting genuinely long, something new in a shin or a calf. Novice runners get hurt at 17.8 injuries per 1,000 hours against 7.7 for recreational runners. Top of the risk curve, with a fixed date at the end of it.
Discomfort during running is normal, expected and tolerated by most all runners. Donna Arrington, UAB — the belief she held three miles before her femur broke
The 30-Day Line
Calf sleeve, protocol, and spike log. One box. The guide is not a bonus and not a value-stack item — it holds the mechanism, so it doesn't come out.
- One pair of graduated calf sleeves, sized on calf circumference
- The 30-Day Line protocol — find your number, read your week, act on the crossings
- The spike log — one page, updated weekly
- PLACEHOLDER guarantee terms — this is where belief #6's low-risk half gets installed. It has to be written from your actual return policy.
If you'd rather start with the free version: the line calculation above is the whole first step, and it costs nothing. Do that either way.
From runners in a block
BUILD NOTE No customer data exists in the research yet — none of the supplied documents contains reviews, tickets or survey data specific to your buyers. Every review on this page must come from real purchasers before launch. This is also the section where the competitor page fails hardest: nineteen reviews on a flagship SKU, top five being a hiker, an edema patient and a turf-durability complaint.