Skip to main content
Founding member21 of 97 slots remaining
Claim my slot →

Wolverine stack calculator

The Wolverine stack runs BPC-157 and TB-500 together from separate vials. Separate vials is the whole advantage: each compound gets its own draw, its own target and its own schedule, instead of sharing one ratio.

Set the vial sizes, the water per vial, your experience level and your body weight. The tool returns a draw volume per vial per phase, then a supplies plan for the cycle. Every dose figure is read from the Klarovel engine’s dose table, never typed into the page.

Vial sizes

Vial contents, not doses. Confirm against the label on the vial in front of you before you mix.

Bacteriostatic water per vial

Experience with injectable peptides

Body weight

kg

Standard phase, one draw per vial

BPC-157

6.0 units

delivers 300 mcg

TB-500 (Thymosin Beta-4)

48.0 units

delivers 2.4 mg

Separate vials mean separate draws, so each compound can hold its own target. That is the practical difference between running these two as a stack and buying them co-mixed in one vial.

Per-component breakdown at every draw volume

What each draw volume actually delivers per component at 2 ml of bacteriostatic water and the vial composition selected above. These are mathematical breakdowns of the vial, not dose recommendations. The targets and ceilings are in the titration table below.

Per-component amount delivered at each insulin syringe draw volume
DrawVolumeBPC-157TB-500 (Thymosin Beta-4)
2 units0.02 ml100 mcg0.1 mg
4 units0.04 ml200 mcg0.2 mg
5 units0.05 ml250 mcg0.25 mg
6 units0.06 ml300 mcg0.3 mg
8 units0.08 ml400 mcg0.4 mg
10 units0.1 ml500 mcg0.5 mg
12 units0.12 ml600 mcg0.6 mg
15 units0.15 ml750 mcg0.75 mg
20 units0.2 ml1000 mcg1 mg
25 units0.25 ml1250 mcg1.25 mg
30 units0.3 ml1500 mcg1.5 mg
40 units0.4 ml2000 mcg2 mg
50 units0.5 ml2500 mcg2.5 mg

Arithmetic over the vial composition and your water volume. The display unit per component is the unit that component's row declares in the engine dose table.

Phase by phase titration

Three phases, in the order the engine escalates a dose: opening, standard, then upper. Every figure below is the beginner row of the engine dose table for that component, after the modifiers your inputs trigger. Change experience level, weight or age above and the whole table recomputes.

Phase 1, opening dose

Phase 1, opening dose per component
ComponentDrawDeliveredCeiling
BPC-1575.0 units250 mcg500 mcg
TB-500 (Thymosin Beta-4)48.0 units2.4 mg2.5 mg
  • TB-500 (Thymosin Beta-4) is weight sensitive in the catalog at 0.03 mg/kg, so 80 kg sets the target rather than the fixed phase figure.

Phase 2, standard dose

Phase 2, standard dose per component
ComponentDrawDeliveredCeiling
BPC-1576.0 units300 mcg500 mcg
TB-500 (Thymosin Beta-4)48.0 units2.4 mg2.5 mg
  • TB-500 (Thymosin Beta-4) is weight sensitive in the catalog at 0.03 mg/kg, so 80 kg sets the target rather than the fixed phase figure.

Phase 3, upper dose

Phase 3, upper dose per component
ComponentDrawDeliveredCeiling
BPC-1578.0 units400 mcg500 mcg
TB-500 (Thymosin Beta-4)48.0 units2.4 mg2.5 mg
  • TB-500 (Thymosin Beta-4) is weight sensitive in the catalog at 0.03 mg/kg, so 80 kg sets the target rather than the fixed phase figure.

Targets, upper bounds and ceilings read from dose_protocols, the engine's dose table. Weight scaling applies only where PEPTIDE_CATALOG flags a component weight sensitive. The 0.75x age reduction is the engine's own contraindication rule for age 65 and over.

What your body weight does, and does not, change

Weight sensitive: TB-500 (Thymosin Beta-4) at 0.03 mg/kg. The engine catalog carries a per-kilogram factor for this component, so the weight you entered sets the target directly and is then held inside the beginner ceiling.

Not weight sensitive: BPC-157. The catalog does not flag this component weight sensitive and the dose calculator applies no weight scaling of its own, so changing the weight field does not move its target. Scaling every compound by body mass would be an invention, so the tool does not do it.

Supplies for one cycle

One on-cycle runs 12 weeks, followed by 4 weeks off.

Administrations per week

Options come from the components' own frequency strings: BPC-157 is once to twice daily, TB-500 (Thymosin Beta-4) is twice weekly. Where those disagree there is no single correct value, so the default is the most conservative one the data supports.

