StackSenseHow to Track a BPC-157 and TB-500 Stack (the Repair Stack, Tracked Right)
The pair people call the wolverine stack has one tracking quirk that trips everyone up: the two peptides run on completely different clocks. Log them the same way and the picture blurs. Here's how to keep it sharp.
Why a spreadsheet falls apart here
A repair stack has a problem a weight-loss protocol doesn't: you're chasing one specific thing getting better. A knee, a shoulder, a tendon. So your tracking has to tie every injection back to how that one area feels over time, and it has to do it for two compounds that don't behave alike. A spreadsheet handles this for about a week. Then the entries drift, the injury notes end up in a different app, and the recovery signal you were trying to catch gets lost in the mess.
The two run on different clocks
This is the whole reason the stack needs deliberate tracking. BPC-157 clears fast, in a matter of hours. TB-500 hangs around far longer. That gap is exactly why you log the time of each shot, not just the date, and why your TB-500 entries will look sparse next to your BPC-157 ones. Here are the research-default half-lives, which vary by person and source:
| Compound | Research half-life | Typical route | Why it matters for tracking |
|---|---|---|---|
| BPC-157 | ~3 to 6 hours | SubQ / IM | Short and site-directed, so log the exact site and time each entry; patterns cluster fast |
| TB-500 (Thymosin Beta-4) | ~24 hours (community estimate) | SubQ | Longer-acting and systemic, so entries are sparser; a timeline keeps it lined up with BPC-157 |
Half-life ranges are research defaults for context only. TB-500 has little formal human data, so treat its figure as a community estimate. These are not dosing instructions.
What to actually log
Good tracking here is boring and consistent. Capture these:
Every injection, with the site
What, when, and where. Track injection sites across both compounds, not siloed per peptide, so you can see rotation at a glance and catch a spot that's getting overused before it gets sore.
A recovery score
This is the number that matters and the one people forget. Rate the injury or area you're rehabbing on a plain 1 to 10 scale, most days. Pain, stiffness, range of motion, whatever fits. A dated score turns "I think it's a bit better" into a line you can actually read.
Where you are in the cycle
People run repair peptides in blocks, on for a stretch and then off. Note where you are in that block, because a plateau reads completely differently at week two than at week six. Without cycle position logged, you're guessing.
A baseline
On day one, capture the starting state of the thing you're fixing: your recovery score, range of motion, and any relevant bloodwork. "Better" is meaningless without it. The baseline is what makes the whole log a before-and-after instead of a diary.
Bloodwork, if you track it
Some people watch an inflammation marker like hs-CRP with their clinician across a recovery block. If you do, keep those results next to the log so you can line them up with your score instead of hunting through email.
The plateau trap
Repair peptides tend to help while tissue is actively healing, then level off once you've gotten the available benefit. That's normal, but it's also where people get fooled. Without a dated recovery score, you can't tell a natural plateau from a slow slide backward, and you can't tell a genuinely better batch from wishful thinking after you reorder. The log is the only thing that keeps you honest with yourself.
Keep supplements in the same place
If you're taking collagen, vitamin C, or anything else alongside the peptides for recovery, track it in the same timeline. The interactions and the timing only make sense when the whole stack is in one view, not peptides in one app and supplements in another.
Where StackSense fits
Disclosure: we build StackSense, so factor that in. Peptide-only apps log injections fine, and some do it well. We built StackSense for the bigger version of this problem, when your repair stack, your supplements, your recovery notes, and your bloodwork are scattered across a spreadsheet, a notes app, and a camera roll.
StackSense puts the whole stack (supplements and peptides, 420+ compounds), your symptoms, and your labs on one timeline, with a baseline so progress is measured instead of guessed. It runs as a web app, so you add it to your homescreen on any device, no app store needed. It's a tracking tool, full stop. It doesn't tell you what to take or how much, and it isn't a medical device.
One timeline for your whole stack, your recovery score, and your labs.
Get early access to StackSenseFAQ
What should I track on a BPC-157 and TB-500 stack?
At minimum: each injection (what, when, and which site), a simple daily score for the injury or area you're rehabbing, and where you are in the cycle, all against a starting baseline. The recovery score and the baseline are the parts people skip and later wish they hadn't.
Why log BPC-157 and TB-500 differently?
They move on different clocks. BPC-157 clears in a matter of hours, while TB-500 lingers far longer, so a log that captures the time of each shot, not just the day, keeps the picture clean. Tracking sites across both compounds also shows rotation at a glance.
What is the wolverine stack?
It's a community nickname for running BPC-157 and TB-500 together for recovery. This page isn't about how to run it, only how to track it honestly so you can tell whether it's actually helping the thing you're rehabbing.
Is this dosing or medical advice?
No. This is about organizing your own data. Anything involving what to take, how much, or how often belongs with a qualified professional.
This is a tracking and organization guide only. It is not medical, dosing, or treatment advice, and StackSense is not a medical device. Work with a qualified healthcare professional on anything you put in your body.