Station XX-15594 · no signal
#1 MIO PARA MIS MIERDAS (LOCAL)
Offline 93.156.201.240:28015 checked 14d ago
- Players now
- 0/ 10
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,594
- top 71%
- Last wipe
- 14d ago
- weekly schedule
- Next wipe
- 6d 4h
- Fri 27 Nov, 17:43 UTC
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. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Friday 27 November, 17:43 UTC, in 6d 4h. Its weekly schedule tag · low confidence
- wipe-day peak
- 1players, last three wipes
Coming wipes
- 6d 4hFri 27 Nov, 17:43 UTC
- 12d 5hThu 3 Dec, 19:00 UTCFW
- 13d 4hFri 4 Dec, 17:43 UTC
- 20d 4hFri 11 Dec, 17:43 UTC
- 27d 4hFri 18 Dec, 17:43 UTC
- 34d 4hFri 25 Dec, 17:43 UTC
- 41d 4hFri 1 Jan, 17:43 UTC
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 |
|---|---|---|---|---|---|---|
| Fri 6 Nov, 17:43 UTC14d ago | M0.0▲rising | 1 | – | running | 0 | |
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | – | – |
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 #1 MIO PARA MIS MIERDAS (LOCAL)?
#1 MIO PARA MIS MIERDAS (LOCAL) uses a procedural map, which the game generates.
Which settings and rules apply on #1 MIO PARA MIS MIERDAS (LOCAL)?
You will find no gather rate in the name of #1 MIO PARA MIS MIERDAS (LOCAL). At the game's default, groups can have up to 8 players. It plays in pve mode, no combat against other players. Listed as Modded in the server browser, it changes the game through plugins or settings. The plugins run on Carbon. The server has VAC off, Valve's anti-cheat.
Live population
What is the current population on #1 MIO PARA MIS MIERDAS (LOCAL)?
No players are recorded on #1 MIO PARA MIS MIERDAS (LOCAL) at this moment; it is offline, and the last sighting was 14 days 16 hours ago.
How does #1 MIO PARA MIS MIERDAS (LOCAL) rank against other Rust servers?
The last seven days of player hours place #1 MIO PARA MIS MIERDAS (LOCAL) at #15,594, in the top 71% of all ranked servers.
Operator and location
How reliably does #1 MIO PARA MIS MIERDAS (LOCAL) stay online?
#1 MIO PARA MIS MIERDAS (LOCAL) is down at the moment; the last recorded contact was 14 days 16 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. 31 October 2026 is when Rust Server Trends first recorded it.
Where in the world is #1 MIO PARA MIS MIERDAS (LOCAL) hosted?
Nothing about a region comes from #1 MIO PARA MIS MIERDAS (LOCAL). 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 93.156.201.240:28015.
What build of Rust does #1 MIO PARA MIS MIERDAS (LOCAL) use?
Rust network protocol 2636 and build 170460 on Windows is what #1 MIO PARA MIS MIERDAS (LOCAL) runs. The protocol must match for you to join, and Steam takes care of updating it.
Wipe pattern
What does wipe day look like on #1 MIO PARA MIS MIERDAS (LOCAL)?
On average, the busiest point of its recent wipes drew 1 players. The peak on the most recent wipe came 1 hours after the wipe.
On what timetable does #1 MIO PARA MIS MIERDAS (LOCAL) run its wipes?
The prediction follows its tag, because too few of #1 MIO PARA MIS MIERDAS (LOCAL)'s wipes are on record to confirm its schedule. The date of its next wipe is Friday 27 November at 17:43 UTC. 14 days 18 hours is how long the current world has been running. The tags it publishes carry a weekly wipe schedule.
Tags
What do the server tags on #1 MIO PARA MIS MIERDAS (LOCAL) mean?
These are the tags #1 MIO PARA MIS MIERDAS (LOCAL) publishes for the browser to read: gmvanilla (Game mode): You'll find vanilla survival here; mp10 (Max players): The server has 10 slots; ts8 (Group limit): Teams max out at 8, the default set by the game; v2636 (Protocol): Your game needs to be on protocol 2636 to join; cs170460 (Build): The game build is 170460; 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; ^w (Weekly): The server wipes every week; ^p (PvE): There's no player combat; the world provides the threat; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon is the plugin framework running here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On which Rust Server Trends lists does #1 MIO PARA MIS MIERDAS (LOCAL) appear?
You will find #1 MIO PARA MIS MIERDAS (LOCAL) on the following Rust Server Trends lists: Modded Rust servers, tracked live and Rust PvE servers. On the server list, the filters it matches are: Type: Modded; Game mode: PvE; Server tag: Weekly ^w, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly.
Connecting
What steps get you onto #1 MIO PARA MIS MIERDAS (LOCAL)?
To join, enter client.connect 93.156.201.240: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.