TestTest3
Offline 119.201.237.49:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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- 513/575
- 315/400
- 42/250
- 35/250
- 91/150
- 111/200
Quick answers
from the figures on this pageWipe timing
How often does TestTest3 wipe, and when?
The rhythm of TestTest3's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 51 days 17 hours ago.
Tags
How should you read the tags on TestTest3?
These are the tags TestTest3 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Game build reading: 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show TestTest3?
Rust Metrics lists featuring TestTest3: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Population
Where does TestTest3 sit in the rankings?
Player hours over seven days put TestTest3 at #12,835, in the top – of all ranked servers.
What is the population on TestTest3?
Reading for TestTest3: offline at this moment; last seen 44 days 5 hours ago.
Operator and location
Where does TestTest3 sit?
No region comes from TestTest3. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 119.201.237.49:28015.
What Rust version is TestTest3 on?
Rust network protocol 2633 and build 163794 on Windows is the build TestTest3 runs. To get in, your game needs the same protocol; Steam applies the update.
Is TestTest3 up, and how often does it stay up?
TestTest3 reports offline. The last reading came 44 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 14 September 2026.
Rules and settings
What settings and rules apply on TestTest3?
Check: gather rate. The name TestTest3 does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Combat and raiding against other players are on. The server browser lists it under Community. VAC is on. That is Valve's anti-cheat.
What map is TestTest3 on?
The game generates a procedural map for TestTest3.
How to join
How can you get onto TestTest3?
Check: join. Open Rust, press F1, then enter client.connect 119.201.237.49:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.