TestServer
Offline 94.134.193.191:28015 checked 43d 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- 513/525
- 418/450
- 52/250
- 55/250
- 60/100
- 167/200
Quick answers
from the figures on this pageReset cycle
When does TestServer wipe?
To tell the rhythm of TestServer, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 54 days 23 hours ago the current world was made.
Tags
How should you read the tags on TestServer?
These are the tags TestServer publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show TestServer?
On Rust Metrics, TestServer sits in these lists: 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.
Occupancy
Where does TestServer sit in the rankings?
Ranking for TestServer: #14,446 on seven-day player hours, top – of all ranked servers.
What is the population on TestServer?
Status for TestServer: offline. Last seen 43 days 21 hours ago.
Operator and location
Where does TestServer sit?
No region tag on TestServer. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 94.134.193.191:28015.
What Rust version is TestServer on?
Reading: TestServer, Rust network protocol 2633 and build 163794, Windows. Check: protocol. To join, your game must match; Steam handles the update.
What is the uptime on TestServer, and is it online?
Check: connection. TestServer is offline at this moment. Last contact was 43 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 15 September 2026.
Map and rules
What settings and rules apply on TestServer?
Reading the name gives no gather rate for TestServer. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
Which map is live on TestServer?
Check: map. Procedural, generated by the game, on TestServer.
How to join
What do you do to join TestServer?
Check: join. Open Rust, press F1, then enter client.connect 94.134.193.191:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.