Test
Offline 93.94.176.134:28015 checked 28d ago
Server instruments
no direct query in 48 hoursPlayers now
50% 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 60% 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- 280/300
- 230/250
- 20/250
- 21/250
- 26/100
- 107/200
Quick answers
from the figures on this pageWipe schedule
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 it runs now was made 48 days ago.
Tag meanings
How should you read the tags on Test?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp2 (Max players): The server holds 2 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163493 (Build): Game build reading: 163493; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set from Test. 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?
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.
Occupancy
What position does Test hold among Rust servers?
Ranking for Test: #14,436 on seven-day player hours, top 60% of all ranked servers.
What player count does Test carry?
Status for Test: offline. Last seen 28 days 20 hours ago.
Operator and location
Which location does Test run from?
No region tag on Test. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 93.94.176.134:28015.
What Rust version is Test on?
Rust network protocol 2633 and build 163493 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 28 days 20 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 30 September 2026.
Settings and map
What rules does Test enforce, and what are its settings?
No gather rate appears in the name: Test. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.
Join
How can you get onto Test?
Check: join. Open Rust, press F1, then enter client.connect 93.94.176.134:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.