TestServer
Offline 94.134.192.240:28015 checked 39d 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- 162/250
- 148/200
- 15/250
- 15/250
- 19/100
- 69/200
Quick answers
from the figures on this pageWipe timing
When does TestServer wipe?
The rhythm of TestServer's wipes cannot be told yet: too few 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 54 days 16 hours ago.
Tag meanings
How should you read the tags on TestServer?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): The server runs game build 164530; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from TestServer. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
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.
Player count
What position does TestServer hold among Rust servers?
Player hours over seven days put TestServer at #14,395, in the top – of all ranked servers.
How full does TestServer get?
TestServer is not responding; status offline, last seen 39 days 19 hours ago.
Operator and location
What location is TestServer hosted in?
No region tag on TestServer. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 94.134.192.240:28015.
What Rust version is TestServer on?
Reading: TestServer, Rust network protocol 2633 and build 164530, Windows. Matching protocol is required to join. Let Steam update your game.
Is TestServer up, and how often does it stay up?
Reading: offline. TestServer last answered 39 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 19 September 2026, recorded by Rust Metrics.
Settings and map
What rules does TestServer enforce, and what are its settings?
Reading the name gives no gather rate for TestServer. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is TestServer on?
The game generates a procedural map for TestServer.
Join
How can you get onto TestServer?
Press F1 in Rust and enter client.connect 94.134.192.240:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.