How we measure

Every figure on CamsAddict comes from one source: the public list of online rooms that a cam network publishes for its affiliate partners. This page explains what we read, how often, and how those snapshots become broadcasts, viewer counts and schedules. Who we are and how the site is funded: About CamsAddict.

1. What we collect, and from where

We read the "online rooms" feed that each cam network provides to its affiliates. For every room that is online it tells us, among other things, the username, how many people are watching, how many followers the model has, which type of show the room is in and, on some networks, how long the room has been live.

Chaturbate is published on the site today. Other networks are collected in the background first and only appear once we have enough history for their statistics to mean something.

2. How often, and what a complete snapshot is

We take a snapshot of each network every three minutes (180 seconds), measured from the start of one snapshot to the start of the next. If a network starts refusing requests because we ask too often, we slow down to every five minutes until ten snapshots in a row go through cleanly.

A snapshot is complete only when every page of the feed loaded without an error, at least 90% of the rooms the network said were online came through, and the number of rooms did not fall below half of the previous complete snapshot (which would point to a cut-off feed).

If a snapshot is incomplete we still record the rooms that did arrive, but we never use it to decide that anyone has gone offline. When a network's feed fails we leave a gap; we do not fill it with estimates.

3. What counts as a broadcast

A broadcast (we call it a session) starts when we see a room in the feed that has no open session. Where the network reports how long the room has been live, we use that to date the start, so the start can be earlier than our first snapshot; where it does not, the start is the first snapshot. A new session never starts before the previous one ended.

A session ends when the model is missing from two complete snapshots in a row, about six minutes. The end time we record is the last snapshot in which we saw the model, not the moment we noticed they were gone. Missing a single snapshot does not end a session, and an incomplete snapshot never counts as missing.

If a model reappears and the network says the room has been live since no later than five minutes after the recorded end of the previous session, we reopen that session instead of starting a new one. This repairs the cases where we simply lost sight of a room.

Accuracy: end times are accurate to within one snapshot interval. Start times are as accurate as the network's own "time live" figure, or to within one interval where there is none. A broadcast shorter than the interval can fall between two snapshots and never be seen.

A model is shown as live only while it has an open session that we have seen in the last ten minutes. If our collection ever stops, nobody stays "live" on the site.

4. What "viewers" means

The viewer count is the number the network reports for the room in each snapshot. We do not adjust, de-duplicate or verify it. A missing or zero figure is stored as zero.

The peak of a broadcast is the highest count in any of its snapshots, so a spike between two snapshots is not captured. The average is the mean of the counts across all snapshots of the broadcast. The viewer trend on a model page shows that average for each of the model's last 20 broadcasts.

Networks' viewer counts may include people watching through players embedded on other sites, and they are not independently audited. Use them to compare broadcasts with each other, not as a count of unique people.

5. Hours online, schedules and time zones

Hours online is the total time covered by a model's sessions, from start to end (or to the last snapshot, for a broadcast still running). The 7-day and 30-day figures count only the time inside that window, counted back from now. The daily bars use calendar days in UTC over the last 30 days. Active days is the number of those days with any time online, and the streak is the number of consecutive UTC days with time online, up to today (or yesterday, if the model has not been online yet today).

The weekly heatmap covers the last four weeks. For each weekday and hour it shows the share of those weeks in which the model was online at any point in that hour. Weeks before we started tracking the model do not count against it.

"Usually online" is derived from the heatmap: the usual days are the weekdays at least half as strong as the model's strongest day, and the usual hours are the longest run of hours (it can cross midnight) that are at least half as strong as the model's busiest hour. A model needs at least seven days of tracking before a schedule is shown.

The "chance of being online in the next hour" is an estimate from past behaviour, not a promise. It combines the same weekday and hour over the last four weeks (50%), how many of the last seven days the model was online in that hour (30%), and, for a model broadcasting now, how likely the current broadcast is to still be running compared with the length of its recent broadcasts (20%).

All calendar calculations use UTC, because pages are cached and shared between visitors. The server sends times in UTC; after the page loads, the usual hours and the "last seen" time switch to your device's time zone, and hovering shows the UTC value. The heatmap and the broadcast log always show UTC and say so.

6. Private, group and other shows

Each snapshot includes the show type the room is in. We count snapshots as public, private, group, away or hidden; any other value counts as public. A room in a private, group, away or hidden show is still listed by the network, so that time is included in hours online.

The show-time chart on a model page is the share of snapshots in each type over the last 30 days, with away and hidden combined. It appears only when there are at least 20 snapshots, and only counts broadcasts since 7 October 2026, when we started recording show types.

7. Followers

Follower counts come from the same feed. The number on a model page is the last one we saw while the model was online; where a network does not report followers, none is shown.

Once per UTC day, at the first snapshot in which we see the model, we also store that day's count. The gain shown for 7 or 30 days compares the current count with the stored count from that long ago, and is left out if we have no stored count within three days of that date. Follower history started on 7 October 2026.

8. What we do not do

• We do not record or store video.
• We do not store images. Thumbnails are loaded directly from the network, and only while the model is live.
• We do not scrape network pages. We use only the public affiliate feed described above.
• We have no access to models' accounts, earnings, messages or any private data, and we do not use any.
• We do not show the room subject, and tags only while the model is live.

9. How fresh the data is

Pages are generated on request and shared through a cache. A cached page can be up to five minutes old, and while a fresh copy is being fetched an older one can be served for up to fifteen minutes more. With a snapshot every three minutes, expect most figures to be a few minutes behind the network.

10. Corrections and opt-out

If a figure looks wrong, write to [email protected] with the address of the page and what you expected; see also the contact page. Models can opt out at any time: the page is removed, the history is deleted and the model is no longer recorded.