Station EU-15414 · no signal
TEST
Offline EU 95.52.241.30:28015 checked 5d ago
- Players now
- 0/ 300
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,414
- top 69% · #2590 in EU
- Last wipe
- 17d ago
- weekly schedule
- Next wipe
- 1d 16h
- Thu 29 Oct, 18:18 UTC
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 300 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, top 89% in EU. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 29 October, 18:18 UTC, in 1d 16h. Its weekly schedule tag · low confidence
- usual gap
- 1 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 0players, last three wipes
Coming wipes
- 1d 16hThu 29 Oct, 18:18 UTC
- 8d 17hThu 5 Nov, 19:00 UTCFW
- 15d 16hThu 12 Nov, 18:18 UTC
- 22d 16hThu 19 Nov, 18:18 UTC
- 29d 16hThu 26 Nov, 18:18 UTC
- 36d 17hThu 3 Dec, 19:00 UTCFW
- 43d 16hThu 10 Dec, 18:18 UTC
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 22 Oct, 18:18 UTC5d ago | M0.0■steady | 0 | – | – | running | 0 |
| Sat 10 Oct, 14:54 UTC17d ago | M0.0■steady | 0 | – | 12.1 days | 0 | |
| Fri 9 Oct, 14:57 UTC18d ago | M0.0▲rising | 1 | – | 1 days | 0 | |
| Thu 8 Oct, 20:04 UTC19d ago | M0.3▲rising | 2 | – | 0.8 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 pageRules and settings
Which settings and rules apply on TEST?
No gather rate appears in the name of TEST. The group limit is 24 players. In survival mode, gather, build and raid in the standard game. Player combat and raiding are permitted. Plugins or settings alter the game here; the browser lists it as Modded. Oxide is the plugin framework it runs. It describes itself as vanilla, which means unchanged from Facepunch's release: no altered rates, kits or rules. The server has VAC off, Valve's anti-cheat.
Player counts
What is the current population on TEST?
TEST is not responding at this moment and is offline, last seen 5 days 6 hours ago. Averaged across the last seven days, the population was 0 players.
How does TEST rank against other Rust servers?
TEST is #2,590 in Europe and #15,414 worldwide on the past week's player hours, within the top 69% of ranked servers.
Server details
How reliably does TEST stay online?
TEST is down at the moment; the last recorded contact was 5 days 6 hours ago. It was up 2% of the time across the last 7 full days: 4 of 168 hours. 1 October 2026 is when Rust Server Trends first recorded it.
Which region does TEST run from?
With its EU tag, TEST lists itself in Europe. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 95.52.241.30:28015.
What build of Rust does TEST use?
On Windows, TEST runs Rust network protocol 2635 and build 168909. 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 0 players. 0 hours after the latest wipe, the crowd peaked.
On what timetable does TEST run its wipes?
The prediction follows its tag, because too few of TEST's wipes are on record to confirm its schedule. Thursday 29 October at 18:18 UTC is when its next wipe is due. The present world dates from 17 days 10 hours. A weekly wipe schedule is published in its tags.
Tags
What do the server tags on TEST mean?
These are the tags TEST publishes for the browser to read: gmrust (Game mode): The game mode is standard Rust survival; mp300 (Max players): The server has 300 slots; ts24 (Group limit): The team limit is 24; v2635 (Protocol): To connect, your game must be on the same protocol, 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): A region code has not been set; ^w (Weekly): Wipes happen weekly; ^v (Vanilla): Unchanged from Facepunch's release: no altered rates, kits or rules; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EU (Europe): The server browser files it under Europe. 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 TEST appear?
These Rust Server Trends lists include TEST: EU Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
How to join
What steps get you onto TEST?
You can connect by pressing F1 in Rust and typing client.connect 95.52.241.30:28015 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.