Bacteriostatic water bottle size
Supplies required for one on-cycle
Cycle length12 weeks
Administrations per week2
Total administrations24
Vials, per compound1
Insulin syringes24 (30-unit holds the draw)
Bacteriostatic water2 ml, 1 bottle of 10 ml

Cycle length from PEPTIDE_CATALOG cycling data. Administrations per week derived from the frequency string on each component's dose row. Vial and syringe counts are arithmetic over your draw volume and water volume.

The components' sourced frequencies do not overlap: BPC-157 is once to twice daily, TB-500 (Thymosin Beta-4) is twice weekly. A single vial forces one schedule, so no frequency satisfies every component's row. That is a real limitation of a fixed-ratio blend and the reason a protocol would run these as separate vials.

Component reference

Route, timing, frequency and cycling per component, read from the engine catalog.

Per-component administration and cycling reference
ComponentRouteTimingFrequencyCycleLoading phase
BPC-157subcutaneousAny timeonce to twice daily12 on / 4 offNone
TB-500 (Thymosin Beta-4)subcutaneousAny timetwice weekly12 on / 4 off4 weeks at 2x

Route, timing and cycling from PEPTIDE_CATALOG. Frequency from the beginner row of dose_protocols.

What a fixed blend cannot do, stated plainly

A blend is one ratio in one vial. There is exactly one draw volume, and it has to serve every component at once. When the ratio does not match the ratio of the components' own targets, something has to give: either a component lands under its target, or another is pushed toward its ceiling. The table above says which, for your inputs, rather than printing a single volume and leaving it unresolved.

Contraindications are the second limit. A protocol can drop one compound and keep the rest. A blend cannot, because the compounds share a vial. If a health condition rules out one component, it rules out the vial.

A Klarovel protocol is built from your health data. Blood work is optional and sharpens the result, but it never gates it. The engine resolves contraindications, sets the dose envelope by experience level, removes incompatible pairs and sets the cycling schedule. That is the difference between a calculator and a protocol.

Save your reconstitution. Get the protocol it belongs in.

Free founding-member access while spots last. We'll send your reconstitution + a link to claim your slot.

Questions

What is the Wolverine stack?
A community name for running BPC-157 and TB-500 together, usually from two separate vials rather than a co-mixed blend. The name comes from the pairing’s reputation in recovery contexts, not from anything in the literature.
Stack or blend: does it matter?
It matters more than the naming suggests. Two vials means two draws, so each compound can sit at its own target and follow its own frequency. One co-mixed vial means one draw volume for both, so the vial’s ratio decides how far each compound lands from its target. This page works the two-vial case; the BPC-157 and TB-500 blend calculator works the one-vial case.
Do the two compounds share a schedule?
Not necessarily, and that is one reason to run them as separate vials. The engine catalog carries a different frequency and a different cycling pattern for each, including a loading phase where one exists. The component reference table on this page shows both, side by side, for the experience level you selected.
Does body weight change either dose?
TB-500 yes, BPC-157 no. The engine catalog flags TB-500 weight sensitive and carries a per-kilogram factor, so the weight you enter sets its target and is then held inside the ceiling for your experience level. BPC-157 carries no such factor, and the dose calculator applies no generic weight scaling, so the tool does not move it.
Why does the calculator ask about age 65 and over?
Because the engine’s contraindication rules apply a 0.75x dose reduction across every peptide in the catalog once age reaches 65. It is a real modifier in the protocol path, so the calculator applies the same one rather than pretending age is irrelevant.
What is a loading phase and does the stack need one?
A loading phase is a short opening period at a higher frequency or multiple before settling into maintenance. Whether a component has one is read from the engine catalog and shown in the component reference table, along with its duration and multiplier. Nothing is assumed.
How many vials will a cycle take?
The supplies table multiplies the cycle length from the catalog by the administrations per week from the dose table, then divides the total volume by your water volume per vial. Because this is a stack, the vial count is per compound, not combined.
Can a protocol include both at once?
Depends on the person. The Klarovel engine caps the number of compounds in a protocol by experience level and removes incompatible pairs, and it blocks pro-angiogenic compounds outright on a cancer history. The calculator shows the arithmetic for any inputs; a protocol resolves whether the combination is appropriate for you.
Is this calculator free?
Yes. No account, no paywall, no usage limit. The protocol engine behind it is a separate product, but the calculator is open.
Does Klarovel sell this blend?
No. Klarovel is the protocol layer: a questionnaire, a deterministic rules engine and a generated protocol. Any product is fulfilled by partner suppliers, not by Klarovel. This page exists because the arithmetic of a fixed-ratio vial is genuinely hard to do in your head, not to move a product.
Is this medical advice?
No. It is arithmetic over published dose data, presented as a reference. It is not a prescription and not a recommendation to use any compound. Discuss peptide use with a qualified clinician.

