TST13273
TEST
Offline 195.78.100.186:28015 checked 40d 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 445/500
-
02COMPlayers 273/300
-
03COMPlayers 40/250
-
04COMPlayers 34/250
-
05COMPlayers 82/100
-
06COMPlayers 103/200
Quick answers
From the figures on this page.
Tags
Which lists and filters on Rust Tracker show TEST?
These Rust Tracker lists carry TEST: 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): Rust survival, standard mode; mp10 (Max players): Capacity: 10 slots; ts8 (Group limit): Team limit is 8, the game default; v2633 (Protocol): Join only if your game is on protocol 2633; cs164530 (Build): The game build is 164530; 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 Schedule
When does TEST wipe?
Too few wipes on record for TEST to show its rhythm. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. This world has been running 40 days 7 hours.
Location and Status
What is the uptime on TEST, and is it online?
Offline: TEST confirmed offline, last seen 40 days 4 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. Rust Tracker logged it first on 18 September 2026.
What Rust version is TEST on?
Rust network protocol 2633 and build 164530 on Windows is what TEST runs. The same protocol is required to join, and Steam updates it for you.
Which location is TEST in?
No region is published by TEST. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 195.78.100.186:28015.
Population
What is the player count on TEST?
Last seen 40 days 4 hours ago; TEST is offline at present.
Where does TEST sit in the server rankings?
Top – of all ranked servers, and #13,273 on seven-day player hours: TEST.
Map and Rules
Which settings and rules are confirmed on TEST?
No gather rate appears in TEST's name. The game's default applies: groups can have up to 8 players. survival is the game mode, 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.
What map is TEST on?
Procedural map on TEST, made by the game.
How to Join
What is the way to join TEST?
Open the console in Rust with F1 after starting the game, then type client.connect 195.78.100.186:28015. Alternatively, Launch Rust here opens Rust via Steam and connects you.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2633,gmrust,cs164530,ts8
Game
gmrust
mp10
ts8
v2633
cs164530
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.