Why Are My Stats Missing or Incomplete on lastfmstats.com?
Updated
lastfmstats.com reads your public Last.fm scrobble history and turns it into enhanced statistics, so missing or incomplete stats almost always trace back to one of three things: your Last.fm listening data isn't publicly visible, the username you entered doesn't match your account, or the site hasn't finished pulling your history yet. Work through the checks below in order — most cases are resolved by the first one.
Check whether your Last.fm data is publicly visible
lastfmstats.com can only analyze scrobbles that Last.fm exposes publicly. If your listening data is hidden or restricted, the site has nothing to read.
- Log in to Last.fm and open your Settings → Privacy.
- Confirm that your listening data (recent tracks / your library) is set to public rather than private or visible only to you.
- If you recently changed this setting, give it a moment and reload lastfmstats.com — the change needs to propagate before the site can see your history.
If you want your stats on lastfmstats.com, your Last.fm profile effectively has to be public. There is no separate lastfmstats.com account or permission that overrides this.
Confirm the username is correct and has enough history
A single typo produces an empty or partial result that looks like a data problem.
- Re-enter your Last.fm username exactly as it appears in your profile URL (
last.fm/user/yourname). Usernames are case-insensitive but must otherwise match. - Make sure you're entering a username, not your email or display name.
- Check that the account actually has scrobbles. A brand-new account, or one that has barely scrobbled, will show thin or empty statistics simply because there's little to compute from.
- If you have scrobbles spread across a very long history, expect the first load to take longer and some sections to populate before others.
Account for scraping delay and temporary failures
lastfmstats.com builds its output by pulling your history from Last.fm, which takes time and can be interrupted.
- First-time load: a large library can take a while to process. If numbers look partial, wait and reload rather than assuming the data is wrong.
- Recent scrobbles missing: the newest tracks may not appear immediately, since the site has to fetch them after Last.fm records them. A short delay is normal.
- Whole page empty or erroring: this usually points to a temporary problem on lastfmstats.com or with the Last.fm API rather than your account. Try again later, and try a different browser or a private window to rule out caching or extensions.
Quick diagnostic table
| Symptom | Most likely cause | What to do |
|---|---|---|
| Nothing loads at all | Private Last.fm data, or site/API outage | Make listening data public; retry later |
| Wrong or empty profile | Username typo or wrong identifier | Re-enter exact Last.fm username |
| Very few stats | New account or little scrobble history | Confirm the account has enough scrobbles |
| Recent tracks absent | Fetch/scrape delay | Wait and reload |
| Some sections blank, others fine | Partial load still in progress | Reload after processing finishes |
When it still doesn't work
If your Last.fm data is public, the username is correct, the account has a solid scrobble history, and the site still shows incomplete stats after several retries, the remaining explanation is a temporary fault on lastfmstats.com's side. In that case there's nothing to fix in your own settings — check back later.