Test
Offline 153.66.149.134:28015 checked 31d ago
Server instruments
no direct query in 48 hoursPlayers now
100% 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 65% 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- 261/275
- 20/250
- 17/250
- 162/200
- 67/200
- 39/100
Quick answers
from the figures on this pageReset cycle
What wipe timing does Test follow?
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 31 days 22 hours ago.
Lists and filters
Which tags does Test carry, and what do they mean?
Tags published by Test, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Test appear in Rust Metrics lists and filters?
On Rust Metrics, Test sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
What position does Test hold among Rust servers?
Ranking for Test: #15,068 on seven-day player hours, top 65% of all ranked servers.
How full does Test get?
Test is not responding; status offline, last seen 31 days 21 hours ago.
Operator and location
Where does Test sit?
No region tag on Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 153.66.149.134:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2633 and build 165217, Windows. Matching protocol is required to join. Let Steam update your game.
Is Test up, and how often does it stay up?
Check: connection. Test is offline at this moment. Last contact was 31 days 21 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 26 September 2026.
Settings and map
What settings and rules apply on Test?
Reading the name gives no gather rate for Test. The group cap is 8 players, which is the default in the game. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Listing: Community server. VAC is on. That is Valve's anti-cheat.
Which map is live on Test?
Procedural map on Test, made by the game's generator.
Join
What do you do to join Test?
Press F1 in Rust and enter client.connect 153.66.149.134:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.