Rust StatisticsWorking papers on every public Rust server · 93,889 players now

#1 MIO PARA MIS MIERDAS (LOCAL)

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 14d ago · 93.156.201.240:28015

Abstract

We describe the public Rust server #1 MIO PARA MIS MIERDAS (LOCAL), reached at 93.156.201.240:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,594 of all servers, the top 71%. It last wiped 14d ago on a published weekly schedule; the next wipe is expected Friday 27 November, 17:43 UTC, its weekly schedule tag.

Keywordsweekly wipes modded carbon pve

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/100% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,594top 71%
Last wipe14d agoweekly schedule
Next wipe36d 2hFri 27 Nov, 17:43 UTC

2Population

Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.

No hourly history yet.
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

3Performance

We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: 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.

4Rank

The server stands in the top 71% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.

RankRank in region
15k10k15k20k31 Oct3 Nov5 Nov8 Nov10 Nov13 Nov
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: from its schedule tag

The next wipe is expected Friday 27 November, 17:43 UTC, in 6d 2h. Its weekly schedule tag (low confidence).

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Wipe-day peak1players, last three wipes
Table 3: Coming wipes, as expected.
When (UTC)InKind
Fri 27 Nov, 17:436d 2hits own schedule
Thu 3 Dec, 19:0012d 3hforce wipefw
Fri 4 Dec, 17:4313d 2hits own schedule
Fri 11 Dec, 17:4320d 2hits own schedule
Fri 18 Dec, 17:4327d 2hits own schedule
Fri 25 Dec, 17:4334d 2hits own schedule
Fri 1 Jan, 17:4341d 2hits own schedule
00.250.50.751+0h+9h+19h+28h+38h+47h
Figure 4: 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.

5.2History

Table 4: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 6 Nov, 17:4314d ago 1 – running 0
Thu 5 Nov, 19:00fw15d ago – – – –

Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.

6Map and settings

No map picture published
Figure 5: The map: Procedural Map.
Table 5: The server's published settings.
Address93.156.201.240:28015
Region–
Max players10
Group limit8, the default
Wipe scheduleweekly
Last wipe6 Nov 2026, 18:23 UTC
Hostname–
First seen31 Oct 2026
MapProcedural Map
Size–
Seed–

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust servers listed live [2], pve wipes and settings [3] and predicted wipe schedule [4].

Table 6: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
[PvE] TruePvE [x1-x5|Loot+|NPC|RB|Quests|NoRaid/NoKill]groups of 200+ · 1x · weekly · 16 on average34/100
[SEA]Singapore PVEx20 11/21/26 SkillTree EventsEA · groups of 8+ · weekly · 4 on average10/50
RustMode PvE | 11/19 | No Tech Tree | Skills | Raids | EventsNA · groups of 150+ · weekly · 4 on average4/50
TRINUM.RU PVE NoKill NoRaid Skills Artifacts Boss ZombieEU · groups of 8+ · weekly · 3 on average9/250
Moradon - PVE - [AU] [Raidable Bases] [Skill Tree]OC · groups of 8+ · weekly · 3 on average4/30
RUSTILA[PVE]NoRAID|NoKILL|RAIDBASE|Events|Quest|TPgroups of 8+ · weekly · 1 on average3/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1In which location is #1 MIO PARA MIS MIERDAS (LOCAL) based?

There is no region published for #1 MIO PARA MIS MIERDAS (LOCAL). Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 93.156.201.240:28015.

A.2How reliable is #1 MIO PARA MIS MIERDAS (LOCAL), and is it currently online?

At the present moment, #1 MIO PARA MIS MIERDAS (LOCAL) is offline; it was last seen 14 days 18 hours ago. The server was up 0% of the time over the last 7 full days, 0 of 168 hours. The first record of it by Rust Statistics dates to 31 October 2026.

A.3What version of Rust is run on #1 MIO PARA MIS MIERDAS (LOCAL)?

