Test Server
Online 216.245.177.46:28015 checked 7m ago
Server instruments
last reading Thu 17:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 76 · below 20 is lag, below 10 is badEntities
48 h range 85,909–88,366 · memory 1,988 MBUptime
18 h 50 min since its last restart, at the last readingPlayers
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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 69% of all ranked servers, and #195 of the solo servers (top 89%). Ranked on player hours over the last seven days.
Wipe schedule
no rhythm it keepsIts 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 wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 28 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 6 Oct, 10:53 UTC23d ago | 1 | – | running | 0 |
| Thu 17 Sep, 10:39 UTC42d ago | 1 | halved by day 2 | 19 days | 0 |
| Tue 15 Sep, 00:57 UTC44d ago | 1 | held half | 2.4 days | 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- 314/325
- 89/100
- 54/100
- 198/215
- 38/100
- 3/100
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on Test Server?
An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 28 hours in. Until the next wipe, the crowd stayed above half that peak in 50% of its recent wipes. By day 2 it fell below half when it didn't.
How often does Test Server wipe, and when?
No next wipe can be predicted for Test Server, which wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 23 days 7 hours ago.
Tag meanings
How should you read the tags on Test Server?
Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp30 (Max players): 30 slots in total; ts1 (Group limit): Teams are capped at 1; v2634 (Protocol): Your game must run protocol 2634 to get in; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from Test Server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Test Server?
These Rust Metrics lists carry Test Server: Rust community servers: live readings and Solo-only Rust servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: Solo.
Player count
What position does Test Server hold among Rust servers?
Ranking for Test Server: #15,310 on seven-day player hours, top 69% of all ranked servers. The solo group places it at #195.
What is the population on Test Server?
Current headcount on Test Server: 0 players, 30 slots available. Check: player average. 0 over the last seven days.
Server
Where does Test Server sit?
No region comes from Test Server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 216.245.177.46:28015.
What Rust version is Test Server on?
Version check: Rust network protocol 2634 and build 166652 on Windows, run by Test Server. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on Test Server within range?
Check: fps. Average 97 server fps over the last 48 hours, low of 76. Within range. Reading: 88,366 entities at the highest. That covers buildings, deployables and everything else. Memory peak: 5,624 MB. Expect lag when fps falls and entities climb.
How reliable is Test Server, and is it online now?
Test Server reports online. Status: normal. Reading: uptime. About 18 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Check: first contact. Rust Metrics logged it on 13 September 2026.
Settings and map
What rules does Test Server enforce, and what are its settings?
Check: gather rate. The name Test Server does not state one. Check: teams. Solo only — no teams. The mode is survival. Note the following: standard play of gathering, building and raiding. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is on.
What map is Test Server on?
Check: map. Procedural, size 4,000, seed 3513435846, generated by the game on Test Server. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Connection
What do you do to join Test Server?
To join: start Rust, press F1 and type client.connect 216.245.177.46:28015. Or press Launch Rust here and Steam opens the game and connects you.