TEST
Offline 46.42.23.218:28015 checked 37d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 58% 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- 636/675
- 485/525
- 59/250
- 36/250
- 138/200
- 255/300
Quick answers
from the figures on this pageWipe timing
When does TEST wipe?
The rhythm of TEST's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 37 days 4 hours ago.
Tags
How should you read the tags on TEST?
These are the tags TEST publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show TEST?
Rust Metrics lists featuring TEST: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does TEST sit in the rankings?
Player hours over seven days put TEST at #13,227, in the top 58% of all ranked servers.
How full does TEST get?
Reading for TEST: offline at this moment; last seen 37 days 2 hours ago.
Server details
What location is TEST hosted in?
No region tag on TEST. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 46.42.23.218:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 164530 on Windows is the build TEST runs. Check: protocol. To join, your game must match; Steam handles the update.
Is TEST up, and how often does it stay up?
TEST reports offline. The last reading came 37 days 2 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 21 September 2026, recorded by Rust Metrics.
Rules and settings
What rules does TEST enforce, and what are its settings?
No gather rate appears in the name: TEST. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.
Which map is live on TEST?
Procedural map on TEST, made by the game's generator.
Connection
How do you connect to TEST?
To join: start Rust, press F1 and type client.connect 46.42.23.218:28015. Or press Launch Rust here and Steam opens the game and connects you.