Station XX-17108 · no signal
test72
Offline 92.255.175.39:31000 checked 19d ago
- Players now
- 0/ 50
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #17,108
- top 71%
- Last wipe
- 20d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 50 slots
- Motion · 24 h
- M –not enough readings
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 71% 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.
- wipe-day peak
- 1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | running | – |
| Sun 1 Nov, 10:48 UTC20d ago | M0.0▲rising | 1 | – | – | 0 |
Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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 wipesQuick answers
from the figures on this pageRules and settings
Which map is running on test72?
test72 uses a procedural map, which the game generates.
Which settings and rules apply on test72?
The name of test72 gives no gather rate. Groups hold up to 8 players, which is the default for the game. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Plugins or settings alter the game here; the browser lists it as Modded. The plugins run on Carbon. Anti-cheat is on: VAC, from Valve.
Player counts
What is the current population on test72?
A reading taken now finds test72 offline; the most recent activity was 19 days 20 hours ago.
How does test72 rank against other Rust servers?
Over the last seven days, test72 recorded enough player hours to reach #17,108 worldwide, placing it in the top 71% of all ranked servers.
Server details
How reliably does test72 stay online?
No contact with test72 right now, and the last recorded contact was 19 days 20 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. Its earliest appearance in the records of Rust Server Trends dates to 1 November 2026.
Which region does test72 run from?
A region is not published by test72. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. 92.255.175.39:31000 is the address it uses.
What build of Rust does test72 use?
On Windows, test72 runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on test72?
1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 1 hours after the wipe.
On what timetable does test72 run its wipes?
Too few wipes of test72 are on record yet to show its rhythm. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 20 days 2 hours is how long the current world has been running.
Server tags
What do the server tags on test72 mean?
These are the tags test72 publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp50 (Max players): The server has 50 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): No region code is set for this server; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does test72 appear?
You will find test72 on the following Rust Server Trends lists: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Connecting
How do you connect to test72?
You can connect by pressing F1 in Rust and typing client.connect 92.255.175.39:31000 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you.
Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.