testserver
Offline 37.37.139.160:28015 checked 5d 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 50% 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
Quick answers
Tags and listings
Where does testserver appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include testserver: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on testserver?
The server browser shows these tags for testserver: gmrust (Game mode): Survival, as standard Rust does it; mp10 (Max players): It holds 10 players; ts5 (Group limit): You can have up to 5 in a team; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs167058 (Build): The build number is 167058; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): It has no region code; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. 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.
About the server
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. The endpoint is 37.37.139.160:28015.
Is testserver up, and how often does it stay online?
The server testserver is not reachable at the moment; the last sighting was 5 days 21 hours ago. Over the past full 5 days it stayed up for 0 of 120 hours, or 0%. The first sighting by Rust Going Deep was on 12 October 2026.
What is the Rust version for testserver?
Rust network protocol 2634 and build 167058 is what testserver runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
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 10 days 21 hours ago.
Settings and map
What settings and rules have been applied to testserver?
No gather rate appears in the name of testserver. The group limit is 5 players. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. In the server browser it sits under Modded, where plugins or settings change the game. You will find Oxide plugins installed. VAC is on: Valve's anti-cheat is active.
Which map is active on testserver?
The map on testserver is procedural, made by the game.
Population
Is testserver busy?
The last sighting of testserver was 5 days 21 hours ago; it is offline right now. For the past week, players averaged 1 with a high of 1.
What's testserver's rank among Rust servers?
For player hours in the last seven days, testserver ranks #11,117, within the top 50% of ranked servers.
How to join
What's the process to join testserver?
Open Rust and press F1, then type client.connect 37.37.139.160:28015. Alternatively, click Launch Rust on this page to join via Steam.