About D2Sherpa.report

D2Sherpa.report looks up a Bungie Name and turns that player's Destiny 2 raid and dungeon history into completion stats and a set of "Sherpa" scores meant to reflect how much raid/dungeon experience they have to offer a fireteam.

Where the numbers come from

Everything is pulled live from the Bungie.net API: the player's full raid and dungeon activity history, then the Post-Game Carnage Report (PGCR) for every completed instance. The PGCR is what makes it possible to tell a full clear from a checkpoint join, count deaths for flawless detection, and see who else was in the fireteam; none of that is available from the activity history alone.

What the activity card stats mean

• Full clears: completions where the report shows the activity was started from the very beginning.
• Checkpoint clears: completions where the player joined a run already in progress.
• Fastest / Average full clear: the shortest and mean duration across that player's full clears only; checkpoint joins aren't timed since they don't start from the beginning.
• Solo / Duo / Trio: completions where the whole fireteam that finished the activity was 1, 2, or 3 players.
• Flawless / Solo flawless: a full clear with zero deaths across the fireteam (flawless), or the same with a fireteam of one (solo flawless).

How the Sherpa scores are calculated

Each score is built up in stages, from raw clears to a single 0-100 headline number.

1. Recency-weighted clears

Every full clear counts as 1 completion; every checkpoint clear counts as a quarter of one (0.25) since it's a smaller lift than running the whole thing. That number is then multiplied by a recency weight for the specific raid or dungeon (1x for the oldest activity in the game, scaling up to 2x for the most recently released one), so recent experience counts for more than clears from years-old content. Summing that across every raid (or every dungeon) gives the "Recency Weighted Clears" figure shown on the scorecards.

2. Experience Score (0-100)

The recency-weighted clears total is mapped onto a 0-100 scale using an approach curve (100 × (1 − e^−x/k)): the score climbs quickly with your first clears and then levels off, asymptotically approaching but never quite reaching 100 as clears keep piling up. This keeps a single score from being dominated by players with thousands of clears of one activity.

3. Breadth Score (0-100)

The percentage of raids (or dungeons) the player has cleared at least 10 times. This rewards being well-rounded across the whole roster instead of only ever running one or two favorites.

4. Full Clear Tendency (0-100)

The percentage of completions that were full clears rather than checkpoint joins, a rough signal of how often the player runs activities start-to-finish versus hopping into someone else's checkpoint.

5. Headline scores

The Raid Sherpa Score and Dungeon Sherpa Score each blend that kind's Experience Score (75%), Breadth Score (15%), and Full Clear Tendency (10%), mostly a measure of experience, with smaller nudges for variety and for finishing what you start.

The Generalist Sherpa Score blends both kinds together: Raid Experience (45%), Dungeon Experience (30%), a raid-leaning blend of both Breadth Scores (15%), and a raid-leaning blend of both Full Clear Tendencies (10%). Raids are weighted more heavily throughout since sherpa-ing a raid is typically the bigger ask.

A few caveats

• Raid and dungeon release order (used for recency weighting) is curated by hand, since Bungie's API doesn't expose usable release dates for activities. Brand-new content is always treated as the most recent until the list is updated.
• If a Post-Game Carnage Report fails to load for a given instance (rare, but it happens), that completion is skipped rather than guessed at, and a warning is shown on the profile page.
• Scores are a heuristic, not an official Bungie or community rating; they're meant as a rough, consistent way to compare raid/dungeon experience across players, nothing more.

Not affiliated with Bungie. All Destiny 2 data is provided via the Bungie.net API.