Personal estimate, explicit limits
Apex Heirloom Tracker
Keep your eligible-pack estimate, opening records and cycle history in this browser, with a separate ledger for event/direct unlocks and Shards. Personal records do not change the probability model or supply an official EA counter.
Loading this browser's records…
Your personal records are loaded only in this browser.
Build the estimate from records, not memory
- Start with the current pack-awarded Bonus Heirloom Shards cycle.
- Count only rewards you can classify as eligible Apex Packs.
- Exclude EA-listed event and replacement-item pack categories.
- Do not add packs opened while your Bonus Shards eligibility was paused.
- Record event/direct Mythic unlocks separately without changing the counter.
Save today and continue next time
In My records, choose an estimate, a finite range, an explicitly new zero cycle, or unknown history. Describe which opening boundary that starting value already covers, then review and confirm. Ordinary new openings have a short Save pack record path. Use Backfill history for older or same-day records whose coverage is unclear; review whether they are included before confirming. Edit, delete and immediate undo recalculate from the records rather than maintaining a second editable total.
In Correct the starting estimate, review every existing record's relation to the revised boundary. A clearly marked trial example is separate from your records and never writes its demonstration count into your history. Wait for Saved in this browser before closing the page.
A complete demonstration, not a player testimonial
Suppose you estimate 240 eligible openings before starting the ledger. Add 10 new eligible, unpaused openings: the estimate becomes 250. Backfill 10 older openings already included in the original 240: the estimate stays 250. Add four openings with uncertain eligibility: it becomes 250–254, not a guessed midpoint. Excluded types and paused openings remain visible without increasing the counter.
If a later batch of 10 contains a confirmed award at position 7, the cycle preview separates six before, one winning opening, and three after. The first seven stay in the completed cycle and the last three start the next cycle. The winning opening is not added again. An unknown position must be clarified first. Event/direct unlocks remain separate; a Shards balance is a dated snapshot, not cumulative income.
Correct a cycle without losing later records
Cycle management always asks for a confirmed award boundary or a reason for manual reorganization. Neither the date nor reaching 500 creates a cycle automatically. You can undo an empty next cycle. If it already has records, use the retained-record correction: review each destination and coverage relation, then confirm. The tool does not restore an old snapshot over later records.
Backup limits and recovery
JSON preserves all cycles and the collection ledger. CSV is for reading and cannot be imported. Import previews a replacement and first preserves one valid recovery snapshot; a snapshot or storage failure cancels the replacement. Limits are 5000 combined records, 200 cycles and 2 MiB of complete JSON, whichever comes first, plus your browser's actual storage quota. Long notes can reach the byte limit before the record limit. Valid saved data can be restored by a compatible version with enough space.
Different browsers and devices do not share records. Damaged or unsupported-version originals can be downloaded for safekeeping, but this version may not restore them. An unsaved session does not overwrite them. Clear all tracker data removes this tool's ledger, recovery copy and current temporary/undo copies; it keeps only a nonpersonal marker to block stale-tab writes. Downloaded backups must be deleted yourself.
What the tracker deliberately does not infer
It does not add platform accounts together, reconstruct a hidden EA counter from account level, or decide that every event reward resets the guarantee. EA does not expose enough account-specific information for those calculations. When evidence is incomplete, the tracker keeps the uncertainty visible.
Official reference
Read the EA Apex Legends FAQ for the 500-pack rule, eligibility pauses, and excluded pack types. The associated lower-bound probability uses EA's disclosed minimum global drop rate.
Related reading
FAQ
What number should I enter?
Enter your estimate of eligible Apex Packs opened in the current Bonus Heirloom Shards cycle. Do not use an unqualified lifetime total.
Do event unlocks change the probability?
Not in this tracker. Event or direct Mythic unlocks and your Shards balance are recorded in a separate ledger and never alter the eligible-pack formula.
Why is the counter only an estimate?
LootCalc cannot access an official EA account counter. Pack classification, eligibility pauses, and incomplete personal records can all change the true count.
What happens at 500?
A current waiting estimate that reaches 500 switches to a diagnostic; a range touching 500 does too. A historical cycle you explicitly completed at 500 instead shows the completed event. The tracker never uses modulo arithmetic or guesses an award.
Will my records still be here next time?
After you explicitly start recording and see Saved in this browser, records remain in this browser profile. There is no account or cloud sync. Clearing browser data, private browsing or device failure can lose them, so export JSON backups. An unsaved session stays in memory only.
Does backfilling history add the same packs twice?
For history, explicitly choose whether each record was already included in your starting estimate. Included details add zero; not-included eligible, unpaused records add their count. Unknown coverage stays pending. Dates alone do not decide inclusion. Correct the starting estimate separately if its original value was wrong.
What if I do not know my starting count or eligibility?
Keep the starting count unknown or enter your own finite range. Unknown pack type, pause or coverage remains pending; the same uncertain record is counted only once in a possible upper bound. Unknown starting history does not become zero or an exact guarantee distance.
How do I recover a backup or remove my records?
Export JSON for recovery; CSV is a readable report only. Import validates and previews a replacement, never merges it. A current valid ledger must be saved as a recovery snapshot before replacement. Clear all tracker data removes the local ledger and recovery copy after confirmation, but cannot delete downloaded files. Unsupported originals remain untouched until you explicitly clear them.
Changelog
- 2026-09-07: Added local records, explicit starting coverage, cycle history, uncertainty ranges and browser-only JSON recovery.
- 2026-07-11: Replaced inferred reset logic with a user-supplied eligible-pack estimate and separate collection ledger.
- 2025-11-05: Initial tracker published.