Test
Offline 94.50.188.19:28015 checked 14d ago
Players
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 13d 18h. 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
- 138/ 2000
- 274/ 2000
- 48/ 200
- 53/ 250
- 122/ 200
- 29/ 200
Quick answers
Tags and listings
Where does Test appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry Test are: Modded Rust servers and Go deep on PvE servers. The server list shows it 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.
How should you read the tags on Test?
Test's game browser tags read: gmvanilla (Game mode): It's vanilla survival; mp200 (Max players): The slot count is 200; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs166652 (Build): This server runs build 166652; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): No region is set; ^b (Biweekly): The wipe cycle is two weeks; ^p (PvE): Other players aren't a threat; the world is; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
What's the location of Test?
No region comes from Test. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 94.50.188.19:28015.
What's the uptime like for Test?
Right now Test is offline, having last been seen 14 days ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 4 October 2026.
What Rust version is Test on?
The version on Test is Rust network protocol 2634 and build 166652, on Windows. The protocol must match to join; Steam will update your game.
Wipe schedule
When does Test wipe?
An estimate from biweekly: 14 days after its last wipe gives Test's next wipe. Expect the next wipe on Sunday 1 November at 04:11 UTC. This world has been running since 14 days 5 hours ago. The tags show wipes scheduled every two weeks.
Rules and settings
Which rules and settings is Test running?
Its name does not state a gather rate for Test. 8 players is the group cap, the game's default. It runs pve, no fighting other players. In the server browser it sits under Modded, where plugins or settings change the game. Plugins in use: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is active on Test?
A procedural map, generated by the game, is in play on Test.
Player stats
What's the population like on Test?
Test was last seen 14 days ago and is offline as you read this.
What position does Test hold in the server rankings?
Over the last seven days, Test is #15,996 by player hours, among the top 71% of all ranked servers.
Join info
How do you get into Test?
Open Rust and press F1, then type client.connect 94.50.188.19:28015. Alternatively, click Launch Rust on this page to join via Steam.