DWG RG-S15443Server sheetchecked 36d ago
test
Offline 145.224.74.5:20000 checked 36d 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
Top 67% 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
| 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
Quick answers
Recorded details
What uptime is recorded for test, and is it up?
The current state of test is offline, with the last sighting 36 days 5 hours ago. 0 of 168 hours up over the last 7 full days, which is 0% of the time. On 22 September 2026 is when Rust Graphs first saw it.
In which location is test hosted?
There is no region published by test. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. 145.224.74.5:20000 is its address.
On which Rust version is test running?
The platform is Windows and the version is Rust network protocol 2633 and build 165217 on test. Steam updates your game, which must be on the same protocol for you to join.
Counts
What does the population history show for test?
No response from test; the server was last seen 36 days 5 hours ago.
Against other Rust servers, where is test placed?
Over the last seven days, test records #15,443 for player hours: the top 67% of all ranked servers.
Schedules
What wipe schedule has been recorded for test?
Too few wipes are on record for test to show its rhythm. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The world it runs now was made 47 days 9 hours ago.
Settings
What settings and rules apply on test?
No gather rate is stated in the name of test. The group limit is 8 players, the game's default. It runs the survival game mode, the standard game: gather, build, raid. Fighting and raiding between players are enabled. Community is its tab in the server browser. VAC is off: that is Valve's anti-cheat.
Which map has test loaded?
test runs a procedural map, which the game generates.
Tags
Where does test appear among the Rust Graphs lists and filters?
On Rust Graphs, test is placed in these lists: Rust community servers, plotted. On the server list, these filters bring it up: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meaning is attached to each tag on test?
Tags published by test, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp10 (Max players): 10 player slots; ts8 (Group limit): Teams are capped at 8, the default setting; v2633 (Protocol): Join only if your game is on protocol 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is recorded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
How to join
How is test joined?
Connect with client.connect 145.224.74.5:20000: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you.
Server tags
Published as mp10,ptrak,$r?,v2633,gmrust,cs165217,ts8
Game
gmrust
mp10
ts8
v2633
cs165217
ptrak
$r?
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.