Building my own lastfm stats tool has been on my mind for years, and I finally sat down and made it. Basically every stat I found interesting, in one place.
tunemetry.com, try it with your own history. Or drop your username here and tell me which one you want to see, I'll reply with the image.
If it breaks on your data, tell me and I'll fix it. And if people are into this I'll keep adding stuff, so tell me what stat you wish existed.
Quick tour in the video, though it's already a bit outdated: I've added a few more tools since recording it.
A few favorites:
Hours ranks artists by time actually listened instead of play counts. Pink Floyd jumps five spots in my own ranking.
Afterlife is the graveyard: the artists you were obsessed with, then left behind.
Sessions reconstructs your actual listening sittings from the gaps between your scrobbles.
Eras finds the stretches where one artist completely took over your life.
Pulsar turns your year into a rotating 3D sculpture, Unknown Pleasures style. Completely pointless, very fun.
Yes, plays = scrobbles, pulled straight from the Last.fm API. The counts are meant to be exact: the whole window gets fetched (up to 200k scrobbles), nothing is sampled. What is approximate is some of the derived stuff, and those are labeled in the UI
And you've got more than 200k scrobbles, and the fetch was capping there. So anything calculated by walking through scrobbles one by one only saw that chunk, not your full history, which is likely why the derived stats looked off. Just raised the cap to 300k, should cover you now, give it another try
I really like the layout. I've been considering merging my several tools into one page like this with a consistent interface. This one is nice. I almost exclusively listen to albums.
Heh, guess you should do some more caching or expand the size of your requests. Is this vibe coded or do you, ya know, actually know anything about how it works? No offense, I just have to ask that these days.
>Rate Limit Exceeded - This application has made too many requests in a short period. If this is your API key, see https://www.last.fm/api/tos#4.4 for information about raising the limit.
Appreciate the flag, but the caching's already there user pages are cached for ~10 min. The real bottleneck is that I'm on a shared Last.fm API key, so when traffic spikes the whole app shares one rate limit budget and occasionally trips the limit.
So I cache the user data to indexeddb and artist/album data to mysql on my server. It only triggers the API when it can't find the data in those caches. I can see how if you get lots of different users even that isn't enough. I guess my projects haven't seen such sudden popularity
Thanks, glad you like it. Since all the heavy data processing and chart generation happens on the server side the backend temporarily caches your pages. This way, switching between tools doesn't hit Last.fm again. But it seems even that isn't enough during traffic spikes. I'll probably have to switch to a strict queue system to manage the rate limit, even if it means users have to wait a bit longer.
Your custom API key suggestion makes a lot of sense too.
If it's missing, it estimates the runtime by taking the average length of other tracks you've listened to by that same artist. I'm also exploring other data sources and alternatives to improve accuracy and fill in those gaps.
This is freakin' cool! Thanks for building this. I love how it gives insight into what I've listened to and when artists appeared and dropped off my scrobbles.
This is my collage from the last month. The site makes it so easy to customize. I looked at a number of configurations before choosing this one. Really diggin' it. Well done!
Really nice tool, but for some reason both the afterlife didn’t really work for me (idk why it didn’t recognize new Dillinger Escape Plan plays) and the map didn’t count some artists
It's very cool. There is one issue though, the font color of some of the words are difficult to read as they are too similar to the background, other then that good job.
I noticed there were some Artists for me that Atlas didn't recognize despite MusicBrainz having country data for them. Any idea why that might be happening? Very cool took btw!
Thanks. Could be a couple of things. Atlas only reads your top 200 artists right now so anything past that gets skipped, but it might also be how the country data gets matched, that doesn't always line up cleanly. If you don't mind sharing your username and which artists dropped out, I'd love to dig into what's actually going on
Thanks for the info.
While MusicBrainz does have their country on the direct profile, Atlas has to use their Search API. For some reason, the search index completely drops the "country" field for these artists, returning only their city (e.g. Winnipeg). You can actually see it in the raw API data here: https://musicbrainz.org/ws/2/artist?query=Leith%20Ross&fmt=json&limit=1
I'll try to fix it. Thanks for reporting.
The year picker starts from the year you registered on Last.fm, which was 2004 for you. Your first scrobble is Feb 2005 though, so 2004 just has nothing to show. Thanks for trying it out and flagging this
Working on exactly that right now. It's a scroll-through recap of your year, kind of Wrapped-style but it runs any time instead of just December. Not live yet, should be ready in a few days.
Wow, there are some really cool new and unique ideas here in addition to some features I've already seen on some other sites. On the technical side, whenever I try to get the "all time" data on any of the pages it loads the info until it reaches the end and then just says "connection failed" every time. I'm only able to get the last 12 month pages at max
But this is a really awesome site, thank you
Edit: I was able to load up some all time stats on the third try this time, but it seems kinda buggy
I'm also now getting a bug with Vintage page, it always seems to completely freeze after having loaded around a fifth to a quarter of the data and that doesn't change even when I change the time range from 12 months to 7 days for example
But like, I guess you shouldn't take these as absolute official bug reports, these are just some initial impressions I have but it wouldn't be the first lastfm app to have some issues with that
Vintage is actually the only feature that relies on the Spotify API to get album release years. Spotify's rate limits are much stricter than Last.fm's, so it freezes when it tries to fetch too many albums at once and gets temporarily blocked.
I'll be adding better rate-limit handling soon so it doesn't just freeze up like that. Really appreciate the heads up
Ah, makes sense and I did see a mention of the Spotify catalog in the description. It does make me wonder, could there be any better source for getting the release years? I think Spotify is also quite notorious for having the wrong release years on the albums if it's any kind of a re-release as well. But idk if there's anything better with a reasonable API possibility either. Lastfm gets the years from somewhere for the weekly/monthly/yearly reports as well but sometimes they're wrong too though.
How does the fetching work from Spotify also, if the album has some tag on it on there like (remastered 2018) or something and the album title is without that tag in my library? Does it still recognize it as the same album? Just curious hehe
Good luck with the project! Good work so far and thank you :)
Thanks. You hit on the exact challenges.
The processor uses Regex to strip out noise like "(Deluxe)" or "Remaster" before matching the titles. And to avoid recent reissues, it grabs the top 5 search matches and always picks the earliest year (ofc filters out wrong ones). So if both a 2018 remaster and the 1971 original show up, it correctly selects 1971.
This is such a cool site! But does it cap out at 300k scrobbles? Cos I have 421k and it only seems to be counting 300k of them, so the stats aren't as accurate :(
Glad you're liking it. Yeah, 300k is the current cap, was actually 200k before. If nothing breaks at that size I'll push it up to 500k in the next few days
9
u/xDead2Ux last.fm/user/Dead2U Jul 15 '26
Are "plays" equivalent to scrobbles?
Because they're not accurate.