Station EU-16111 · no signal
RustMods.win | Classic x2 Monthly | TEST
Offline EU 212.3.194.139:28015 checked 34d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #16,111
- top 71% · #2554 in EU
- Last wipe
- 37d ago
- monthly schedule
- Next wipe
- 7d 2h
- Thu 5 Nov, 19:00 UTC FW
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 71% of all ranked servers, top 87% in EU. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 2h. The force wipe
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| No wipe seen yet. | ||||||
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 pageServer rules
Which map is running on RustMods.win | Classic x2 Monthly | TEST?
The map on RustMods.win | Classic x2 Monthly | TEST is procedural, produced by the game.
Which settings and rules apply on RustMods.win | Classic x2 Monthly | TEST?
2x gather is what RustMods.win | Classic x2 Monthly | TEST runs, judging by its name. Groups hold up to 8 players, which is the default for the game. It plays 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. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.
Population
How many players are recorded on RustMods.win | Classic x2 Monthly | TEST right now?
RustMods.win | Classic x2 Monthly | TEST is not responding at this moment and is offline, last seen 34 days 16 hours ago.
How does RustMods.win | Classic x2 Monthly | TEST rank against other Rust servers?
RustMods.win | Classic x2 Monthly | TEST is #2,554 in Europe and #16,111 worldwide on the past week's player hours, within the top 71% of ranked servers.
Server details
How reliably does RustMods.win | Classic x2 Monthly | TEST stay online?
No contact with RustMods.win | Classic x2 Monthly | TEST right now, and the last recorded contact was 34 days 16 hours ago. 0 of 168 hours in the last 7 full days were up time, 0% of the total. 24 September 2026 is when Rust Server Trends first recorded it.
Which region does RustMods.win | Classic x2 Monthly | TEST run from?
The EU tag is how RustMods.win | Classic x2 Monthly | TEST lists itself in Europe. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. You reach it at 212.3.194.139:28015.
Which Rust version is RustMods.win | Classic x2 Monthly | TEST running?
On Windows, RustMods.win | Classic x2 Monthly | TEST runs Rust network protocol 2633 and build 165217. Steam updates your game for you, but it has to be on the same protocol as the server to join.
Wipe day
On what timetable does RustMods.win | Classic x2 Monthly | TEST run its wipes?
An estimate from the force wipe gives RustMods.win | Classic x2 Monthly | TEST's next wipe. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. The present world dates from 37 days 16 hours. A monthly wipe schedule is published in its tags.
Lists and tags
What do the server tags on RustMods.win | Classic x2 Monthly | TEST mean?
The game's server browser reads the tags RustMods.win | Classic x2 Monthly | TEST publishes: gmrust (Game mode): You'll find standard Rust survival here; mp10 (Max players): Slots: 10; ts8 (Group limit): Teams max out at 8, the default set by the game; v2633 (Protocol): To connect, your game must be on the same protocol, 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): A region code has not been set; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): Carbon is the plugin framework running here; EU (Europe): In the server browser it appears 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 RustMods.win | Classic x2 Monthly | TEST appear?
You will find RustMods.win | Classic x2 Monthly | TEST on the following Rust Server Trends lists: 2x Rust servers, listed live, EU Rust servers and Modded Rust servers, tracked live. On the server list, the filters it matches are: Region: Europe; Type: Modded; Server tag: Monthly ^m, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly; Gather rate: 2x.
Connecting
How do you connect to RustMods.win | Classic x2 Monthly | TEST?
You can connect by pressing F1 in Rust and typing client.connect 212.3.194.139: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.