Station EU-3347 · no signal
NO MERCY | CLASSIC | NO LIMIT
Offline EU 185.189.255.147:35100 checked 3h ago
- Players now
- 2/ 350
- 1% full
- Motion · 24 h
- M0.0▲rising
- +0 players on the day
- 7-day average
- 1
- peak 5
- Rank
- #3,347
- top 15% · #1250 in EU
- Last wipe
- 6d ago
- biweekly schedule
- Next wipe
- 7d 11h
- Thu 5 Nov, 19:00 UTC FW
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 2of 350 slots
- Motion · 24 h
- M0.0▲rising+0 players
- Sharpest hour
- +1into Tue 09:00 UTC
- Peak · 48 h
- 2most players in any hour
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, measured since 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 15% of all ranked servers, top 43% in EU. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Thursday 5 November, 19:00 UTC, in 7d 11h. The force wipe · high confidence
- usual gap
- 3.2 daysbetween real wipes
- on rhythm
- 33%of its recent wipes
- wipe-day peak
- 4players, last three wipes
- crowd held
- 0%else halves by day 1
Coming wipes
- 7d 11hThu 5 Nov, 19:00 UTCFW
- 21d 0hThu 19 Nov, 07:22 UTC
- 35d 11hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 5, 7 hours in.
Wipes
newest first| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 22 Oct, 07:22 UTC6d ago | M0.7▲rising | 5 | – | running | 0 | |
| Mon 19 Oct, 02:09 UTC10d ago | M0.5▲rising | 3 | halved by day 1 | 3.2 days | 0 | |
| Sat 17 Oct, 20:20 UTC11d ago | M0.5▲rising | 3 | – | 1.2 days | 0 | |
| Thu 8 Oct, 12:02 UTC20d ago | M0.0▲rising | 1 | halved by day 1 | 9.3 days | 0 |
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 NO MERCY | CLASSIC | NO LIMIT?
Generated by the game, the map on NO MERCY | CLASSIC | NO LIMIT is procedural, size 4,200 with seed 1813615169. You can view it on RustMaps from this page: the same size and seed produce the same map.
Which settings and rules apply on NO MERCY | CLASSIC | NO LIMIT?
No gather rate appears in the name of NO MERCY | CLASSIC | NO LIMIT. The group limit is 35 players. survival is the game mode, the usual game of gathering, building and raiding. You can raid and fight other players here. The server browser lists it under Modded, where plugins or settings change the game. Oxide is the plugin framework it runs. Vanilla is the label it uses for itself: no changed rates, kits or rules: this is the game as Facepunch ships it. VAC, Valve's anti-cheat, is switched on.
Player counts
What is the current population on NO MERCY | CLASSIC | NO LIMIT?
A reading taken now finds NO MERCY | CLASSIC | NO LIMIT offline; the most recent activity was 3 hours ago. Averaged across the last seven days the population was 1 players, reaching a peak of 5. The busiest point in the last 48 hours came at 17:00 UTC, averaging 1 players.
How does NO MERCY | CLASSIC | NO LIMIT rank against other Rust servers?
NO MERCY | CLASSIC | NO LIMIT is #1,250 in Europe and #3,347 worldwide on the past week's player hours, within the top 15% of ranked servers.
Server details
How reliably does NO MERCY | CLASSIC | NO LIMIT stay online?
As recorded now, NO MERCY | CLASSIC | NO LIMIT is not reachable, the last contact having been 3 hours ago. Going by the uptime figure it reports, it restarted about 1 hours ago. 167 of 168 hours in the last 7 full days were up time, 99% of the total. 18 September 2026 is when Rust Server Trends first recorded it.
Does NO MERCY | CLASSIC | NO LIMIT hold a steady tick rate?
Its average server fps over the last 48 hours was 176, and it never dropped below 126. At its highest, it carried 105,125 entities: buildings, deployables and the world's other contents. Its highest memory use was 3,321 MB. Low fps together with a growing entity count is what players experience as lag.
Which region does NO MERCY | CLASSIC | NO LIMIT run from?
In Europe NO MERCY | CLASSIC | NO LIMIT lists itself, with the tag EU. Rust Server Trends does not look up where the machine stands; it shows where a server says it is. You reach it at 185.189.255.147:35100.
Which Rust version is NO MERCY | CLASSIC | NO LIMIT running?
On Windows, NO MERCY | CLASSIC | NO LIMIT runs Rust network protocol 2635 and build 168909. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on NO MERCY | CLASSIC | NO LIMIT?
On average, the busiest point of its recent wipes drew 4 players. 7 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. In the wipes that didn't hold, the crowd was below half by day 1.
How often does NO MERCY | CLASSIC | NO LIMIT wipe, and on which days?
The prediction follows its tag, because too few of NO MERCY | CLASSIC | NO LIMIT's wipes are on record to confirm its schedule. On Thursday 5 November at 19:00 UTC the force wipe arrives: that is its next wipe, and every Rust server wipes then. It has run its current world for 6 days 23 hours. In its tags it sets out a wipe schedule of every two weeks.
Tags
What do the server tags on NO MERCY | CLASSIC | NO LIMIT mean?
The game's server browser reads the tags NO MERCY | CLASSIC | NO LIMIT publishes: gmrust (Game mode): The game mode is standard Rust survival; mp350 (Max players): Slots: 350; ts35 (Group limit): The team limit is 35; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): Game build: 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): The server has no region code; ^b (Biweekly): A wipe comes every second week; ^v (Vanilla): No changed rates, kits or rules: this is the game as Facepunch ships it; ^o (Oxide): A plugin framework, Oxide (uMod), runs here; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; EU (Europe): The server browser files it under Europe; jp0 (Custom tag): A custom tag, not standard Rust: set by the owner or a plugin. 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 NO MERCY | CLASSIC | NO LIMIT appear?
These Rust Server Trends lists include NO MERCY | CLASSIC | NO LIMIT: EU Rust servers and Modded Rust servers, tracked live. These filters bring it up 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 week.
Connecting
How do you connect to NO MERCY | CLASSIC | NO LIMIT?
To join, enter client.connect 185.189.255.147:35100 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. For the website, go to https://nomercyrust.ru.
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.