StatusLive Servers online11,814 Players72,000 Populated3,646 Wiped · 3 h206 Interval5 min Date29 OCT 2026

DWG RG-S3392Server sheetchecked 9h ago

NO MERCY | CLASSIC | NO LIMIT

Offline EU 185.189.255.147:35100 checked 9h ago

biweekly wipes vanillamoddedoxide
Connect
Players now 2/ 350 1% full
7-day average1peak 5
Rank#3,392top 15% · #1270 in EU
Last wipe7d agobiweekly schedule
Next wipe7d 5hThu 5 Nov, 19:00 UTC FW
Fig. 1

Players

AveragePeak
00.511.5214:0021:0004:0012:0020:0003:00

Hourly average and peak, UTC.

Fig. 1Players on NO MERCY | CLASSIC | NO LIMIT
Fig. 2

Server performance

010020030040014:0021:0004: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.

Fig. 2FPS, entities and memory
Fig. 3

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.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

from its schedule tag

Next wipe Thursday 5 November, 19:00 UTC, in 7d 5h. 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

  1. 7d 5hThu 5 Nov, 19:00 UTCFW
  2. 20d 18hThu 19 Nov, 07:22 UTC
  3. 35d 5hThu 3 Dec, 19:00 UTCFW

The first 48 hours of its last wipes

Thu 22 OctMon 19 OctSat 17 Oct
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

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

ScheduleExpected wipes
Log

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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10EU · groups of 50+ · biweekly · 9 on average
8 / 200
02
RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮEU · groups of 8+ · biweekly · 8 on average
9 / 200
03
[ESP][PVE] PACIFIC WORLD (WIPED 15/10/2026)EU · groups of 16+ · biweekly · 4 on average
2 / 50
04
РЕЛАКС #2 Х2|Для новичков| No LimitEU · groups of 10+ · biweekly · 3 on average
2 / 200
05
#1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RUEU · groups of 10+ · biweekly · 3 on average
2 / 300
06
PurrRust|РУССКИЙ ДЛЯ НОВИЧКОВ|Vanilla2x|27.10EU · groups of 8+ · biweekly · 2 on average
1 / 80
Ref.Similar
General notes

Quick answers

from the figures on this page

Recorded details

Is NO MERCY | CLASSIC | NO LIMIT online, and what uptime has been recorded?

The current state of NO MERCY | CLASSIC | NO LIMIT is offline, with the last sighting 9 hours ago. Counted from its reported uptime, the last restart was about 1 hours ago. For the last 7 full days the record is 167 of 168 hours up, 99% of the time. First seen by Rust Graphs on 18 September 2026.

How does NO MERCY | CLASSIC | NO LIMIT perform, as measured?

175 server fps on average over the last 48 hours, and never under 126. Counted at its highest: 104,536 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 3,321 MB. What players feel as lag is low fps together with a climbing entity count.

In which location is NO MERCY | CLASSIC | NO LIMIT hosted?

In Europe NO MERCY | CLASSIC | NO LIMIT lists itself, tagged EU. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. 185.189.255.147:35100 is its address.

On which Rust version is NO MERCY | CLASSIC | NO LIMIT running?

Rust network protocol 2635 and build 168909 on Windows: that is what NO MERCY | CLASSIC | NO LIMIT runs. The same protocol is required for joining, and Steam updates your game to it.

Population

What player count is recorded on NO MERCY | CLASSIC | NO LIMIT?

NO MERCY | CLASSIC | NO LIMIT is not responding at the latest refresh; the last record of it online is 9 hours ago. The seven-day mean is 1 players; the peak over the same period is 5. Averaged over the last 48 hours, the player count is highest at 17:00 UTC: 1 players.

What rank has been recorded for NO MERCY | CLASSIC | NO LIMIT?

NO MERCY | CLASSIC | NO LIMIT also measures #1,270 in Europe on the same seven-day player-hour count, at #3,392 globally and in the top 15% of ranked servers.

Wipe times

On NO MERCY | CLASSIC | NO LIMIT, what does the data show for wipe day?

At their busiest, its recent wipes drew 4 players on average. 7 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. In the other cases the crowd was below half by day 1.

On NO MERCY | CLASSIC | NO LIMIT, when do wipes occur?

Too few of NO MERCY | CLASSIC | NO LIMIT's wipes are on record for its schedule to be confirmed, so its tag is followed for the prediction. On Thursday 5 November at 19:00 UTC the force wipe falls; that is the next wipe, and it wipes every Rust server. The current world has been in use since 7 days 5 hours ago. A wipe schedule of one wipe every two weeks is listed in its tags.

Map and rules

Which settings does NO MERCY | CLASSIC | NO LIMIT run, and what rules?

The name of NO MERCY | CLASSIC | NO LIMIT records no gather rate. The group limit is 35 players. survival, the standard game: gather, build, raid, is the game mode. PvP and raiding are on. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. It describes itself as vanilla, by which it means no changed rates, kits or rules: the game as Facepunch ships it. Anti-cheat: VAC, from Valve, is on.

On which map is NO MERCY | CLASSIC | NO LIMIT played?

Size 4,200 with seed 1813615169: that is the procedural map NO MERCY | CLASSIC | NO LIMIT runs, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Tags

Where does NO MERCY | CLASSIC | NO LIMIT appear among the Rust Graphs lists and filters?

The Rust Graphs lists that carry NO MERCY | CLASSIC | NO LIMIT are: Europe servers, plotted and Modded Rust servers. It is returned by these filters on the server list: 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.

Which meaning is attached to each tag on NO MERCY | CLASSIC | NO LIMIT?

Tags published by NO MERCY | CLASSIC | NO LIMIT, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp350 (Max players): 350 player slots; ts35 (Group limit): Team size is capped at 35; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): No region code is recorded; ^b (Biweekly): The wipe cycle is two weeks; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; EU (Europe): The server browser lists it under Europe; jp0 (Custom tag): The owner or a plugin set this tag; it is not standard Rust. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

How to join

What is the way to connect to NO MERCY | CLASSIC | NO LIMIT?

Connect with client.connect 185.189.255.147:35100: start Rust, press F1, use the console. Launch Rust and join on this page is the alternative, opening Rust through Steam and connecting you. You will find its website at https://nomercyrust.ru.

NotesAnswered from the figures
Key

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 Standard survival, as Rust plays.
mp350
Max players 350 player slots.
ts35
Group limit Team size is capped at 35.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build 168909 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code No region code is recorded.

Wipe schedule

^b
Biweekly The wipe cycle is two weeks.

Difficulty

^v
Vanilla No changed rates, kits or rules: the game as Facepunch ships it.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded The game is changed by plugins or settings; the listing is Modded.

Region

EU
Europe The server browser lists it under Europe.

Other

jp0
Custom tag The owner or a plugin set this tag; it is not standard Rust.

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.

KeyTag string decoded