Test
Offline 94.50.188.19:28015 checked 25d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Sunday 1 November, 04:11 UTC, in 2d 8h. Biweekly: 14 days after its last 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- 190/2000
- 322/2000
- 66/200
- 34/200
- 67/100
- 35/250
Quick answers
from the figures on this pageWipe timing
What wipe timing does Test follow?
The estimate for Test's next wipe comes from biweekly: 14 days after its last wipe. Due on Sunday 1 November at 04:11 UTC is its next wipe. The world in play was created 25 days 15 hours ago. The tags carry an every-two-weeks wipe schedule.
Tag meanings
How should you read the tags on Test?
Tags published by Test, read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp200 (Max players): Slots: 200; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^b (Biweekly): Check: wipe cycle. Every two weeks; ^p (PvE): No fighting between players: the world itself is the hazard; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. 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: Modded Rust servers, checked live and Rust PvE servers. Reading: server list filters. It comes up under Type: Modded; Game mode: PvE; Server tag: Biweekly ^b, PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Population
What position does Test hold among Rust servers?
Player hours over seven days put Test at #15,996, in the top 71% of all ranked servers.
What player count does Test carry?
Reading for Test: offline at this moment; last seen 25 days 10 hours ago.
Operator and location
What location is Test hosted in?
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 94.50.188.19:28015.
What Rust version is Test on?
Reading: Test, Rust network protocol 2634 and build 166652, Windows. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on Test, and is it online?
Reading: offline. Test last answered 25 days 10 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 4 October 2026, recorded by Rust Metrics.
Rules and settings
What rules does Test enforce, and what are its settings?
Check: gather rate. The name Test does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is pve. Note the following: fighting between players is off. Listing: Modded. Plugins or settings change the game. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.
Which map is live on Test?
The game generates a procedural map for Test.
Connection
How do you connect to Test?
Check: join. Open Rust, press F1, then enter client.connect 94.50.188.19:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.