Online 152.89.199.20:35100 checked 3h ago
[NSK] 28.10-05.11|BORDER-RUST|
Connect
srv = rust.server("152.89.199.20:35110")
print(srv.connect_command)
Right now
srv.summary()
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 3 Oct. 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 best
Top 13% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · fixed weekdays
srv.wipe_schedule()
Next wipe Wednesday 4 November, 05:04 UTC, in 6d 9h. # Every Wednesday at 05:04 UTC · medium confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 6d 9h | Wed 4 Nov, 05:04 UTC | wipe |
| 1 | 7d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 2 | 13d 9h | Wed 11 Nov, 05:04 UTC | wipe |
| 3 | 20d 9h | Wed 18 Nov, 05:04 UTC | wipe |
| 4 | 27d 9h | Wed 25 Nov, 05:04 UTC | wipe |
| 5 | 34d 9h | Wed 2 Dec, 05:04 UTC | wipe |
| 6 | 35d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 7 | 41d 9h | Wed 9 Dec, 05:04 UTC | wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 8, 7 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Wed 28 Oct, 05:04 UTC14h ago | NaN | NaN | running | 0 |
| 1 | Wed 21 Oct, 04:44 UTC7d ago | 8 | halved by day 2 | 7 days | 1 |
| 2 | Wed 14 Oct, 05:06 UTC14d ago | 6 | held half | 7 days | 0 |
| 3 | Wed 7 Oct, 16:03 UTC21d ago | 4 | held half | 6.5 days | 1 |
# 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())
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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 90 on average | 126/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 50/1000 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 74 on average | 453/700 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 67 on average | 178/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 | EU · groups of 16+ · monthly · 67 on average | 24/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 58 on average | 580/1000 |
Quick answers
From the figures on this page.
Population
What position does [NSK] 28.10-05.11|BORDER-RUST| take in the server rankings?
Rank #2,841 on seven-day player hours for [NSK] 28.10-05.11|BORDER-RUST|, within the top 13% of all ranked servers.
How many players does [NSK] 28.10-05.11|BORDER-RUST| hold at once?
The sample now reads 2 players for [NSK] 28.10-05.11|BORDER-RUST|, out of 200 slots. Over the last seven days it averaged 1 players and peaked at 6. Peak hour in the last 48 hours: 15:00 UTC, mean 6 players.
Server facts
How smoothly does [NSK] 28.10-05.11|BORDER-RUST| run?
The 48-hour average is 69 server fps, with a low of 45. Entity numbers reached 141,872, and that includes buildings, deployables and the rest. Memory peaked at 5,130 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does [NSK] 28.10-05.11|BORDER-RUST| run?
The build is Rust network protocol 2635 and build 168909 on Windows, run by [NSK] 28.10-05.11|BORDER-RUST|. Steam updates your game for you, but the protocol must match to join.
How reliable is [NSK] 28.10-05.11|BORDER-RUST|, and is it up?
The current sample puts [NSK] 28.10-05.11|BORDER-RUST| online. The uptime it reports puts the last restart about 5 hours ago. Over the last 7 full days the hours up number 168 of 168, 100%. The first row Rust Data holds for it is dated 3 October 2026.
Which location does [NSK] 28.10-05.11|BORDER-RUST| run from?
There is no region published for [NSK] 28.10-05.11|BORDER-RUST|. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 152.89.199.20:35100.
Rules, settings, map
What rules and settings are recorded for [NSK] 28.10-05.11|BORDER-RUST|?
The name [NSK] 28.10-05.11|BORDER-RUST| carries no gather rate. 10 players is the maximum per group. Game mode survival, with this note: the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC is running: Valve's anti-cheat is on.
Which map has [NSK] 28.10-05.11|BORDER-RUST| selected?
The game generates the map on [NSK] 28.10-05.11|BORDER-RUST|: procedural, size 5,000, seed 108205031. Size and seed fix the map, so RustMaps can show it, linked from this page. Recorded under map name: Custom Map.
Wipe schedule
On what schedule does [NSK] 28.10-05.11|BORDER-RUST| wipe?
The wipe rhythm for [NSK] 28.10-05.11|BORDER-RUST| is every Wednesday at 05:04 UTC. Wednesday 4 November at 05:04 UTC is when the next wipe is due. A new world was started 14 hours ago, and that is the one in play. A monthly wipe schedule is published in its tags.
On [NSK] 28.10-05.11|BORDER-RUST|, what happens on wipe day?
The average peak over recent wipes is 6 players. 7 hours after the latest wipe, the crowd reached its peak. Recent wipes kept the crowd above half the peak until the next wipe 67% of the time. The drop under half arrived by day 2 in the other cases.
Lists and tags
Which Rust Data filters and lists contain [NSK] 28.10-05.11|BORDER-RUST|?
These Rust Data lists include [NSK] 28.10-05.11|BORDER-RUST|: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 24 hours.
How should you read the server tags on [NSK] 28.10-05.11|BORDER-RUST|?
The game's server browser reads these tags from [NSK] 28.10-05.11|BORDER-RUST|: gmvanilla (Game mode): Game mode: vanilla survival; mp200 (Max players): Slot count: 200; ts10 (Group limit): Team size tops out at 10; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Modded listing: the game is changed by plugins or settings; jp0 (Custom tag): This tag comes from the owner or a plugin, not from Rust itself. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
How can I connect to [NSK] 28.10-05.11|BORDER-RUST|?
In Rust, F1 opens the console: type client.connect 152.89.199.20:35100. Launch Rust on this page does the same by opening the game through Steam and connecting. You will find its website at https://vk.ru/borderrust.
