TestServer
Offline 91.11.200.94:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
20% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| No wipe seen yet. | ||||
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- 260/300
- 15/250
- 31/250
- 119/200
- 45/200
- 49/100
Quick answers
from the figures on this pageWipe schedule
When does TestServer wipe?
To tell the rhythm of TestServer, too few of its wipes are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world in play was created 49 days 18 hours ago.
Tags
Which tags does TestServer carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): Slots: 5; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163207 (Build): Game build reading: 163207; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set from TestServer. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show TestServer?
These Rust Metrics lists carry TestServer: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does TestServer sit in the rankings?
Ranking for TestServer: #13,034 on seven-day player hours, top – of all ranked servers.
What player count does TestServer carry?
TestServer is not responding; status offline, last seen 44 days 7 hours ago.
Server
What location is TestServer hosted in?
No region comes from TestServer. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 91.11.200.94:28015.
What Rust version is TestServer on?
Rust network protocol 2633 and build 163207 on Windows is the build TestServer runs. To get in, your game needs the same protocol; Steam applies the update.
Is TestServer up, and how often does it stay up?
TestServer reports offline. The last reading came 44 days 7 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Settings and map
How is TestServer configured, and what rules are in force?
Reading the name gives no gather rate for TestServer. The group cap is 8 players, which is the default in the game. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on TestServer?
The game generates a procedural map for TestServer.
How to join
What do you do to join TestServer?
To join: start Rust, press F1 and type client.connect 91.11.200.94:28015. Or press Launch Rust here and Steam opens the game and connects you.