TEST
Offline 94.78.215.196:28015 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 64% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Wed 30 Sep, 12:23 UTC17d ago | 1 | – | running | 0 |
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
- 282/ 300
- 585/ 600
- 470/ 500
- 130/ 200
- 482/ 525
- 212/ 250
Quick answers
Tags and filters
Where does TEST appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry TEST are: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How should you read the tags on TEST?
The server browser shows these tags for TEST: gmrust (Game mode): This is the standard Rust survival experience; mp10 (Max players): There are 10 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2633 (Protocol): The protocol is 2633; a different version won't get you in; cs165217 (Build): It's on build 165217; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): It has no region code. 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
Where can you find TEST?
TEST does not put out a region. Rust Going Deep reports the location a server claims; it does not check where the machine actually is. You can reach it at 94.78.215.196:28015.
How reliable is TEST?
The server TEST is not reachable at the moment; the last sighting was 17 days 20 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 30 September 2026.
What Rust version is TEST on?
Rust network protocol 2633 and build 165217 is what TEST runs, on Windows. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe details
What schedule does TEST follow for wipes?
TEST's rhythm is unclear because not enough wipes are on record yet. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 17 days 20 hours ago.
What happens on wipe day at TEST?
The average peak across recent wipes is 1 players. The peak crowd on the latest wipe came 0 hours in.
Settings and map
What settings are in place on TEST?
No gather rate appears in the name of TEST. 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. The server browser lists it under Community, making it a community server. The server runs Valve's anti-cheat, VAC.
What's the map on TEST?
TEST uses a game-generated procedural map.
Population
How many players are on TEST?
Right now TEST is offline, with its last appearance 17 days 20 hours ago.
What's TEST's rank among Rust servers?
Over the last seven days, TEST is #15,391 by player hours, among the top 64% of all ranked servers.
Join info
What's the process to join TEST?
Open Rust and press F1, then type client.connect 94.78.215.196:28015. Alternatively, click Launch Rust on this page to join via Steam.