TST13745
test
Offline 114.33.108.48:28015 checked 22d 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 bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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 566/625
-
02COMPlayers 418/450
-
03COMPlayers 161/250
-
04COMPlayers 51/100
-
05COMPlayers 175/250
-
06COMPlayers 348/225
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry test?
On Rust Tracker, test sits in these lists: Community servers, no tags. 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 test?
These tags are published by test for the game's server browser to read: gmrust (Game mode): Survival as standard Rust plays; mp10 (Max players): Slots: 10; ts8 (Group limit): Team limit is 8, the game default; v2634 (Protocol): To join, your game must match protocol 2634; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): Region code: not set. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Wipe Schedule
On what schedule does test wipe?
test's rhythm cannot be told yet: too few wipes on record. Track the force wipe: Thursday 5 November at 19:00 UTC. Every Rust server resets on that date. 22 days 4 hours since this world was made.
Location and Status
What is the uptime on test, and is it online?
Offline now, test was last seen 22 days 3 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. Rust Tracker logged it first on 7 October 2026.
Which Rust version is confirmed on test?
Confirmed for test: Rust network protocol 2634 and build 166652, Windows. The same protocol is required to join, and Steam updates it for you.
Where does test sit?
Region: none published by test. Where a server says it is, Rust Tracker shows; where the machine stands, it does not look up. Connect on 114.33.108.48:28015.
Player Count
What is the player count on test?
Last seen 22 days 3 hours ago; test is offline at present.
How does test compare in the rankings?
Seven-day player hours put test at #13,745, within the top 62% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on test?
The name of test carries no gather rate. The game's default applies: groups can have up to 8 players. 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 confirmed for test?
Generated by the game: the procedural map on test.
Connect
Which steps join test?
Open the console in Rust with F1 after starting the game, then type client.connect 114.33.108.48:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
mp10
ts8
v2634
cs166652
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.