Testing1
Offline 93.137.36.64:28015 checked 23d 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 60% 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
- 463/ 475
- 592/ 600
- 322/ 375
- 750/ 775
- 109/ 200
- 335/ 375
Quick answers
Tags and listings
Where does Testing1 appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Testing1: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
What's the meaning of the tags on Testing1?
gmrust (Game mode): Survival, as standard Rust does it; mp2 (Max players): It holds 2 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs165217 (Build): The build number is 165217; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set — that is the tag list Testing1 puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server details
Where can you find Testing1?
No region comes from Testing1. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 93.137.36.64:28015.
How reliable is Testing1?
Testing1 is down at the moment; it was last up 23 days 17 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 24 September 2026.
What Rust version is Testing1 on?
On Windows, Testing1 runs Rust network protocol 2633 and build 165217. The protocol must match to join; Steam will update your game.
Wipe details
How often does Testing1 wipe?
Too few wipes are on record for Testing1 to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 23 days 19 hours ago.
Map and rules
Which rules and settings is Testing1 running?
The name of Testing1 contains no gather rate. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. PvP and raiding are enabled. Community is where the server browser puts it, as a community server. The server runs Valve's anti-cheat, VAC.
What's the map on Testing1?
The map on Testing1 is procedural, made by the game.
Player stats
What's the population like on Testing1?
Right now Testing1 is offline, with its last appearance 23 days 17 hours ago.
What position does Testing1 hold in the server rankings?
Over the last seven days, Testing1 is #13,515 by player hours, among the top 60% of all ranked servers.
How to join
What's the way to join Testing1?
Open Rust and press F1, then type client.connect 93.137.36.64:28015. Alternatively, click Launch Rust on this page to join via Steam.