TES12835
TestTest3
Offline 119.201.237.49:28015 checked 44d 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 bestWipe 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.
-
01COMPlayers 636/675
-
02COMPlayers 485/525
-
03COMPlayers 59/250
-
04COMPlayers 36/250
-
05COMPlayers 138/200
-
06COMPlayers 255/300
Quick answers
From the figures on this page.
Filters
Which Rust Tracker filters and lists carry TestTest3?
Community servers, no tags — the Rust Tracker lists that include TestTest3. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on TestTest3?
These tags are published by TestTest3 for the game's server browser to read: gmrust (Game mode): Rust survival, standard mode; mp10 (Max players): Slots: 10; ts8 (Group limit): Default team size: 8; v2633 (Protocol): Your game must be on protocol 2633 to connect; cs163794 (Build): This server runs game build 163794; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): The region code is unset. The tags also hold the current player count, the queue and when the world was made; all appear at the top of this page.
Wipe Times
When does TestTest3 wipe?
The record holds too few of TestTest3's wipes to show its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. Its world went live 51 days 15 hours.
Location and Status
Is TestTest3 up, and how does its uptime hold?
Tracking shows TestTest3 offline as of now, last seen 44 days 2 hours ago. 0% uptime over the last 7 full days, with 0 of 168 hours up. Rust Tracker logged it first on 14 September 2026.
Which Rust build is TestTest3 running?
Confirmed for TestTest3: Rust network protocol 2633 and build 163794, Windows. Steam updates it for you; your game must share the protocol to join.
Where does TestTest3 sit?
No region is published by TestTest3. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 119.201.237.49:28015.
Player Count
Is TestTest3 busy?
Last seen 44 days 2 hours ago; TestTest3 is offline at present.
How does TestTest3 compare in the rankings?
Seven-day player hours put TestTest3 at #12,835, within the top – of all ranked servers.
Settings
Which settings and rules are confirmed on TestTest3?
The name of TestTest3 carries no gather rate. 8 players per group is the game's default, and the cap holds. It runs survival, gather, build and raid: the standard game. Fighting and raiding between players are on. A community server: the server browser lists it under Community. VAC is on, Valve's anti-cheat.
Which map is loaded on TestTest3?
Generated by the game: the procedural map on TestTest3.
How to Join
How do you get onto TestTest3?
To connect: start Rust, press F1, enter client.connect 119.201.237.49:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8
Game
gmrust
mp10
ts8
v2633
cs163794
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.