#1 MIO PARA MIS MIERDAS (LOCAL) is running Rust network protocol 2636 and build 170460 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe schedule

A.4On what cycle does #1 MIO PARA MIS MIERDAS (LOCAL) wipe?

The record of #1 MIO PARA MIS MIERDAS (LOCAL)'s wipes is too sparse to confirm the schedule, so the prediction is based on its tag. The server is due to wipe on Friday 27 November at 17:43 UTC. The world currently in use was created 14 days 20 hours ago. According to its tags, the server wipes on a weekly schedule.

A.5How would you describe wipe day on #1 MIO PARA MIS MIERDAS (LOCAL)?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 1 hours after the latest wipe.

Player count

A.6What is the rank of #1 MIO PARA MIS MIERDAS (LOCAL) among Rust servers?

Ranked by player hours across seven days, #1 MIO PARA MIS MIERDAS (LOCAL) holds #15,594, in the top 71% of all ranked servers.

A.7What is the population level of #1 MIO PARA MIS MIERDAS (LOCAL)?

The last recorded sighting of #1 MIO PARA MIS MIERDAS (LOCAL) was 14 days 18 hours ago; it is offline now.

Tags, lists

A.8How should the tags on #1 MIO PARA MIS MIERDAS (LOCAL) be interpreted?

Tags from #1 MIO PARA MIS MIERDAS (LOCAL), read by the game's server browser, are gmvanilla (Game mode): Survival on vanilla rules; mp10 (Max players): The slot count is 10; ts8 (Group limit): 8 per team, the value the game sets by default; v2636 (Protocol): The game protocol is 2636; your client must match it to join; cs170460 (Build): Build 170460 is the one running; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^w (Weekly): A weekly wipe cycle applies; ^p (PvE): There is no player combat; the world supplies the danger; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; ^y (Carbon): Plugins run through Carbon. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can #1 MIO PARA MIS MIERDAS (LOCAL) be found among the Rust Statistics lists and filters?

These Rust Statistics lists include #1 MIO PARA MIS MIERDAS (LOCAL): Modded Rust servers and Rust PvE servers: live list. These filters on the server list return it: Type: Modded; Game mode: PvE; Server tag: Weekly ^w, PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly.

Rules, settings, map

A.10Under what rules and settings does #1 MIO PARA MIS MIERDAS (LOCAL) operate?

The name of #1 MIO PARA MIS MIERDAS (LOCAL) states no gather rate. The group cap is 8 players, which is the default in the game. Listed as pve, the game mode is no player-versus-player fighting. Plugins or settings change the game; the browser files it under Modded. Carbon plugins are running. VAC is inactive: the anti-cheat from Valve is off.

A.11What is the map for #1 MIO PARA MIS MIERDAS (LOCAL)?

On #1 MIO PARA MIS MIERDAS (LOCAL) the terrain is procedural, built by the game itself.

Connection

A.12How do you connect to #1 MIO PARA MIS MIERDAS (LOCAL)?

Press F1 inside Rust to open the console and enter client.connect 93.156.201.240:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.

Appendix BServer tags

What each of the server's tags means. Published as mp10,ptrak,$r?,v2636,^z,^y,^w,^p,gmvanilla,cs170460,ts8.

Table 7: The server's tags and their meanings.
TagMeaning
Game
gmvanillaGame mode. Survival on vanilla rules.
mp10Max players. The slot count is 10.
ts8Group limit. 8 per team, the value the game sets by default.
v2636Protocol. The game protocol is 2636; your client must match it to join.
cs170460Build. Build 170460 is the one running.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. No region code is set.
Wipe schedule
^wWeekly. A weekly wipe cycle applies.
Gameplay
^pPvE. There is no player combat; the world supplies the danger.
Mods and access
^zModded. The game is altered by plugins or settings, so it is listed as Modded.
^yCarbon. Plugins run through Carbon.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

References

  1. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust servers listed live. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Pve wipes and settings. ruststatistics.org/top-rust-pve-servers.
  4. [4]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.