Station XX-16036 · no signal
TEST
Offline 188.191.42.1:28015 checked 27d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,036
- top 69%
- Last wipe
- 27d ago
- no schedule published
- Next wipe
- –
- no rhythm it keeps
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 10 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 69% of all ranked servers. 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.
- usual gap
- 1.3 daysbetween real wipes
- on rhythm
- 38%of its recent 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 0, 0 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 1 Oct, 20:49 UTC FW27d ago | M0.0■steady | 0 | – | – | running | 0 |
| Thu 1 Oct, 09:15 UTC28d ago | M0.0▲rising | 1 | – | 0.5 days | 0 | |
| Sat 26 Sep, 08:30 UTC33d ago | M0.0■steady | 1 | – | 5 days | 1 | |
| Fri 25 Sep, 07:55 UTC34d ago | M0.0■steady | 1 | – | 1 days | 1 | |
| Wed 23 Sep, 20:24 UTC35d ago | M0.0▲rising | 1 | – | 1.5 days | 0 | |
| Tue 22 Sep, 11:54 UTC37d ago | M0.0■steady | 1 | – | 1.4 days | 1 | |
| Mon 21 Sep, 05:54 UTC38d ago | M0.0■steady | 1 | – | 1.2 days | 1 | |
| Sun 20 Sep, 10:10 UTC39d ago | M0.0■steady | 1 | – | 0.8 days | 1 | |
| Fri 18 Sep, 01:21 UTC41d ago | M0.0■steady | 1 | held half | 2.4 days | 1 | |
| Mon 14 Sep, 12:58 UTC45d ago | M0.0■steady | 1 | held half | 3.5 days | 1 | |
| Sun 13 Sep, 23:55 UTC45d ago | M0.0■steady | 1 | – | 0.5 days | 1 |
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 TEST?
A procedural map runs on TEST, generated by the game.
Which settings and rules apply on TEST?
No gather rate appears in the name of TEST. The group limit is 8 players, the game's default. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. Anti-cheat is on: VAC, from Valve.
Population
What is the current population on TEST?
A reading taken now finds TEST offline; the most recent activity was 27 days 20 hours ago.
How does TEST rank against other Rust servers?
The last seven days of player hours place TEST at #16,036, in the top 69% of all ranked servers.
Operator and location
How reliably does TEST stay online?
No contact with TEST right now, and the last recorded contact was 27 days 20 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 13 September 2026 is when Rust Server Trends first recorded it.
Which region does TEST run from?
A region is not published by TEST. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. You reach it at 188.191.42.1:28015.
What build of Rust does TEST use?
On Windows, TEST runs Rust network protocol 2633 and build 163207. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on TEST?
The recent wipes averaged a busiest count of 1 players. The peak on the most recent wipe came 0 hours after the wipe.
How often does TEST wipe, and on which days?
There is no next wipe to predict at TEST, since its wipes fall at irregular times. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The present world dates from 27 days 21 hours.
Tags
What do the server tags on TEST mean?
Tags published by TEST and read by the game's server browser include gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team is the default, and that's the limit here; v2633 (Protocol): Your game needs to be on protocol 2633 to join; cs163207 (Build): It runs game build 163207; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): No region code is set for this server. 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 TEST appear?
You will find TEST on the following Rust Server Trends lists: Rust community servers without the side modes. On the server list, the filters it matches are: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
How to join
What steps get you onto TEST?
Enter client.connect 188.191.42.1:28015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust 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.