Server profile
TEST
Offline, with 1 of 10 players on; ranked #13,012 of every public Rust server, the top 59%. It last wiped 11d ago.
Offline 80.237.93.157:28015 checked 9d ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 59% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
No rhythm it keeps.
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 2, 22 hours in.
The record
Wipes
Every wipe we saw, newest first.
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 13:24 UTC11d ago | 2 | – | running | 1 |
| Sat 10 Oct, 17:49 UTC17d ago | 4 | held half | 5.8 days | 2 |
| Thu 8 Oct, 10:15 UTC19d ago | 3 | held half | 2.3 days | 0 |
| Wed 7 Oct, 16:54 UTC20d ago | 2 | – | 0.7 days | 0 |
| Sun 27 Sep, 21:55 UTC30d ago | 2 | halved by day 4 | 9.8 days | 0 |
| Sat 26 Sep, 16:38 UTC31d ago | 6 | – | 1.2 days | 3 |
| Fri 25 Sep, 12:22 UTC32d ago | 6 | – | 1.2 days | 0 |
| Wed 23 Sep, 18:18 UTC34d ago | 2 | – | 1.8 days | 0 |
| Sat 19 Sep, 06:52 UTC38d ago | 5 | halved by day 2 | 4.5 days | 1 |
| Fri 18 Sep, 16:51 UTC39d ago | 5 | – | 0.6 days | 1 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe cycle
What should you expect on wipe day at TEST?
At their busiest, its recent wipes drew 3 players on average. 22 hours into the latest wipe, the crowd on the server reached its peak. The crowd stayed above half that peak until the next wipe in 67% of its recent wipes. In the other cases, it dropped below half by day 4.
When does TEST wipe, and how often?
No next wipe can be predicted for TEST, which wipes at irregular times. Next on Thursday 5 November at 19:00 UTC, every Rust server, this one included, takes the monthly force wipe. 11 days 17 hours have passed since its current world was created.
About the server
On what version does TEST currently run?
The Rust build is network protocol 2634 and build 166652, running on Windows, for TEST. The same protocol is required to join, and Steam takes care of updating it.
What does uptime look like for TEST, and is it online?
The last sighting of TEST was 9 days 14 hours ago, and it is offline at present. The last 7 full days gave 0 of 168 hours up, or 0% of the time. The first record Rust Insights has of it is 18 September 2026.
In which location does TEST sit?
There is no region published for TEST. Rust Insights reports the location a server declares, not the physical place of the machine. Connect through 80.237.93.157:28015.
Tags
What is meant by each tag on TEST?
When the game's server browser reads TEST, it finds these tags: gmrust (Game mode): The game mode is standard Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): 8 to a team, which is the default the game ships with; v2634 (Protocol): Matching versions are required, and the protocol is 2634; cs166652 (Build): Build 166652 is what it runs; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): No region code is set; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Plugins or settings alter the game, so it is filed under Modded. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
Which Rust Insights filters and lists feature TEST?
The Rust Insights lists that carry TEST are Modded Rust servers, explained. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Population history
How many players are on TEST right now, and how does that number move?
The last time TEST was seen online was 9 days 14 hours ago, and it is offline now.
In the ranking of Rust servers, where does TEST place?
The player-hours ranking for the last seven days puts TEST at #13,012, among the top 59% of all ranked servers.
Rules and settings
What are the settings and rules for TEST?
Nothing about gather rate is given in the name of TEST. No group limit is set, so the game's default of 8 players applies. survival is the game mode, the standard game: gather, build, raid. Players may raid and fight one another. The server browser lists it under Modded: plugins or settings alter the game. Plugins: Oxide run here. Anti-cheat: VAC, from Valve, is off.
Which map is live on TEST?
A procedural map, generated by the game, is what TEST runs.
Connecting
How do you connect to TEST?
To connect, start Rust and enter client.connect 80.237.93.157:28015 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.