Recovery & soft-tissue research
The Wolverine Stack (BPC-157 + TB-500)
Why this combination exists
The pairing is the most-referenced combination in recovery research because the two compounds work at different levels: BPC-157 is studied for local repair signaling — angiogenesis, fibroblast migration, growth-factor upregulation at the injury site — while TB-500 acts systemically through actin regulation, mobilizing cell migration body-wide.
Their dosing rhythms are complementary rather than overlapping: BPC-157's ~4-hour half-life puts it on a daily schedule, while longer-acting TB-500 runs weekly.
Literature-referenced schedule
| Component | Referenced schedule |
|---|---|
| BPC-157 | 250–500 mcg once or twice daily (literature reference), typically 4–8 weeks |
| TB-500 | 2–2.5 mg once or twice weekly loading for 4–6 weeks, then weekly maintenance |
Reconstitution notes
Two separate vials, two separate schedules. Common reference: 5 mg BPC-157 + 2 mL BAC water (250 mcg = 10 units); 5 mg TB-500 + 1 mL BAC water (2.5 mg = 50 units). Both refrigerate for ~60 days reconstituted.
Build this protocol in the app
The protocol builder turns this schedule into dose reminders, syringe-unit calculations, and a running log — free to start.
Peptides in this protocol
BPC-157
A synthetic peptide fragment studied for tissue repair, tendon/ligament and gut healing in animal research.
Full research profile →
Healing & RecoveryTB-500
A synthetic version of a region of Thymosin Beta-4, studied for cell migration, angiogenesis and tissue repair.
Full research profile →
Frequently asked questions
Why is it called the Wolverine stack?
A community nickname referencing the comic-book character's healing — shorthand for the BPC-157 + TB-500 pairing that dominates recovery research discussion.
Are BPC-157 and TB-500 mixed in the same syringe?
Research references describe both same-session administration and separate schedules; because their frequencies differ (daily vs weekly), most referenced protocols simply run them on their own rhythms.
How long is the stack referenced to run?
Common literature references describe 4–8 week cycles, matching TB-500's loading-then-maintenance pattern.