Rust Server TrendsSeismic network · station log
Recording Stations11,649 Players42,065 Active2,888 Wipes · 3 h106 48 h

Station XX-3133 · recording

[NSK] 28.10-05.11|BORDER-RUST|

Online 152.89.199.20:35100 checked 12m ago

monthly wipes moddedoxide
Connect
Players now
0/ 200
0% full
Motion · 24 h
M0.0steady
+0 players on the day
7-day average
1
peak 6
Rank
#3,133
top 14%
Last wipe
1d ago
monthly schedule
Next wipe
5d 0h
Wed 4 Nov, 05:04 UTC
Seismic record · station XX-3133 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
Now
0of 200 slots
Motion · 24 h
M0.0steady+0 players
Sharpest hour
+2into Wed 06:00 UTC
Peak · 48 h
3most players in any hour
Events picked
1wipe on this record, in red
Channel 1 · calibrated

Players

AveragePeakWipe
0123405:0014:0000:0008:0017:0002:00Wiped Wed 28 Oct, 05:04 UTCWIPE

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

Server fpsWipe
025507510005:0014:0000:0008:0017:0002:00Wiped Wed 28 Oct, 05:04 UTCWIPE

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
12k4k6k8k3 Oct8 Oct14 Oct19 Oct25 Oct30 Oct

Top 14% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

fixed weekdays

Next wipe Wednesday 4 November, 05:04 UTC, in 5d 0h. Every Wednesday at 05:04 UTC · medium confidence

usual gap
7 daysbetween real wipes
on rhythm
75%of its recent wipes
wipe-day peak
6players, last three wipes
crowd held
67%else halves by day 2

Coming wipes

  1. 5d 0hWed 4 Nov, 05:04 UTC
  2. 6d 14hThu 5 Nov, 19:00 UTCFW
  3. 12d 0hWed 11 Nov, 05:04 UTC
  4. 19d 0hWed 18 Nov, 05:04 UTC
  5. 26d 0hWed 25 Nov, 05:04 UTC
  6. 33d 0hWed 2 Dec, 05:04 UTC
  7. 34d 14hThu 3 Dec, 19:00 UTCFW
  8. 40d 0hWed 9 Dec, 05:04 UTC

The first 48 hours of its last wipes

Wed 21 OctWed 14 OctWed 7 Oct
02468+0h+9h+19h+28h+38h+47h

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

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
Wed 28 Oct, 05:04 UTC1d ago – – – – running 0
Wed 21 Oct, 04:44 UTC8d ago M0.8rising 8 halved by day 2 7 days 1
Wed 14 Oct, 05:06 UTC15d ago M0.8rising 6 held half 7 days 0
Wed 7 Oct, 16:03 UTC22d ago M0.5rising 4 held half 6.5 days 1

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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 97 on average
7/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 94 on average
25/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 85 on average
1/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 EU · groups of 16+ · monthly · 80 on average
14/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 EU · groups of 16+ · monthly · 77 on average
22/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 29.10 EU · groups of 16+ · monthly · 74 on average
60/ 1000
Readings, in words

Quick answers

from the figures on this page

Rules and settings

Which map is running on [NSK] 28.10-05.11|BORDER-RUST|?

The procedural map on [NSK] 28.10-05.11|BORDER-RUST| is size 5,000 with seed 108205031, generated by the game. From this page you can look at it on RustMaps, since the same size and seed give the same map. The name of its map is Custom Map.

Which settings and rules apply on [NSK] 28.10-05.11|BORDER-RUST|?

You will find no gather rate in the name of [NSK] 28.10-05.11|BORDER-RUST|. Up to 10 players can be in a group. It plays in survival mode, standard play, with gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Oxide is the plugin framework it runs. The server has VAC on, Valve's anti-cheat.

Population

What is the current population on [NSK] 28.10-05.11|BORDER-RUST|?

At this moment, [NSK] 28.10-05.11|BORDER-RUST| records 0 players across 200 slots. Averaged across the last seven days the population was 1 players, reaching a peak of 6. The busiest point in the last 48 hours came at 06:00 UTC, averaging 3 players.

How does [NSK] 28.10-05.11|BORDER-RUST| rank against other Rust servers?

