Station XX-15614 · no signal
Test567
Offline 107.201.49.208:28015 checked 27d ago
- Players now
- 1/ 50
- 2% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,614
- top 66%
- Last wipe
- 32d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 1of 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 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.
- usual gap
- 0.6 daysbetween real wipes
- 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, 25 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Fri 25 Sep, 16:26 UTC32d ago | M0.0▲rising | 1 | – | running | 0 | |
| Fri 25 Sep, 02:28 UTC33d ago | M0.0▲rising | 1 | – | 0.6 days | 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 pageMap and rules
Which map is running on Test567?
Test567 uses a procedural map, which the game generates.
Which settings and rules apply on Test567?
You will find no gather rate in the name of Test567. At the game's default, groups can have up to 8 players. It plays in survival mode, standard play, with gathering, building and raiding. Player combat and raiding are permitted. Listed as Modded in the server browser, it changes the game through plugins or settings. Carbon is the plugin framework it runs. VAC, Valve's anti-cheat, is switched on.
Player counts
What is the current population on Test567?
Test567 is not responding at this moment and is offline, last seen 27 days 12 hours ago.
How does Test567 rank against other Rust servers?
The last seven days of player hours place Test567 at #15,614, in the top 66% of all ranked servers.
Operator and location
How reliably does Test567 stay online?
Test567 is down at the moment; the last recorded contact was 27 days 12 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. On 25 September 2026 it was recorded for the first time by Rust Server Trends.
Which region does Test567 run from?
Nothing about a region comes from Test567. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 107.201.49.208:28015.
What build of Rust does Test567 use?
Test567 is running Rust network protocol 2633 and build 165217 on a machine with Windows. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe pattern
What does wipe day look like on Test567?
1 players, on average, was the busiest crowd at its recent wipes. The peak on the most recent wipe came 25 hours after the wipe.
On what timetable does Test567 run its wipes?
Too few wipes of Test567 are on record yet to show its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. It has run its current world for 32 days 19 hours.
Lists and tags
What do the server tags on Test567 mean?
The game's server browser reads the tags Test567 publishes: gmrust (Game mode): Survival in standard Rust; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): Game protocol 2633: to join, your game must match this version; cs165217 (Build): It runs game build 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. You will find its current players, queue and world creation time among the tags, displayed at the top of this page.
On which Rust Server Trends lists does Test567 appear?
You will find Test567 on the following Rust Server Trends lists: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How to join
What steps get you onto Test567?
To join, enter client.connect 107.201.49.208:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for 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.