test
Offline 83.23.140.41:28015 checked 19d 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 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
- 320/ 400
- 523/ 600
- 199/ 225
- 266/ 325
- 276/ 350
- 337/ 425
Quick answers
Tags and search
Where does test appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include test: 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.
How should you read the tags on test?
gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): There are 2 slots on this server; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs165217 (Build): This server runs build 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code — that is the tag list test puts out for the game's server browser. 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 info
What location is test in?
No region comes from test. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. The endpoint is 83.23.140.41:28015.
What's the uptime like for test?
The server test is not reachable at the moment; the last sighting was 19 days 9 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 28 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for test?
Rust network protocol 2633 and build 165217 is what test runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
What schedule does test follow for wipes?
The wipes recorded for test are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. The world you are on now was created 20 days 9 hours.
Map and rules
Which rules and settings is test running?
The name of test contains no gather rate. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. Community is where the server browser puts it, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is active on test?
A procedural map, generated by the game, is in play on test.
Population
What's the population like on test?
The last sighting of test was 19 days 9 hours ago; it is offline right now.
What position does test hold in the server rankings?
For player hours in the last seven days, test ranks #14,543, within the top 61% of ranked servers.
Join info
What's the process to join test?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 83.23.140.41:28015.