TestTest3
Offline 211.199.53.75: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- 468/575
- 295/400
- 41/250
- 34/250
- 83/150
- 101/200
Quick answers
from the figures on this pageWipe schedule
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.
Tag meanings
Which tags does TestTest3 carry, and what do they mean?
Check: tags. The game's server browser reads 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): Your game must run protocol 2633 to get in; cs163794 (Build): Game build reading: 163794; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty from TestTest3. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does TestTest3 appear in Rust Metrics lists and filters?
Rust Metrics lists featuring TestTest3: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does TestTest3 sit in the rankings?
Player hours over seven days put TestTest3 at #12,998, in the top – of all ranked servers.
How full does TestTest3 get?
Status for TestTest3: offline. Last seen 44 days 21 hours ago.
Server details
What location is TestTest3 hosted in?
No region comes from TestTest3. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 211.199.53.75:28015.
What Rust version is TestTest3 on?
Reading: TestTest3, Rust network protocol 2633 and build 163794, Windows. Matching protocol is required to join. Let Steam update your game.
Is TestTest3 up, and how often does it stay up?
Check: connection. TestTest3 is offline at this moment. Last contact was 44 days 21 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Settings and map
What rules does TestTest3 enforce, and what are its settings?
Check: gather rate. The name TestTest3 does not state one. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
What map is TestTest3 on?
Procedural map on TestTest3, made by the game's generator.
Connection
How do you connect to TestTest3?
Press F1 in Rust and enter client.connect 211.199.53.75:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.