test
Offline 85.130.130.191:28090 checked 17d 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 70% 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
- 17/ 100
- 303/ 400
- 186/ 225
- 120/ 100
- 388/ 1000
- 30/ 700
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. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on test?
gmrust (Game mode): Survival, as standard Rust does it; mp3 (Max players): It holds 3 players; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs165217 (Build): This server runs build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): Plugins run through Oxide (uMod); ^z (Modded): You'll see it in Modded, since plugins or settings modify the game — that is the tag list test puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What location is test in?
There is no published region for test. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 85.130.130.191:28090.
Is test up, and how often does it stay online?
The server test is not reachable at the moment; the last sighting was 17 days 10 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. The first sighting by Rust Going Deep was on 16 September 2026.
What Rust version is test on?
The version on test is Rust network protocol 2633 and build 165217, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe details
When does test wipe?
Too few wipes are on record for test to show its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. This world has been running since 41 days 14 hours ago.
Map and rules
Which rules and settings is test running?
The name of test contains no gather rate. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. You will find Oxide plugins installed. 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 count
Is test busy?
test was last seen 17 days 10 hours ago and is offline as you read this.
What's test's rank among Rust servers?
Over the last seven days, test is #16,685 by player hours, among the top 70% of all ranked servers.
Join info
How do you get into test?
Open Rust and press F1, then type client.connect 85.130.130.191:28090. Alternatively, click Launch Rust on this page to join via Steam.