Testing1
93.137.36.64: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 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
Quick answers
Rules and settings
What is the setup on Testing1 when it comes to rules and settings?
There is no gather rate in the name Testing1. That is the game's default: groups of up to 8 players. survival is the game mode, gather, build and raid: the standard game. You can fight and raid other players here. Community is its section in the server browser. Anti-cheat is on: VAC, from Valve.
What is the map on Testing1?
The game generates the procedural map Testing1 runs.
Server population
How full is Testing1?
The server Testing1 is currently offline; it was last seen 19 days 22 hours ago.
Where does Testing1 sit in the rankings?
In the top 60% of ranked servers, Testing1 holds #13,515 for player hours over the last seven days.
Lists and tags
How should you read the tags on Testing1?
For the game's server browser, Testing1 publishes these tags: gmrust (Game mode): Survival in the standard Rust mode; mp2 (Max players): It holds 2 players; ts8 (Group limit): This uses the standard team limit of 8; v2633 (Protocol): Protocol 2633—only players on that version can get in; cs165217 (Build): It runs build 165217; ptrak (Networking): Standard RakNet networking is in use here; $r? (Region code): No region code is set. At the top of this page you see its players now, its queue and the time its world was made, which are in the tags too.
Where does Testing1 appear in Rust Zerg Life lists?
The Rust Zerg Life lists that include Testing1 are Rust community servers for clans. Under these filters it shows on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
About the server
What is the uptime and reliability of Testing1?
Currently offline, Testing1 was last seen 19 days 22 hours ago. Over the last 7 full days, uptime was 0%: 0 hours up out of 168. Rust Zerg Life has been tracking it since 24 September 2026.
Which Rust build does Testing1 use?
Rust network protocol 2633 and build 165217 is what Testing1 runs, on Windows. Joining requires your game to be on the same protocol, which Steam updates automatically.
Where can you find Testing1?
No region is published by Testing1. Rust Zerg Life displays the location a server claims, not where the machine actually stands. You can reach it at 93.137.36.64:28015.
Wipe cycle
When does Testing1 wipe?
So few of Testing1's wipes are recorded that its rhythm cannot be told yet. Next on Thursday 5 November at 19:00 UTC: the monthly force wipe that every Rust server gets. 20 days 1 hours ago is when its present world was created.
Join the server
How can I connect to Testing1?
Join by entering client.connect 93.137.36.64:28015 in the console (press F1 first). Or use Launch Rust on this page, which opens Rust through Steam and connects you.
Server tags
Published as mp2,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp2
ts8
v2633
cs165217
ptrak
$r?
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.