TST9408=
Test Server
Online 88.198.7.190:28115 checked 23m 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, measured since 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 42% of all ranked servers, and #178 of the solo servers (top 80%). Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 22 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 23 Oct, 22:02 UTC6d ago | 2 | – | running | 0 |
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.
-
01MODPlayers 52/100
-
02MODPlayers 24/100
-
03MODPlayers 1/100
-
04MODPlayers 7/200
-
05MODPlayers 1/400
-
06MODPlayers 2/400
Quick answers
From the figures on this page.
Tags
Where does Test Server appear in Rust Tracker lists and filters?
On Rust Tracker, Test Server sits in these lists: Modded servers, tracked live and Solo Rust servers, tracked live. These filters surface it on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Carbon ^y; Group limit: Solo; Last wipe: In the last week.
How should you read the tags on Test Server?
These tags are published by Test Server for the game's server browser to read: gmrust (Game mode): Standard survival mode for Rust; mp10 (Max players): 10 slots on this server; ts1 (Group limit): Team limit: 1; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): Region code: not set; ^v (Vanilla): No changed rates, kits or rules — the game as Facepunch ships it; ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; ^y (Carbon): Carbon is installed — a plugin framework. Current players, queue length and world creation time sit in the tags as well, shown at the top of this page.
Who is behind Test Server?
The p-o-t.net hostname on Test Server also appears on 1 other server we track, which points to one operator behind them.
Wipe Times
What should you expect on Test Server when wipe day lands?
At their busiest, recent wipes averaged 2 players. The peak on the latest wipe came 22 hours after it.
Which wipe times are confirmed for Test Server?
Test Server'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. Its world went live 6 days 2 hours.
Location and Status
Is Test Server up, and how does its uptime hold?
Right now Test Server is online. About 8 hours ago it restarted last, based on reported uptime. 103 of 168 hours up over the last 7 full days: 61% uptime. First contact for Rust Tracker: 18 September 2026.
Which Rust build is Test Server running?
Confirmed for Test Server: Rust network protocol 2635 and build 168909, Linux. Steam updates it for you; your game must share the protocol to join.
What is performance like on Test Server?
Average server fps over the last 48 hours: 40, with a low of 40. Maximum entities carried: 61,929, from buildings and deployables to everything else. Memory peaked at 3,881 MB. Players feel lag when fps drops and the entity count climbs.
Which location is Test Server in?
Region: none published by Test Server. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 88.198.7.190:28115.
Player Count
Is Test Server busy?
Slots 10; players on board 0: that is Test Server now. Seven-day average 0 players; peak 2.
What rank does Test Server carry among Rust servers?
On player hours over seven days, Test Server ranks #9,408, inside the top 42% of all ranked servers. Position #178 among solo servers.
Map and Rules
Which settings and rules are confirmed on Test Server?
The name of Test Server carries no gather rate. No teams. Solo only. It runs survival, gather, build, raid, as the game intends. Raiding and PvP are permitted between players. The server browser lists it under Modded, where plugins or settings change the game. Plugins on it: Carbon. Its label is vanilla: no changed rates, kits or rules — the game as Facepunch ships it. On: VAC, Valve's anti-cheat.
Which map is loaded on Test Server?
A procedural map of size 4,250 runs on Test Server, generated by the game from seed 1234. Look at it on RustMaps from this page: equal size and seed return the same map. Read the name of its map: Custom Map.
Connect
What is the way to join Test Server?
To connect: start Rust, press F1, enter client.connect 88.198.7.190:28115 in the console. Or use Launch Rust on this page to open Rust through Steam and join. The server's website: https://www.lagcity.eu/.
Server tags
What each one means.
Published as mp10,ptrak,$r?,v2635,^z,^y,^v,gmrust,cs168909,ts1
Game
gmrust
mp10
ts1
v2635
cs168909
ptrak
$r?
Difficulty
^v
Mods and access
^z
^y
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.