Analytics
The Stats page (Growth, Activity, Moderation and Regulars), the VRChat and Discord pages' This week, the Bluesky page, and where the numbers come from.
The charts and numbers over time for every part of your community are on one page, Stats, at the top of the sidebar under Now and Chat. It has a tab for each question:
| Tab | The question it answers |
|---|---|
| Growth | Is the community growing or shrinking, and what changed? |
| Activity | When is the community busy, and where? |
| Moderation | Who is doing the moderation work, and when is nobody covering? |
| Regulars | Do people come back, and who comes every week? |
In each tab, the VRChat group and the Discord server have a part of their own, under their names. Nothing adds the two together: a VRChat join and a Discord join are not the same kind of thing.
The VRChat and Discord pages, under Integrations in the sidebar, show the group and the server the way VRChat and Discord do. Each keeps This week: four numbers for the last seven days, each against the seven before. Its heading opens Stats.
The Bluesky page, beside them, shows the group's Bluesky account the way Bluesky does: banner, picture, name, handle, followers, following, posts and bio, then a Posts tab (what Modbot sent, with likes, reposts and replies) and a Replies tab (the replies, mentions and quotes kept in the audit log). Edit profile changes the name, bio, picture and banner on Bluesky.
Stats and the VRChat, Discord and Bluesky pages need the See analytics permission (roles and permissions). The built-in Moderator and Viewer roles have it. Without it, the pages are hidden from the sidebar and Modbot refuses their data.
Clicking the Integrations heading itself opens a different page, Integrations: a card each for VRChat, Discord, Email, Google Calendar, Bluesky and Twitch, with its status and a Set up button that opens the part of Settings where it is set up. It is about setting things up rather than numbers, so it needs Change settings instead of See analytics. Without Change settings the heading only groups the VRChat, Discord and Bluesky pages.
Team and Worlds moved
Until September 2026 the charts were spread over five pages: Team, VRChat, Worlds,
Instances and Discord. Team is now the Moderation tab and Worlds is part of the Activity
tab. Their old addresses, /analytics/team and /analytics/worlds, open those tabs.
Date ranges
Stats has range buttons at the top, shared by its tabs: 7d, 30d (the default), 90d and All time. Regulars offers only 90d and All time. The dates the range covers are shown on the right.
- Ranges are whole days in UTC, and include today. Today's figures are still filling in.
- All time starts at the first day Modbot has anything recorded.
- Switching range keeps the old figures on screen until the new ones arrive.
A few panels ignore the range because they describe now, such as who is a member today. They are noted below.
Where the numbers come from
The pages draw on two kinds of stored data.
Daily totals are counts per day: joins, leaves, messages, bans, instances opened, actions per moderator, and so on. Modbot works them out from its record of events about every 15 minutes, so a chart can be up to about 15 minutes behind. Daily totals are kept forever, even if you set Modbot to delete old events.
The fact log is Modbot's record of individual events (a join, a role change, a person seen in an instance). Panels that need to pair events up, such as "did this invite lead to a join?" or "how long was this instance open?", read the fact log directly. If you have set data retention, old events are deleted, and these panels can only cover what is left.
Data covered
At the bottom of every page, the Data covered card says:
- Daily totals cover: the first and last day with daily totals, and when they were last updated.
- The fact log covers: the first and last day with stored events.
- Facts kept for: how long moderation events and presence events are kept, or forever.
If a chart looks empty or short, check this card first. A deployment that started recording last week has no figures for last month, and a short retention window shortens the fact log panels.
Presence reports
Some figures (time spent in worlds, visitors, who was in an instance, times left without a moderator) come from presence reports: who the companion saw in an instance while a moderator with the client was there. VRChat does not report who is in an instance any other way.
Modbot only knows who was in an instance while a moderator's companion was reporting from it. Nobody with the client in the instance means no presence reports at all, and every figure built on them then reads as nought however busy the instance really was. That is not a fault and it is not an estimate: it is the limit of what VRChat will tell anybody.
What this means for a figure drawn over a range:
- A world nobody with the client visited looks empty.
- "The most people seen in one instance" is the most seen, which is at most the most there were.
- A busy Saturday nobody covered leaves no trace, so it cannot pull an average or a peak up.
Where a page's figures rest on presence reports, it counts them for you and says so when they are thin: No presence reports in this range, or Only 84 presence reports in this range. Treat anything below a few hundred as a sample rather than a measurement.
Head counts
Some figures (People in instances, and the peaks on the Activity tab) come from head counts instead, and these are not limited by who was in the instance. Modbot reads each of the group's open instances' own page about every thirty seconds and keeps VRChat's own count of how many people are in it.
No moderator and no companion is involved, so head counts cover instances nobody from the team was standing in. What they cannot tell you is who those people were — only how many. That is why the two sources sit side by side rather than one replacing the other.
A count is stored only when the number changes, so an instance that sits at twelve people all evening is one stored reading, not a thousand. Charts drawn from head counts are therefore a staircase: each reading holds until the next one.
Head counts start when Modbot starts reading an instance, so they can still be incomplete:
- An instance that opened before Modbot was set up, or while the group's instance list could not be read, has no counts for that part of its life.
- If VRChat rate limits Modbot, reading stops until the limit clears and nothing is counted in between. Health shows when that is happening.
The Activity tab measures exactly this and says so — see Coverage below.
VRChat
Discord
The Discord page needs the Discord bot. Under the server's header, In voice lists the voice channels with somebody in them and who is in each, as Discord's channel list does. It is there for anyone who may open Live, and is read again every 30 seconds. Then This week has New members, Talked, Messages and Time in voice for the last seven days, each against the seven before. Press This week to open the Activity tab of Stats.
The server's charts are on Stats: who comes and goes on Growth, messages and voice on Activity, and moderation actions on Moderation.
For every panel in detail, and how messages are stored, see Discord messages and analytics.
The Roles and Channels tabs in the row under the header list roles nobody holds or that look alike, and channels nobody writes in. See Roles and channels. The Invites tab shows which invite new members used. See Invites. The Account links tab shows what share of the group and the server has linked a VRChat and a Discord account. See Account links. The Snapshots tab saves the server's roles, channels and permissions and shows what changed. See Server snapshots.
Instances
The Instances tab of the VRChat page, in the row under the group's header, shows what
vrchat.com shows there: Open right now (group instances open at this moment, when there are
some) and Recent instances (the most recent instances of the last 30 days). The command palette
finds it as Instances, and g then i opens it. Its address is /analytics/instances.
The charts about when the community is active are on the Activity tab of Stats.
Stats
The page opens on Growth. The tabs are at /stats/growth, /stats/activity and
/stats/moderation and /stats/regulars; g then t opens Stats, and g then w opens Activity. Each tab starts with
the Insights that answer its question, if AI insights are set up.
Growth
Is the community growing or shrinking, and what changed?
VRChat group
The stats along the top:
- Members: the group's member count as VRChat last reported it, with the date it was read.
- Joined and Left: joins and leaves recorded in the range.
- Net change: joined minus left in the range.
Then the peak, with the moment it happened, in your own time zone:
- Most members: the highest member count VRChat reported in the range.
It is read from the five-minute member count readings, so the moment shown is a real reading and not a day. Where the same number was reached more than once, the earliest time is shown, so the figure does not move about between two loads of the same page.
What the peaks rest on. Modbot can only find a peak among the readings it has. If the range reaches back further than Modbot has been running, or retention has deleted the older readings, the peak is the highest Modbot saw and not necessarily the highest there was. When fewer than half the days in the range carry a reading, the page says so above the stats — Readings on 2 of 30 days in this range — and with no readings at all, No member count readings in this range.
| Panel | What it shows | Comes from |
|---|---|---|
| Member count | The member count VRChat reported, reading by reading, with the number of members online in VRChat drawn over it in green on its own scale at the right. Hover a point for both numbers and the time it was read. | Member count readings |
| Joins and leaves per day | Joins and leaves, side by side, per day. | Daily totals |
| Joined minus left, running | A running total of recorded joins minus recorded leaves, counted from zero on the first day Modbot recorded. This is not the member count: a group that already had 5,000 members when Modbot started still starts at zero. | Daily totals |
| Invites and join requests | Invites sent; Invites accepted (the share of invited people who joined within 7 days); Join requests; Requests decided (approved / rejected); and a chart of invites and requests per day. | Daily totals, except invites accepted (fact log) |
| Roles | Each role VRChat lists for the group, with how many times it was Given and Taken away in the range. Badges mark moderation roles, roles given on join and self-service roles. Shows when the role list was last read. | Fact log |
| How long members have been members | Current members grouped into Under 7d, 7d to 28d, 28d to 3mth, 3mth to 1y and Over 1y. | Fact log |
Member count has range buttons of its own: Day, Week (the default), Month and All. Modbot reads the group's member count and online member count about every five minutes and keeps every reading. Long ranges show up to about 500 of them, spread evenly across the range; before the first stored reading, the chart shows one point per day from the group's recorded changes. Readings older than the presence retention window are deleted if one is set.
How long members have been members ignores the range: it is about who is a member now. It only counts members whose join Modbot recorded, and says how many that is. Members who joined before Modbot started recording are not counted here.
Discord
Members, joins and leaves, the member count, new members who stayed, and who the members are now (links to VRChat, new accounts joining, how long members have been here). A line at the top says how many channels the bot can read and whether it can read the audit log. See Discord messages and analytics.
Activity
When is the community busy, and where?
VRChat instances
The stats along the top are Most online at once (the most of the group's members in VRChat at the same moment, anywhere, not only in your instances), Opened, Manually closed and Naturally ended (instances in the range), Typical time open and Most open at once.
Peaks
Under them is a second row of peaks, each with the moment it happened, in your own time zone. All four are built from head counts — VRChat's own numbers — so they cover instances nobody from the team was standing in.
| Stat | What it counts |
|---|---|
| Most people at once | The most people in all of the group's instances added together, at one moment. |
| Fullest instance | The most people in a single instance at one moment, with the world it was in. |
| Busiest day | The day with the most people-time, shown as the most people in instances at once that day. |
| Busiest hour | The single clock hour with the most people-time, on a real date — not "Saturdays at 8". Shown as how many people were there on average, to the nearest person; hover it for the exact figure. |
People-time is people added up over the minutes they were there: one person for an hour and sixty people for one minute are both one hour. Busiest is measured that way rather than by the peak, because a night that touched forty people for five minutes is not a busier night than one that held twenty for six hours. For "Saturdays at 8" — the same hour across weeks — use When the community is active below.
Where the same height was reached twice, the earliest moment is shown, so the figure does not move about between two loads of the same page. A range with nothing recorded shows a dash rather than a zero: nothing was recorded is not the same statement as the peak was nought.
Coverage
A peak is only as good as the time Modbot was counting. Two hours of counting in a week gives a peak that is real and is not the week's peak, and nothing about the number itself says which one you are looking at. So the page measures it.
Modbot compares two amounts of time inside the range:
- how long the group's instances were open, added up across instances, and
- how much of that time it actually had a head count for — an instance counts from its first stored reading onwards, and one Modbot never read contributes nothing.
When the second is less than half the first, the page says so above the stats: Head counts cover 19% of the time instances were open. With no head counts at all in the range, it says No head counts in this range.
The peaks are still shown when coverage is thin. They are marked, not hidden — a real peak from a short window is still worth seeing, as long as you know that is what it is.
Panels
| Panel | What it shows | Comes from |
|---|---|---|
| People in instances | People in all of the group's instances, moment by moment, with how many instances they were spread across drawn over it in green on its own scale at the right. Hover a point for both numbers and the time. | Head counts |
| When the community is active | A week-by-hour grid. Switch between People arriving and Instances opened. Hours are shown in your own time zone (named in the title), rounded to whole hours. | Presence reports (arrivals), instance list (instances opened) |
| Opened, manually closed and naturally ended per day | Instances opened, closed by a moderator and ended on their own each day. | Daily totals (opened and manually closed), instance list (naturally ended) |
| Most open at once, per day | The most group instances open at the same time each day. | Instance list |
| Most people at once, per day | The most people in all of the group's instances at one moment, each day. | Head counts |
| Busy time per day | People-time per day, in hours. A long steady evening reads higher than a short rush. | Head counts |
| Typical time open, per day | The middle time from open to end, over the instances that ended that day, however they ended. The stat at the top is the same figure for the whole range. | Instance list |
| Most people seen in one instance, per day | The biggest crowd a moderator's companion saw in a single instance each day. | Presence reports |
People in instances has range buttons of its own: Day, Week (the default), Month and All, because it is drawn from readings taken every thirty seconds rather than from whole days. Long ranges show up to about 500 readings spread evenly across the range, and every point is a number VRChat reported at the time shown. The line is a staircase because a count is stored only when it changes: each reading holds until the next.
Most people at once, per day and Most people seen in one instance, per day look similar and are not the same figure. The first is every instance added together, from VRChat's own counts, and is complete whether or not anyone was watching. The second is one instance at a time, from what a companion actually saw, and is nought on a day nobody with the client was around. If the range has fewer than 200 presence reports the page says so, and with none it says so in that panel too.
VRChat only records an instance closing when a moderator closes it by hand, and that is what Manually closed counts. Most instances just empty out and drop off the group's list. Modbot sees that in its own instance list, and those are Naturally ended: the ended instances no moderator closed. Typical time open, Most open at once, the opening hours in the grid and the worlds and team figures all count from that instance list, so an instance that emptied out is counted with the time it really ended. Each natural end also gets an entry in the audit log: "ended on its own", written by Modbot and never worded "closed". It is written only after the audit log has been read past the end, so a close by hand that VRChat reports late is not labelled that way. The first time Modbot runs with this, it adds an entry for each instance that ended before, dated when it ended; those are not posted to Discord. Instances that ended before Modbot began reading the audit log get "ended on its own" too, because any close by hand from then cannot be known.
VRChat worlds
If there are no presence reports in the range, the page says No presence reports in this range. If there are fewer than 200, it says how many, as a reminder that the figures are thin.
The stats along the top are Worlds, Time seen, Visitors and Presence reports.
Worlds, by time people were seen in them lists each world with:
| Column | Meaning |
|---|---|
| World | Name, author and world id. Click the name to open the world. |
| Holds | The world's capacity. |
| Time seen | Total time people were seen in the world. |
| Visitors | Different people seen there. |
| Arrivals seen | Times someone was seen arriving. |
| Instances | Group instances Modbot saw open in the world: the same instances the world's popup lists. |
| Last seen | When someone was last seen there. |
Visitors per day, busiest worlds charts visitors per day for the five busiest worlds.
Time, visitors and arrivals come from presence reports. Instances comes from Modbot's own instance list and is complete whether or not a client was there. Visitors per day comes from daily totals and outlasts a short retention window.
Discord
Messages and voice, active members, the busiest channels and hours, who went quiet and the top contributors. Names open that person's popup. "Active" means the person sent a message or spent time in voice; bots are never counted.
Moderation
Is moderation keeping up, and is the team OK?
Team
Moderation work is counted in two kinds that are never added together:
- Actions on people: instance kicks, warns, bans, removals from the group and join requests rejected. These are the actions Reviews count.
- Door and admin: invites, join requests approved, unbans and role changes.
A moderator who lets people in and hands out roles is not one who throws people out, and one total would make them look the same.
You
Your own numbers come first: Actions on people, Door and admin, Days active (days you took any action) and Actions on people per active day. Beside each is the team middle: half the moderators active in the range are at or below it. Beside the last is also your usual: the same number over the 90 days up to yesterday, the one Reviews compare a busy day against. The team middle is left out when fewer than four moderators were active, because on a team that small it would be one person's own number or give it away. Your numbers are found by the VRChat account linked to your Modbot account.
The stats along the top
- Moderators active: how many people took a moderation action in the range.
- Actions on people and Door and admin: the team's totals.
- Left without a moderator: how many times the last moderator left an instance while people were still in it (see below).
- Instances with no moderator in them: group instances (from Modbot's instance list) that opened with no companion in them while they ran, out of all instances opened.
Left without a moderator
A gap is a stretch of time when people were in a group instance and no moderator was. It starts when the last moderator leaves while people are still there, and ends when a moderator is seen again or the instance closes.
A moderator counts as present when their companion is reporting from the instance, or when another client sees someone Modbot recognises as a moderator (they hold a role with moderation permissions, have taken a moderation action, or own the group). A moderator without the client, in an instance no client is in, cannot be seen at all.
The buttons (1+ people, 3+, 5+, 10+) say how many people in one instance mean it wants a moderator. The group's choice is saved: it starts at 3+, and when somebody with Change settings picks another, it is saved for everybody. Anyone else can pick another to look at, and it is not saved.
The grid shows the hours of the week, in your own time zone. An hour is busy when a group instance held at least that many people at some point in it, by VRChat's own head count, which needs no companion. The darker a square, the more of that weekday's busy hours at that time had nobody on: a gap was open in a busy instance. A striped square had busy hours no companion reported from, so Modbot cannot tell whether a moderator was there. Point at a square, or tap it, for "Fri 20:00 · 3 of 4 busy hours with nobody on · 1 not seen".
The table lists the gaps with at least that many people left behind:
| Column | Meaning |
|---|---|
| Began | When the last moderator left. |
| Lasted | How long until the gap ended, or "unknown". |
| People left behind | How many people were there when the last moderator left. |
| Last moderator out | Who left last, or "a client stopped reporting". Only with See the audit log. |
| Ended because | "a moderator arrived", "the instance was closed", or "nothing more was reported". |
| Instance | The world (click to open it) and instance number. |
How long things wait
The middle wait of everything decided in the range, so one request left over a weekend does not outweigh the rest:
- Join requests: from the request to its approval or rejection, from VRChat's audit log. A join by invite is not counted: either no request came before it, or the request was already answered.
- Flags: from when an AutoMod rule flagged something to when a moderator dismissed it or confirmed it.
- Reviews: from when a review opened to when it was closed.
Under each is how many were decided. The chart shows the chosen one's middle wait for each day something was decided.
Acted on again and Bans lifted
- People acted on: people with an action on them in the range, of the kinds the repeat offender rule counts. Acted on again within 30 days: how many of them had another such action in the 30 days before one of those.
- Bans: bans in the range. Lifted within 30 days: of the bans in the range that are at least 30 days old, how many were lifted within 30 days, however they were lifted; under it, that as a share and how many bans it is out of. A newer ban has not had its 30 days yet, so it is left out rather than counted as one that stood.
- Under them, the reasons picked when a ban was lifted from Modbot in the range, most used first, and No reason given for lifts without one. A ban lifted in VRChat itself has no reason.
These are the team's numbers. They are never shown per moderator.
Actions
- Actions per moderator: only with See the audit log, which already shows who did what. One row per moderator with Actions on people, Door and admin, Days active, a column per kind of action (Instance kicks, Warns, Bans, Removed from group, Requests rejected, Invites, Requests approved, Unbans and Role changes) and the day they were Last active. Rows are sorted by last active, most recent first, then by name, so whoever has gone quiet is at the bottom; never by how much anybody did. Click a name to open their popup.
- Actions per day: actions on people or door and admin per day, by the buttons.
- What kind of actions: each kind of action, largest first.
People who can review tickets also see a Reviews of unusual patterns → button that opens Reviews: on Actions per moderator, or on Actions per day for someone who cannot see each moderator.
The action counts come from daily totals. Gaps come from presence reports in the fact log, and busy hours from VRChat's head counts.
Discord
Moderation actions per day: bans, kicks, timeouts and messages removed. Without the audit log, kicks and removed messages are missing, and the panel says so.
Regulars
Do people come back, and who comes every week?
Only the VRChat group has this tab: it is counted from joins, which Discord does not have in the same sense.
The words mean exactly this:
- A visit is a join: Modbot's companion saw a person arrive in one of the group's instances, or already there when it arrived.
- A visitor in a week is anybody with a visit in that week. Weeks run Monday to Sunday, in UTC.
- A visitor came back if they have a visit in any of the next four weeks. Any of the group's instances counts, not only the same world or the same kind of instance.
- The week's return rate is the visitors who came back, out of all its visitors.
- A regular joined in at least three of the latest four whole weeks. The week still under way is not one of the four. The numbers three and four are fixed; Modbot does not ask you to choose them.
Because a visit needs four more weeks to be told apart from a person who simply has not come back yet, a week's return rate is drawn only once those four weeks are over: the latest weeks on the chart are five weeks old or more. That is also why the tab offers 90d and All time and not the short ranges, and why it reads 90 days when the rest of Stats is on a shorter range.
The stats along the top:
- Regulars: how many people are regulars now.
- Came back: the return rate of the latest week that has one, with the week named under it.
- Visitors that week: how many people that rate is out of.
Visitors who came back, per week is the rate for each week as a percentage. Point at a week, or tap it, for its visitors. A week nobody was seen in has no point.
The regulars are listed below, the most days first, with how many of the four weeks and how many different days they joined in, and when they last joined. The name opens the person. The list shows the first 200 and says how many there are when there are more.
All of it comes from presence reports, so it only sees time a moderator's companion was in the instance. A person who came back to an instance nobody from the team attended is not counted as having come back, and a regular who mostly joins unattended instances may not show. Read the rate as at least that many came back, and treat a week with few visitors as a sample. If you have set data retention for presence events, weeks older than that cannot be counted.
Call log
Every AI call Modbot made — feature, model, tokens, cost, time taken and what went wrong — and what the model was sent for the calls that flagged something.
The VRChat group page
The VRChat page, which shows your group the way vrchat.com does, with its tabs, Overview cards, Posts, Gallery, Invites, Settings and Roles, and what each needs.