Rust Server Analytics 81,821 players11,830 servers
All servers
Drill-through Server detail

NO MERCY | CLASSIC | NO LIMIT

Offline EU 185.189.255.147:35100 checked 10h ago

Drill-through
FilterServeris NO MERCY | CLASSIC | NO LIMIT
Attributes
biweekly wipes vanillamoddedoxide
Last refreshed
Players now 2/ 350
7-day average 1 peak 5
Rank #3,405 top 15% · #1274 in EU
Last wipe 7d ago biweekly schedule
Next wipe 7d 4h Thu 5 Nov, 19:00 UTC FW
Capacity 1% full

Players

average and peak, with its wipes marked
AveragePeak
00.511.5215:0022:0005:0012:0020:0003:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
010020030040015:0022:0005:0012:0020:0003:00

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, measured since 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

Top 15% of all ranked servers, top 44% in EU. Ranked on player hours over the last seven days.

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. The force wipe · high confidence

usual gap3.2 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak4players, last three wipes
crowd held0%else halves by day 1

Coming wipes

InWhen, UTCKind
7d 4hThu 5 Nov, 19:00 UTCFW force wipe
20d 16hThu 19 Nov, 07:22 UTCits own
35d 4hThu 3 Dec, 19:00 UTCFW force wipe

The first 48 hours of its last wipes

Thu 22 OctMon 19 OctSat 17 Oct
01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 5, 7 hours in.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 22 Oct, 07:22 UTC7d ago 5 – running 0
Mon 19 Oct, 02:09 UTC10d ago 3 halved by day 1 3.2 days 0
Sat 17 Oct, 20:20 UTC11d ago 3 – 1.2 days 0
Thu 8 Oct, 12:02 UTC21d ago 1 halved by day 1 9.3 days 0

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. 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 wipes
ServerProfilePlayers now
СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10 EU · groups of 50+ · biweekly · 9 on average 9 / 200
RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ EU · groups of 8+ · biweekly · 8 on average 11 / 200
[ESP][PVE] PACIFIC WORLD (WIPED 15/10/2026) EU · groups of 16+ · biweekly · 4 on average 2 / 50
РЕЛАКС #2 Х2|Для новичков| No Limit EU · groups of 10+ · biweekly · 3 on average 2 / 200
#1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RU EU · groups of 10+ · biweekly · 3 on average 2 / 300
PurrRust|РУССКИЙ ДЛЯ НОВИЧКОВ|Vanilla2x|27.10 EU · groups of 8+ · biweekly · 2 on average 1 / 80

Quick answers

from the figures on this page

Wipe data

The wipe schedule for NO MERCY | CLASSIC | NO LIMIT: what is it?

The prediction follows its tag, because too few of NO MERCY | CLASSIC | NO LIMIT's wipes are on record to confirm the schedule. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. 7 days 7 hours ago the current world was made. A wipe every two weeks is stated in its tags.

Wipe day on NO MERCY | CLASSIC | NO LIMIT: what should you expect?

The average busiest count over recent wipes is 4 players. The highest player count on the latest wipe arrived 7 hours in. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. By day 1 it had fallen below half where the hold failed.

Server

What is the hosting location of NO MERCY | CLASSIC | NO LIMIT?

Its EU tag puts NO MERCY | CLASSIC | NO LIMIT in Europe. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 185.189.255.147:35100.

What Rust build does NO MERCY | CLASSIC | NO LIMIT run?

On Windows, NO MERCY | CLASSIC | NO LIMIT runs Rust network protocol 2635 and build 168909. Your game must match the protocol to join, and Steam applies that update.

How reliable is NO MERCY | CLASSIC | NO LIMIT, and is it online now?

Last seen 10 hours ago, NO MERCY | CLASSIC | NO LIMIT now reports offline. Its reported uptime indicates a restart roughly 1 hours ago. Of 168 hours in the last 7 full days, 167 were up: 99%. It entered Rust Server Analytics records on 18 September 2026.

What performance does NO MERCY | CLASSIC | NO LIMIT show?

Over 48 hours the average held at 175 server fps, and the minimum was 126. Entity count reached 104,536, covering buildings, deployables and the rest of the world. Peak memory was 3,321 MB. Lag, for players, means low fps alongside a growing entity count.

Lists and tags

How should the tags on NO MERCY | CLASSIC | NO LIMIT be read?

Tags from NO MERCY | CLASSIC | NO LIMIT, as read by the game's server browser, are: gmrust (Game mode): Rust survival, standard ruleset; mp350 (Max players): 350 slots in total; ts35 (Group limit): The cap is 35 players per team; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^b (Biweekly): A two-week wipe cycle; ^v (Vanilla): Stock Facepunch settings, with no rate changes, kits or extra rules; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded; EU (Europe): Its browser listing sits in Europe; jp0 (Custom tag): Not one of Rust's standard tags; the owner or a plugin applied it. Current players, queue length and world creation time sit in the tags as well, displayed at the top of this page.

Where does NO MERCY | CLASSIC | NO LIMIT appear across Rust Server Analytics's lists and filters?

Among the Rust Server Analytics lists NO MERCY | CLASSIC | NO LIMIT fits are: EU Rust servers: live population data and Modded Rust servers: live data. On the server list, the filters that return it are: Region: Europe; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.

Player numbers

Where does NO MERCY | CLASSIC | NO LIMIT sit among Rust servers?

For player hours over the last seven days, NO MERCY | CLASSIC | NO LIMIT places #3,405 globally and #1,274 in Europe, in the top 15% of all ranked servers.

What is the population of NO MERCY | CLASSIC | NO LIMIT?

NO MERCY | CLASSIC | NO LIMIT is offline at this refresh; the last contact was 10 hours ago. Averaging 1 players across seven days, the server reached a peak of 5. Averaged over 48 hours, activity is highest at 17:00 UTC with 1 players.

Map and rules

What settings and rules does NO MERCY | CLASSIC | NO LIMIT use?

No gather rate is given in the name of NO MERCY | CLASSIC | NO LIMIT. A maximum of 35 players per group applies. It runs survival, the standard game: gather, build, raid. Raiding and PvP combat are available. Plugins or settings modify the game, and it is listed as Modded. The plugin framework is Oxide. Its self-description is vanilla: stock Facepunch settings, with no rate changes, kits or extra rules. VAC, Valve's anti-cheat, is enabled.

What is the map for NO MERCY | CLASSIC | NO LIMIT?

The game generates a procedural map of size 4,200 with seed 1813615169 for NO MERCY | CLASSIC | NO LIMIT. Size and seed fix the map, so a RustMaps view is available from this page.

Connection

What is the way onto NO MERCY | CLASSIC | NO LIMIT?

In the Rust console (F1), enter client.connect 185.189.255.147:35100. Launch Rust on this page also works, opening Rust through Steam and connecting you. https://nomercyrust.ru is its website.

Server tags

what each one means

Published as mp350,ptrak,jp0,$r?,v2635,^b,^v,EU,gmrust,cs168909,ts35,^o^z

Game

gmrust
Game mode Rust survival, standard ruleset.
mp350
Max players 350 slots in total.
ts35
Group limit The cap is 35 players per team.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build The game build is 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code A region code is not set.

Wipe schedule

^b
Biweekly A two-week wipe cycle.

Difficulty

^v
Vanilla Stock Facepunch settings, with no rate changes, kits or extra rules.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it sits under Modded.

Region

EU
Europe Its browser listing sits in Europe.

Other

jp0
Custom tag Not one of Rust's standard tags; the owner or a plugin applied it.

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.