test
Offline 181.163.45.253:28015 checked 22d 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 61% 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 |
|---|---|---|---|---|
| Fri 25 Sep, 22:25 UTC22d ago | 1 | – | running | 1 |
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
- 352/ 375
- 590/ 600
- 397/ 475
- 120/ 200
- 607/ 625
- 243/ 250
Quick answers
Tags and search
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. The server list shows it under 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): Survival, as standard Rust does it; mp1 (Max players): The slot count is 1; 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): This server runs build 165217; ptrak (Networking): Standard RakNet networking; $r? (Region code): The region field is empty. 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
What location is test in?
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 181.163.45.253:28015.
How reliable is test?
Right now test is offline, having last been seen 22 days 11 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. The first sighting by Rust Going Deep was on 25 September 2026.
What Rust version is test on?
The version on test is Rust network protocol 2633 and build 165217, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
What schedule does test follow for wipes?
The wipes recorded for test are too few to reveal its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. The world you are on now was created 22 days 11 hours.
What happens on wipe day at test?
Across its recent wipes, the average busiest point drew 1 players. On the latest wipe, 0 hours passed before the crowd peaked.
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. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Community is where the server browser puts it, as a community server. VAC is on: Valve's anti-cheat is active.
What's the map on test?
A procedural map, generated by the game, is in play on test.
Population
How many players are on test?
test was last seen 22 days 11 hours ago and is offline as you read this.
Where does test sit in the rankings?
For player hours in the last seven days, test ranks #14,105, within the top 61% of ranked servers.
Getting in
What's the way to join test?
Open Rust and press F1, then type client.connect 181.163.45.253:28015. Alternatively, click Launch Rust on this page to join via Steam.