Other blend calculators

Same engine, different vial. Pick the page that matches what you actually have in front of you: the component list and the ratio change the arithmetic completely.

References

These papers cover the mechanism and clinical context of BPC-157 and thymosin beta 4, the parent protein TB-500 is a fragment of.

The dose figures on this page are not sourced from these papers. They are read from the Klarovel engine's own dose table, which is cited inline wherever a number appears. These references cover mechanism, pharmacology and clinical context.

16 references, every identifier resolved against NCBI on 2026-07-30. Per peptide, a relevance-sorted esearch was run and every returned id was resolved through esummary. Any id esummary could not resolve was dropped, and any record carrying the 'Retracted Publication' pubtype was dropped. Titles, journals, years and first authors below are the values esummary returned, not authored text. One retracted record was dropped: PMID 37696839 (thymosin beta 4 query).

  1. 1.Chang CH et al. The promoting effect of pentadecapeptide BPC 157 on tendon healing involves tendon outgrowth, cell survival, and cell migration. J Appl Physiol (1985) 2011. PMID 21030672
  2. 2.Seiwerth S et al. Stable Gastric Pentadecapeptide BPC 157 and Wound Healing. Front Pharmacol 2021. PMID 34267654 PMC8275860
  3. 3.Gwyer D et al. Gastric pentadecapeptide body protection compound BPC 157 and its role in accelerating musculoskeletal soft tissue healing. Cell Tissue Res 2019. PMID 30915550
  4. 4.Józwiak M et al. Multifunctionality and Possible Medical Application of the BPC 157 Peptide-Literature and Patent Review. Pharmaceuticals (Basel) 2025. PMID 40005999 PMC11859134
  5. 5.Vasireddi N et al. Emerging Use of BPC-157 in Orthopaedic Sports Medicine: A Systematic Review. HSS J 2025. PMID 40756949 PMC12313605
  6. 6.Lee E et al. Safety of Intravenous Infusion of BPC157 in Humans: A Pilot Study. Altern Ther Health Med 2025. PMID 40131143
  7. 7.McGuire FP et al. Regeneration or Risk? A Narrative Review of BPC-157 for Musculoskeletal Healing. Curr Rev Musculoskelet Med 2025. PMID 40789979 PMC12446177
  8. 8.Sikiric P et al. The Stable Gastric Pentadecapeptide BPC 157 Pleiotropic Beneficial Activity and Its Possible Relations with Neurotransmitter Activity. Pharmaceuticals (Basel) 2024. PMID 38675421 PMC11053547
  9. 9.Goldstein AL et al. Thymosin β4: a multi-functional regenerative peptide. Basic properties and clinical applications. Expert Opin Biol Ther 2012. PMID 22074294
  10. 10.Kleinman HK et al. Thymosin β4 Promotes Dermal Healing. Vitam Horm 2016. PMID 27450738
  11. 11.Pipes GT et al. Cardioprotection by Thymosin Beta 4. Vitam Horm 2016. PMID 27450736
  12. 12.Smart N et al. Thymosin beta-4 is essential for coronary vessel development and promotes neovascularization via adult epicardium. Ann N Y Acad Sci 2007. PMID 17495252
  13. 13.Zhang Y et al. Recombinant human thymosin beta 4 improves ischemic cardiac dysfunction in mice and patients with acute ST-segment elevation myocardial infarction after reperfusion. Cardiovasc Res 2025. PMID 41229390
  14. 14.Tan WKY et al. Sources of variability in quantifying circulating thymosin beta-4: literature review and recommendations. Expert Opin Biol Ther 2018. PMID 29502471
  15. 15.Nachmias VT et al. Small actin-binding proteins: the beta-thymosin family. Curr Opin Cell Biol 1993. PMID 8448031
  16. 16.Mendias CL et al. Safety and Efficacy of Approved and Unapproved Peptide Therapies for Musculoskeletal Injuries and Athletic Performance. Sports Med 2026. PMID 41966639

Beyond the arithmetic

A protocol resolves what a blend cannot.

The Klarovel engine reads your health data, resolves contraindications, sets the dose envelope by experience level, removes incompatible pairs and builds the cycling and monitoring schedule. Blood work is optional and sharpens the result. It is never required.

Newsletter

Field notes.

Notes from the engine team. What we learned, what we changed, what the literature actually says. Wednesdays.

One email per week. No tracking pixels. One-click unsubscribe in every issue.