On player hours for the past week, [NSK] 28.10-05.11|BORDER-RUST| sits at #3,133, which puts it inside the top 14% of every ranked server.

Server facts

How reliably does [NSK] 28.10-05.11|BORDER-RUST| stay online?

As recorded now, [NSK] 28.10-05.11|BORDER-RUST| is running. Going by the uptime figure it reports, it restarted about 4 hours ago. Of the 168 hours in the last 7 full days, it was up for 167, or 99% of the time. On 3 October 2026 it was recorded for the first time by Rust Server Trends.

Does [NSK] 28.10-05.11|BORDER-RUST| hold a steady tick rate?

Its average server fps over the last 48 hours was 58, and it never dropped below 17. The world held up to 143,117 entities at its peak, buildings and deployables included. Memory use peaked at 4,134 MB. Lag, as players feel it, comes from fps dropping and the entity count climbing.

Which region does [NSK] 28.10-05.11|BORDER-RUST| run from?

No region is published by [NSK] 28.10-05.11|BORDER-RUST|. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. The address it publishes is 152.89.199.20:35100.

What build of Rust does [NSK] 28.10-05.11|BORDER-RUST| use?

[NSK] 28.10-05.11|BORDER-RUST| is running Rust network protocol 2635 and build 168909 on a machine with Windows. 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 [NSK] 28.10-05.11|BORDER-RUST|?

On average, the busiest point of its recent wipes drew 6 players. 7 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 67% of its recent wipes. It fell under half by day 2 in the wipes where it didn't hold.

On what timetable does [NSK] 28.10-05.11|BORDER-RUST| run its wipes?

every Wednesday at 05:04 UTC is how [NSK] 28.10-05.11|BORDER-RUST| wipes. Wednesday 4 November at 05:04 UTC is when its next wipe is due. 47 hours is how long the current world has been running. A monthly wipe schedule is published in its tags.

Server tags

What do the server tags on [NSK] 28.10-05.11|BORDER-RUST| mean?

These are the tags [NSK] 28.10-05.11|BORDER-RUST| publishes for the browser to read: gmvanilla (Game mode): Survival in vanilla mode; mp200 (Max players): 200 slots are available; ts10 (Group limit): The team limit is 10; v2635 (Protocol): Your game needs to be on protocol 2635 to join; cs168909 (Build): The game build is 168909; ptrak (Networking): Network layer: RakNet, the standard for Rust; $r? (Region code): No region code is set for this server; ^m (Monthly): It wipes monthly, together with the Facepunch force wipe; ^o (Oxide): Oxide (uMod) is the plugin framework running here; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; jp0 (Custom tag): The owner or a plugin set this tag, and it's not one of Rust's standard tags. 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 [NSK] 28.10-05.11|BORDER-RUST| appear?

The Rust Server Trends lists that take in [NSK] 28.10-05.11|BORDER-RUST| are: Modded Rust servers, tracked live. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly; Last wipe: In the last 3 days.

Connecting

How do you connect to [NSK] 28.10-05.11|BORDER-RUST|?

You can connect by pressing F1 in Rust and typing client.connect 152.89.199.20:35100 into the console. Another route is to use Launch Rust and join from this page, which opens the game through Steam and connects you. For the website, go to https://vk.ru/borderrust.

Instrument codes

Server tags

what each one means

Published as mp200,ptrak,jp0,$r?,v2635,^m,gmvanilla,cs168909,ts10,^o^z

Game

gmvanilla
Game mode Survival in vanilla mode.
mp200
Max players 200 slots are available.
ts10
Group limit The team limit is 10.
v2635
Protocol Your game needs to be on protocol 2635 to join.
cs168909
Build The game build is 168909.
ptrak
Networking Network layer: RakNet, the standard for Rust.
$r?
Region code No region code is set for this server.

Wipe schedule

^m
Monthly It wipes monthly, together with the Facepunch force wipe.

Mods and access

^o
Oxide Oxide (uMod) is the plugin framework running here.
^z
Modded Plugins or settings alter the game, so it's listed under Modded.

Other

jp0
Custom tag The owner or a plugin set this tag, and it's not one of Rust's standard tags.

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.

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.