Test Server
Offline 176.241.20.49:28088 checked 43d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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- 504/575
- 324/400
- 40/250
- 33/250
- 99/150
- 120/200
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test Server follow?
To tell the rhythm of Test Server, too few of its wipes 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 53 days 5 hours ago.
Tags
How should you read the tags on Test Server?
These are the tags Test Server 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): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163207 (Build): Game build reading: 163207; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does Test Server appear in Rust Metrics lists and filters?
On Rust Metrics, Test Server sits in these lists: 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 Test Server sit in the rankings?
Ranking for Test Server: #15,404 on seven-day player hours, top – of all ranked servers.
How full does Test Server get?
Status for Test Server: offline. Last seen 43 days 3 hours ago.
Server
What location is Test Server hosted in?
No region tag on Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 176.241.20.49:28088.
What Rust version is Test Server on?
Rust network protocol 2633 and build 163207 on Linux is the build Test Server runs. To get in, your game needs the same protocol; Steam applies the update.
Is Test Server up, and how often does it stay up?
Test Server reports offline. The last reading came 43 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 13 September 2026.
Rules and settings
What rules does Test Server enforce, and what are its settings?
Reading the name gives no gather rate for Test Server. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
Join
What do you do to join Test Server?
To join: start Rust, press F1 and type client.connect 176.241.20.49:28088. Or press Launch Rust here and Steam opens the game and connects you.