RadarTest
Offline 77.20.252.163:28015 checked 35d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 66% 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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sun 6 Sep, 11:57 UTC52d ago | – | – | 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- 147/250
- 116/200
- 13/250
- 18/250
- 13/100
- 29/200
Quick answers
from the figures on this pageWipe timing
How often does RadarTest wipe, and when?
The rhythm of RadarTest's wipes cannot be told yet: too few are on record. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 52 days 16 hours ago.
Lists and filters
How should you read the tags on RadarTest?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2633 (Protocol): Protocol 2633: join only on the same game version; cs162929 (Build): The server runs game build 162929; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set from RadarTest. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show RadarTest?
On Rust Metrics, RadarTest sits in these lists: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
Where does RadarTest sit in the rankings?
Player hours over seven days put RadarTest at #14,393, in the top 66% of all ranked servers.
What player count does RadarTest carry?
Reading for RadarTest: offline at this moment; last seen 35 days 5 hours ago.
Server
What location is RadarTest hosted in?
No region tag on RadarTest. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 77.20.252.163:28015.
What Rust version is RadarTest on?
Rust network protocol 2633 and build 162929 on Windows is the build RadarTest runs. Matching protocol is required to join. Let Steam update your game.
How reliable is RadarTest, and is it online now?
Check: connection. RadarTest is offline at this moment. Last contact was 35 days 5 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 14 September 2026.
Map and rules
How is RadarTest configured, and what rules are in force?
Reading the name gives no gather rate for RadarTest. 8 players per group, the default value. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Anti-cheat reading: VAC on, Valve's system.
Which map is live on RadarTest?
Procedural map on RadarTest, made by the game's generator.
How to join
How can you get onto RadarTest?
Press F1 in Rust and enter client.connect 77.20.252.163:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.