Test
Offline 1.170.170.24:28015 checked 7d 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 62% 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
- 1001/ 100
- 59/ 400
- 47/ 245
- 127/ 100
- 77/ 1000
- 8/ 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?
Test's game browser tags read: gmrust (Game mode): This is the standard Rust survival experience; mp5 (Max players): It holds 5 players; ts8 (Group limit): Teams cap at 8, which is the game default; v2634 (Protocol): The protocol is 2634; a different version won't get you in; cs166586 (Build): It's on build 166586; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): The region field is empty; ^o (Oxide): This server uses Oxide (uMod) for plugins; ^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.
About the server
Where can you find Test?
No region comes from Test. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 1.170.170.24:28015.
What's the uptime like for Test?
The server Test is not reachable at the moment; the last sighting was 7 days 22 hours ago. It was up 0% of the time over the last full 7 days, 0 of 168 hours. 10 October 2026 is when Rust Going Deep first saw it.
What is the Rust version for Test?
On Windows, Test runs Rust network protocol 2634 and build 166586. The protocol must match to join; Steam will update your game.
Wipe details
What schedule does Test follow for wipes?
Too few wipes are on record for Test to show its rhythm. All Rust servers wipe at the monthly force wipe, with Thursday 5 November at 19:00 UTC as the next date. This world has been running since 15 days 19 hours ago.
Map and rules
What settings and rules have been applied to Test?
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. PvP and raiding are enabled. Plugins or settings change the game, so the browser lists it as Modded. Plugins in use: Oxide. The server runs Valve's anti-cheat, VAC.
Which map is active on Test?
The map on Test is procedural, made by the game.
Player count
How many players are on Test?
Test was last seen 7 days 22 hours ago and is offline as you read this.
What position does Test hold in the server rankings?
Over the last seven days, Test is #13,597 by player hours, among the top 62% of all ranked servers.
Join info
How do you get into Test?
Open Rust and press F1, then type client.connect 1.170.170.24:28015. Alternatively, click Launch Rust on this page to join via Steam.