TST15404
Test Server
Offline 176.241.20.49:28088 checked 42d 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 430/525
-
02COMPlayers 25/250
-
03COMPlayers 45/250
-
04COMPlayers 195/275
-
05COMPlayers 76/200
-
06COMPlayers 89/150
Quick answers
From the figures on this page.
Filters
Which Rust Tracker filters and lists carry Test Server?
These Rust Tracker lists carry Test Server: Community servers, no tags. These filters surface it on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on Test Server?
Listed for the server browser to read, Test Server publishes these tags: gmrust (Game mode): Survival as standard Rust plays; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Team limit is 8, the game default; v2633 (Protocol): To join, your game must match protocol 2633; cs163207 (Build): Build: 163207; ptrak (Networking): Network layer: RakNet, the game's standard; $r? (Region code): No region code is set. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Times
Which wipe times are confirmed for Test Server?
The record holds too few of Test Server's wipes to show its rhythm. Next monthly force wipe: Thursday 5 November at 19:00 UTC. Every Rust server goes with it. 52 days 7 hours since this world was made.
Location and Status
What is the uptime on Test Server, and is it online?
Tracking shows Test Server offline as of now, last seen 42 days 6 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. First contact for Rust Tracker: 13 September 2026.
What Rust version is Test Server on?
Rust network protocol 2633 and build 163207 on Linux is what Test Server runs. To join, your game must be on the same protocol; Steam handles the update.
Which location is Test Server in?
Region: none published by Test Server. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. You connect at 176.241.20.49:28088.
Population
Is Test Server busy?
Last seen 42 days 6 hours ago; Test Server is offline at present.
How does Test Server compare in the rankings?
On player hours over seven days, Test Server ranks #15,404, inside the top – of all ranked servers.
Map and Rules
Which settings and rules are confirmed on Test Server?
No gather rate appears in Test Server's name. 8 players per group is the game's default, and the cap holds. survival is the game mode, gather, build, raid, as the game intends. Fighting and raiding between players are on. The server browser lists it under Community, as a community server. On: VAC, Valve's anti-cheat.
How to Join
Which steps join Test Server?
To connect: start Rust, press F1, enter client.connect 176.241.20.49:28088 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,cs163207,ts8
Game
gmrust
mp10
ts8
v2633
cs163207
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.