TestServer
Offline 94.134.192.41:28015 checked 23d 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 bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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- 588/675
- 363/525
- 49/250
- 40/250
- 130/200
- 140/300
Quick answers
from the figures on this pageWipe schedule
How often does TestServer wipe, and when?
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. 26 days 13 hours ago the current world was made.
Tags
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): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): The server runs game build 166652; 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. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does TestServer sit in the rankings?
Player hours over seven days put TestServer at #13,792, in the top 61% of all ranked servers.
How full does TestServer get?
TestServer is not responding; status offline, last seen 23 days 3 hours ago.
Server details
Which location does TestServer run from?
No region tag on TestServer. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 94.134.192.41:28015.
What Rust version is TestServer on?
Reading: TestServer, Rust network protocol 2634 and build 166652, 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 23 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 5 October 2026, recorded by Rust Metrics.
Settings and map
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. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. 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.
How to join
What do you do to join TestServer?
Check: join. Open Rust, press F1, then enter client.connect 94.134.192.41:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.