TEST
Offline 98.97.140.132:28015 checked 29d ago
Server instruments
no direct query in 48 hoursPlayers now
14% 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 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- 538/575
- 430/475
- 167/250
- 57/100
- 221/250
- 304/350
Quick answers
from the figures on this pageWipe timing
What wipe timing does TEST follow?
To tell the rhythm of TEST, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 34 days 14 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): Survival, as standard Rust plays it; mp7 (Max players): The server holds 7 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs164530 (Build): The server runs game build 164530; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does TEST appear in Rust Metrics lists and filters?
On Rust Metrics, TEST sits in these lists: 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
What position does TEST hold among Rust servers?
Ranking for TEST: #14,467 on seven-day player hours, top 61% of all ranked servers.
What player count does TEST carry?
Reading for TEST: offline at this moment; last seen 29 days 8 hours ago.
Operator and location
Which location does TEST run from?
No region tag on TEST. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 98.97.140.132:28015.
What Rust version is TEST on?
Rust network protocol 2633 and build 164530 on Windows is the build TEST runs. Matching protocol is required to join. Let Steam update your game.
Is TEST up, and how often does it stay up?
Reading: offline. TEST last answered 29 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 27 September 2026, recorded by Rust Metrics.
Rules and settings
What rules does TEST enforce, and what are its settings?
Reading the name gives no gather rate for TEST. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Under Community in the server browser you will find it. Anti-cheat reading: VAC on, Valve's system.
What map is TEST on?
The game generates a procedural map for TEST.
Join
What do you do to join TEST?
Press F1 in Rust and enter client.connect 98.97.140.132:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.