Offline EU 185.189.255.147:35100 checked 6h ago
NO MERCY | CLASSIC | NO LIMIT
Connect
srv = rust.server("185.189.255.147:35110")
print(srv.connect_command)Right now
srv.summary()display(Image(srv.banner))
Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 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 tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 8h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 8h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 20d 21h | Thu 19 Nov, 07:22 UTC | wipe |
| 2 | 35d 8h | Thu 3 Dec, 19:00 UTC | FW force wipe |
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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 22 Oct, 07:22 UTC7d ago | 5 | NaN | running | 0 |
| 1 | Mon 19 Oct, 02:09 UTC10d ago | 3 | halved by day 1 | 3.2 days | 0 |
| 2 | Sat 17 Oct, 20:20 UTC11d ago | 3 | NaN | 1.2 days | 0 |
| 3 | Thu 8 Oct, 12:02 UTC20d 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.
display(srv.map, srv.info())Map
4200 · seed 1813615169
- map
- Procedural Map
- size
- 4200
- seed
- 1813615169
Server
srv.info()- address
- 185.189.255.147:35100
- region
- EU
- max players
- 350
- group limit
- 35 max
- wipe schedule
- biweekly
- last wipe
- 22 Oct 2026, 07:22 UTC
- hostname
- –
- first seen
- 18 Sep 2026
About this server · in its own words
print(srv.description)Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | СЛАБЫЕ РЫЦАРИ |Vanilla+|Events|FPS+|26.10 | EU · groups of 50+ · biweekly · 9 on average | 9/200 |
| 1 | RUST ACADEMY #2 - Modded / РЕЙДЫ ПО СОГЛАСИЮ | EU · groups of 8+ · biweekly · 8 on average | 5/200 |
| 2 | [ESP][PVE] PACIFIC WORLD (WIPED 15/10/2026) | EU · groups of 16+ · biweekly · 4 on average | 2/50 |
| 3 | РЕЛАКС #2 Х2|Для новичков| No Limit | EU · groups of 10+ · biweekly · 3 on average | 2/200 |
| 4 | #1 [RU] РУССКИЙ КЛАССИКА R7ZONE.RU | EU · groups of 10+ · biweekly · 3 on average | 0/300 |
| 5 | PurrRust|РУССКИЙ ДЛЯ НОВИЧКОВ|Vanilla2x|27.10 | EU · groups of 8+ · biweekly · 2 on average | 3/80 |
Quick answers
From the figures on this page.
Population
What position does NO MERCY | CLASSIC | NO LIMIT take in the server rankings?
On seven-day player hours NO MERCY | CLASSIC | NO LIMIT is #3,364 overall and #1,258 in Europe, inside the top 15% of all ranked servers.
What population does NO MERCY | CLASSIC | NO LIMIT carry?
Offline now for NO MERCY | CLASSIC | NO LIMIT, with the last sample 6 hours ago. Over the last seven days it averaged 1 players and peaked at 5. Averaged by hour over 48 hours, 17:00 UTC is the busiest, at 1 players.
About the server
How smoothly does NO MERCY | CLASSIC | NO LIMIT run?
Server fps over the last 48 hours averages 176; the floor is 126. Entity numbers reached 104,819, and that includes buildings, deployables and the rest. Memory peaked at 3,321 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on NO MERCY | CLASSIC | NO LIMIT?
Rust network protocol 2635 and build 168909 on Windows is what NO MERCY | CLASSIC | NO LIMIT runs. Steam updates your game for you, but the protocol must match to join.
Is NO MERCY | CLASSIC | NO LIMIT up, and what does its uptime show?
Offline now for NO MERCY | CLASSIC | NO LIMIT, last seen 6 hours ago. The uptime it reports puts the last restart about 1 hours ago. Uptime of 99% across the last 7 full days: 167 hours of 168. Its earliest recorded date in Rust Data is 18 September 2026.
In which location is NO MERCY | CLASSIC | NO LIMIT hosted?
With its EU tag, NO MERCY | CLASSIC | NO LIMIT lists itself in Europe. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 185.189.255.147:35100 is its address.
Map and rules
Which rules apply on NO MERCY | CLASSIC | NO LIMIT, and what settings?
You will not find a gather rate in the string NO MERCY | CLASSIC | NO LIMIT. 35 players is the maximum per group. survival is the game mode here, and the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Its own label is vanilla: untouched settings: rates, kits and rules as shipped. VAC, Valve's anti-cheat, is enabled.
Which map has NO MERCY | CLASSIC | NO LIMIT selected?
Size 4,200, seed 1813615169: the procedural map on NO MERCY | CLASSIC | NO LIMIT, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does NO MERCY | CLASSIC | NO LIMIT wipe, and how often?
Too few wipes are on record for NO MERCY | CLASSIC | NO LIMIT to confirm its schedule, so the tag drives the prediction. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. This world was created 7 days 2 hours ago. A fortnightly wipe schedule is published in its tags.
On NO MERCY | CLASSIC | NO LIMIT, what happens on wipe day?
The average peak over recent wipes is 4 players. Peak population on the latest wipe came 7 hours in. Recent wipes kept the crowd above half the peak until the next wipe 0% of the time. Otherwise the crowd fell below half by day 1.
Tags, lists
Which lists on Rust Data hold NO MERCY | CLASSIC | NO LIMIT, and which filters?
The Rust Data lists that NO MERCY | CLASSIC | NO LIMIT fits are: EU Rust servers and Modded Rust servers. 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 2 weeks.
How should you read the server tags on NO MERCY | CLASSIC | NO LIMIT?
Read by the game's server browser, the tags NO MERCY | CLASSIC | NO LIMIT publishes are: gmrust (Game mode): Rust survival in its standard form; mp350 (Max players): Slot count: 350; ts35 (Group limit): No team may exceed 35; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^b (Biweekly): Two weeks between wipes; ^v (Vanilla): Untouched settings: rates, kits and rules as shipped; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings; EU (Europe): Europe is its listing in the server browser; jp0 (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to NO MERCY | CLASSIC | NO LIMIT?
In Rust, F1 opens the console: type client.connect 185.189.255.147:35100. Launch Rust on this page does the same by opening the game through Steam and connecting. https://nomercyrust.ru is the website recorded for it.