Rust Data LabData lab · live
Live readings Servers11,672 Players34,284 Populated2,842 Fresh wipes · 3h85 Sampled every 5 min

Element card · group Community · atomic number 15,963, its rank

my_server

Offline 92.208.255.97:28015 checked 23d ago

Join the experiment
Atomic mass · players now 0/ 500 0% full Room to join
7-day average0peak –
Rank · atomic number#15,963top 71%
Last wipe23d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
No hourly history yet.

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
This server has not answered a direct query in the last 48 hours.

48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory. From asking the server directly; low fps and a climbing entity count mean lag.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k5 Oct6 Oct8 Oct9 Oct11 Oct12 Oct

Top 71% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 5 Oct, 14:27 UTC23d ago 0 – running 0

Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Ru Rusty Moose |E… 140
    Rusty Moose |EU Mondays| EU · groups of 12+ · weekly · 555 on average 140/ 250
  2. 2 Ru Rustoria.co - … 112
    Rustoria.co - EU East Long EU · groups of 12+ · monthly · 319 on average 112/ 200
  3. 3 Ru Rusty Moose |E… 14
    Rusty Moose |EU Main| EU · groups of 12+ · weekly · 291 on average 14/ 250
  4. 4 Ru Rustoria.co - … 18
    Rustoria.co - EU Main EU · groups of 16+ · weekly · 286 on average 18/ 250
  5. 5 Ru Rustafied.com … 11
    Rustafied.com - EU Friday EU · groups of 16+ · weekly · 274 on average 11/ 100
  6. 6 Ru Rustoria.co - … 15
    Rustoria.co - EU East Medium EU · groups of 12+ · biweekly · 250 on average 15/ 200

Quick answers

from the figures on this page

Map and rules

What map is in play on my_server?

A procedural map runs on my_server, generated by the game.

How is my_server configured, and what rules apply?

The name of my_server carries no gather rate. With no change from the default, groups can hold up to 8 players. Play runs as survival, raiding, building and gathering: the standard game. You can fight other players and raid them. It appears under Community in the server browser. VAC is on, Valve's anti-cheat.

About the server

Which location is my_server based in?

Nothing about a region is published by my_server. What a server states is what Rust Data Lab shows for location; no lookup of the machine's whereabouts is made. 92.208.255.97:28015 is the address it uses.

What Rust version does my_server currently run?

Rust network protocol 2634 and build 166757 on Windows is what my_server uses. Joining requires the same protocol on your game; Steam takes care of updating it.

How dependable is my_server for staying online?

Right now my_server is offline, with its last appearance 23 days 8 hours ago. For the last 7 full days, 0 of 168 hours were online, giving 0% uptime. On 5 October 2026, Rust Data Lab saw it for the first time.

Wipe days

How often does a wipe happen on my_server, and at what time?

The record holds too few of my_server's wipes to show its rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. 23 days 8 hours ago the current world was made.

On my_server, what happens when wipe day arrives?

At their busiest, recent wipes averaged 0 players. The latest wipe's peak fell 0 hours after it began.

Tags, lists

What should you understand from the tags my_server carries?

gmrust (Game mode): Survival in the standard Rust style; mp500 (Max players): It has 500 slots; ts8 (Group limit): This uses the game's default: 8 per team; v2634 (Protocol): Protocol 2634 is required; join only if your game matches it; cs166757 (Build): Build number: 166757; ptrak (Networking): This runs on RakNet, the standard layer; $r? (Region code): A region code has not been set here: that is the tag list my_server publishes, and the game's server browser reads it. Current players, the queue and the world's creation time sit in the tags too, shown at the top of this page.

Which Rust Data Lab filters and lists does my_server appear in?

You will find my_server on the following Rust Data Lab lists: Rust community servers, measured. You can find it on the server list by applying these filters: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Player counts

Against other Rust servers, where does my_server place?

Player hours over the last week put my_server at #15,963, inside the top 71% of ranked servers.

What does the current player count on my_server tell you?

No live signal from my_server right now, which was last seen 23 days 8 hours ago.

Connection

What is the way to join my_server?

Open the console with F1 in Rust and type client.connect 92.208.255.97:28015. The Launch Rust button on this page does the same job through Steam.

Server tags

what each one means

Published as mp500,ptrak,$r?,v2634,gmrust,cs166757,ts8

Game

gmrust
Game mode Survival in the standard Rust style.
mp500
Max players It has 500 slots.
ts8
Group limit This uses the game's default: 8 per team.
v2634
Protocol Protocol 2634 is required; join only if your game matches it.
cs166757
Build Build number: 166757.
ptrak
Networking This runs on RakNet, the standard layer.
$r?
Region code A region code has not been set here.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.