TestServer
Offline 82.22.41.15:28015 checked 33d ago
Players
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
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 14 Sep, 14:54 UTC33d ago | 1 | – | 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
- 145/ 200
- 287/ 300
- 253/ 275
- 780/ 800
- 109/ 200
- 112/ 250
Quick answers
Tags and search
Where does TestServer appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include TestServer: Rust community servers, going deep. The server list shows it under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What's the meaning of the tags on TestServer?
TestServer's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): The slot count is 10; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs163794 (Build): The build number is 163794; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
What location is TestServer in?
TestServer does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 82.22.41.15:28015.
Is TestServer up, and how often does it stay online?
Right now TestServer is offline, having last been seen 33 days 10 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. Rust Going Deep has had it on record since 14 September 2026.
What Rust version is TestServer on?
On Windows, TestServer runs Rust network protocol 2633 and build 163794. The protocol must match to join; Steam will update your game.
Wipe schedule
What schedule does TestServer follow for wipes?
The wipes recorded for TestServer are too few to reveal its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 33 days 11 hours ago.
What happens on wipe day at TestServer?
Across its recent wipes, the average busiest point drew 1 players. On the latest wipe, 2 hours passed before the crowd peaked.
Map and rules
What settings are in place on TestServer?
The name of TestServer contains no gather rate. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Community is where the server browser puts it, as a community server. The server does not run Valve's anti-cheat, VAC.
Which map is active on TestServer?
A procedural map, generated by the game, is in play on TestServer.
Player count
What's the population like on TestServer?
The last sighting of TestServer was 33 days 10 hours ago; it is offline right now.
What position does TestServer hold in the server rankings?
For player hours in the last seven days, TestServer ranks #13,781, within the top – of ranked servers.
How to join
What's the way to join TestServer?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 82.22.41.15:28015.