TST14543
test
Offline 83.23.140.41:28015 checked 29d 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 61% 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 725/825
-
02COMPlayers 52/250
-
03COMPlayers 106/250
-
04COMPlayers 415/500
-
05COMPlayers 226/300
-
06COMPlayers 186/300
Quick answers
From the figures on this page.
Filters
Where does test appear in Rust Tracker lists and filters?
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.
What do the tags mean that test is listed under?
The game's server browser reads these tags from test: gmrust (Game mode): Standard survival mode for Rust; mp2 (Max players): Slots: 2; ts8 (Group limit): Team limit is 8, the game default; v2633 (Protocol): Join only if your game is on protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet is the network layer — the game's standard; $r? (Region code): The region code is unset. 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 30 days 7 hours.
Server Details
How reliable is test, and is it online now?
Tracking shows test offline as of now, last seen 29 days 7 hours ago. 0 of 168 hours up over the last 7 full days: 0% uptime. The first sighting by Rust Tracker was 28 September 2026.
Which Rust version is confirmed on test?
Rust network protocol 2633 and build 165217 on Windows is what test runs. The same protocol is required to join, and Steam updates it for you.
What location is test hosted in?
Nothing on region from test; none is published. The location shown by Rust Tracker is the server's own claim; no lookup of the machine's position is made. You connect at 83.23.140.41:28015.
Player Count
Is test busy?
Last seen 29 days 7 hours ago; test is offline at present.
How does test compare in the rankings?
Seven-day player hours put test at #14,543, within the top 61% of all ranked servers.
Map and Rules
Which settings and rules are confirmed on test?
Nothing in test's name states a gather rate. Up to 8 players per group, the game's default. It runs survival, 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. VAC is on, Valve's anti-cheat.
Which map is confirmed for test?
A procedural map runs on test, generated by the game.
Connect
How do you get onto test?
To connect: start Rust, press F1, enter client.connect 83.23.140.41:28015 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 mp2,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp2
ts8
v2633
cs165217
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.