DWG RG-S13515Server sheetchecked 34d ago
Testing1
Offline 93.137.36.64:28015 checked 34d 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
Top 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
| 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
Recorded details
What uptime is recorded for Testing1, and is it up?
The current state of Testing1 is offline, with the last sighting 34 days 21 hours ago. 0 of 168 hours up over the last 7 full days, which is 0% of the time. First seen by Rust Graphs on 24 September 2026.
What location is recorded for Testing1?
No region is published by Testing1. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. You will find it at 93.137.36.64:28015.
On which Rust version is Testing1 running?
The platform is Windows and the version is Rust network protocol 2633 and build 165217 on Testing1. Steam updates your game, which must be on the same protocol for you to join.
Player data
What player count is recorded on Testing1?
The latest refresh records Testing1 as offline, last seen 34 days 21 hours ago.
In the rankings, which position does Testing1 hold?
Within the top 60% of all ranked servers: Testing1 at #13,515 for player hours, seven days recorded.
Wipe data
What wipe schedule has been recorded for Testing1?
Testing1's rhythm cannot be told yet: too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The current world has been in use since 35 days ago.
Map and rules
Which settings does Testing1 run, and what rules?
The name of Testing1 records no gather rate. The group limit is 8 players, the game's default. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Community is its tab in the server browser. VAC is on: that is Valve's anti-cheat.
On which map is Testing1 played?
Testing1 runs a procedural map, which the game generates.
Tags
On Rust Graphs, which lists and filters contain Testing1?
The Rust Graphs lists that carry Testing1 are: Rust community servers, plotted. It is returned by these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
On Testing1, what is meant by each tag?
The game's server browser reads these tags from Testing1: gmrust (Game mode): Survival in standard Rust style; mp2 (Max players): 2 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2633 (Protocol): To join, your game must be on protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.
Joining the server
How is Testing1 joined?
In Rust, press F1 and type client.connect 93.137.36.64:28015 in the console. Launch Rust on this page also works: Rust opens 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.