Test server
Offline 178.46.87.102:28015 checked 16d 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 69% 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
- 67/ 400
- 48/ 245
- 130/ 100
- 84/ 1000
- 7/ 700
Quick answers
Tags and search
Where does Test server appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include Test server: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the tags on Test server?
Test server's game browser tags read: gmrust (Game mode): Survival, as standard Rust does it; mp1 (Max players): There are 1 slots on this server; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): This server runs game protocol 2633, so your game must match that version to join; cs163207 (Build): This server runs build 163207; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): The Modded category fits: plugins or settings are in play. Live pop, queue length and the world's creation time also sit in the tags, shown at the top of this page.
Server info
Where can you find Test server?
Test server does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. To connect, use 178.46.87.102:28015.
What's the uptime like for Test server?
The server Test server is not reachable at the moment; the last sighting was 16 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 1 October 2026.
What Rust version is Test server on?
Rust network protocol 2633 and build 163207 is what Test server runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
What schedule does Test server follow for wipes?
The wipes recorded for Test server are too few to reveal its rhythm. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. The world you are on now was created 74 days 16 hours.
Rules and settings
Which rules and settings is Test server running?
Its name does not state a gather rate for Test server. Up to 8 players per group, which is the default. survival is the game mode, gather, build and raid, the standard game. You can fight and raid other players. 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.
Player count
Is Test server busy?
Test server was last seen 16 days 10 hours ago and is offline as you read this.
What's Test server's rank among Rust servers?
For player hours in the last seven days, Test server ranks #16,275, within the top 69% of ranked servers.
How to join
How do you get into Test server?
Open Rust and press F1, then type client.connect 178.46.87.102:28015. Alternatively, click Launch Rust on this page to join via Steam.