Skip to content
Statistics

Who uses what — and what just lies there

Disks are the one thing about a setup like this that really costs money — and the one thing that eventually fills up. Buy another one without knowing where the space went, and you pay for the same show twice: once as a file and once as a hard drive.

So Nexview has a section of its own for figures, and it holds two views. One describes the operation: who requests, what actually arrives, how happy everyone is with it. The other describes the space: what has been sitting there for years without anyone watching it. Both are for the people who approve — administrators and approvers.

The first view

Six numbers before you click anything

The key figures come first: requests in total and from how many people, how many of them finished downloading, how many are still waiting for a decision, and the average rating. Plus two that are otherwise easy to miss — ratings of two stars or fewer, and written feedback nobody has answered yet.

Below them two charts: requests per month, split into movies and shows, and how often each number of stars was given. The first says whether the place is growing; the second says whether the titles land well.

And then the space used per person. That is the number this is really about: not how much is free, but whose the occupied gigabytes are. Whatever belongs to nobody stands next to it as the house library — titles that are there for everyone, or whose account is gone.

Screenshot: the statistics view with key figures for requests, downloads, pending approvals and ratings, below them the monthly history and the distribution of the space used
The state of the place on one page. Key figures at the top, below them history, ratings and how the space is split — here 73 % of the attributed gigabytes belong to a single person.
Per person

Who requests, who occupies, who is happy

One row per account: requests, the split into movies and shows, how many of them finished, the success rate, both quotas, the space used against the limit, and the average rating.

The success rate is the column that explains the most. Someone who requests a lot and receives little either has a taste for titles that do not exist as files, or keeps running into a limit. Either way you would otherwise only find out once they complain.

An account over its limit stands in red — here 71 of 50 GB. That is not a punishment and not a block, the number simply sits there. What follows from it is decided by the person reading the page.

Screenshot: the per-user table with requests, success rate, both quotas, storage used and average rating
One row per account. Success rate, quotas and space used side by side — an account over its limit stands out at a glance.
The second view

What is lying around unused

The second view turns the question around: not who fetched something, but which of it nobody watches any more. Biggest first — when clearing out, what counts is not the number of titles but the space they take.

A title only appears if nobody watched it within the chosen period and it has been here at least that long. The period is yours to pick: three, six, twelve or twenty-four months. Something downloaded recently therefore does not show up — otherwise every new arrival would land on the list straight away.

Per row: size, when it was last watched, how long it has been here, who watched it, who it is attributed to, and how it was rated. Shows appear season by season, not as one item — clearing out happens season by season too.

Screenshot: the list of unused titles, biggest first, with size, last watched, how long it has been here, who it is attributed to, and a delete button per row
15 items, 397 GB together. The yellow note above says unprompted how many accounts the watch data comes from — and whose is missing.
Before anything disappears

Deleting on a deadline, not on a shout

Two ways stand side by side in the dialogue: delete now, or with fourteen days' grace. The grace period is the actual suggestion, and it is more than a waiting time.

During those fourteen days the title stands on the home page for everyone to see, everyone connected to it is told — and whoever watches it in that time cancels the deletion by doing so. No button, no objection, nobody has to ask. Knowing the outcome in advance saves the argument.

Deletion goes through Radarr and Sonarr, not around them. If a recycle bin is set up there, the file lands in it first; without one it is gone immediately and for good. That stands in the dialogue before you press — not in a manual you read afterwards.

Screenshot: the delete dialogue with the choice between deleting now and fourteen days' grace, plus the note about the recycle bin in Radarr and Sonarr
The grace period is the suggestion. The red button is the one with the fourteen days — deleting now sits beside it, quietly.
Honestly

What Nexview cannot know

“Last watched” is only as good as the accounts that are linked. The watch data comes from the media server. Whoever has not linked one does not appear in this calculation — what they watch, Nexview simply does not know. The list says so unprompted: above the table it states how many of the existing accounts the watch data comes from and which are missing. Without that sentence half a truth would look like a whole one.

And sometimes Nexview knows that someone watched something but not when — media servers keep the two apart, and a trimmed history leaves the counter standing while the timestamp disappears. The row then does not say “never” but “watched – when is unknown”. Such items stay in the list and are counted above the table: leaving them out would hide exactly the oldest ones.

“Here since” comes from Radarr and Sonarr, not from Nexview — it is the date the file was created there. Items still missing it are skipped and counted above the table, rather than quietly left out. The sync runs hourly and fills it in.

And both views see only the library itself, not the disk. Whatever sits outside Radarr and Sonarr — files copied by hand, a second folder, old backups — does not count here. The figures describe what Nexview manages; they do not pretend to know the drive.

Nexview uses TMDB as its data source but is not from TMDB and is not endorsed or certified by TMDB. The screenshots come from a test installation; the accounts and requests shown in them are made up.

Nexview is published under the AGPL-3.0 licence. Radarr, Sonarr, Plex, Docker, Synology, IMDb, Rotten Tomatoes, Metacritic and JustWatch are trademarks of their respective owners and are named here for descriptive purposes only. Some of the icons on this page are based on Lucide (ISC licence) — copyright held in part by Cole Bemis 2013–2022 as part of Feather (MIT licence), otherwise by the Lucide contributors from 2022.