RUST METRICSFlight deck · live data
Data live Servers11,636 Players40,778 Populated2,957 Fresh wipes 3 h91 Scan5 min
‹ All servers152.89.199.20:35100
Online Full Queue Fresh wipe Wipe due No query

[NSK] 21.10-28.10|BORDER-RUST|

Online 152.89.199.20:35100 checked 6m ago

monthly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Wed 01:00 UTC
0 50 100 150 200 PAX 0 /200

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 89 SERVER FPS

Server fps

48 h low 44 · below 20 is lag, below 10 is bad
0 50 100 150 200 ENT 111,663 ×1000

Entities

48 h range 109,466–116,510 · memory 3,060 MB
1239 ET SINCE RESTART 03:56

Uptime

3 h 56 min since its last restart, at the last reading
7-day average1peak 8
Rank#2,595top 12%
Last wipe6d agomonthly schedule
Next wipe8d 16hThu 5 Nov, 19:00 UTC FW
Memory3,060MB48 h peak 6 players
REC 1

Players

AveragePeak
0246803:0012:0021:0007:0016:0001:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020003:0012:0021:0007:0016:0001: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 3 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
12k4k6k8k3 Oct8 Oct13 Oct18 Oct23 Oct28 Oct

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

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 8d 16h. The force wipe · high confidence

usual gap6.8 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak6players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC8d 16hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC36d 16hFW

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.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 21 Oct, 04:44 UTC6d ago 8 – running 1
Wed 14 Oct, 05:06 UTC13d ago 6 held half 7 days 0
Wed 7 Oct, 16:03 UTC20d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on [NSK] 21.10-28.10|BORDER-RUST| when wipe day comes?

The busiest point of its recent wipes drew 6 players on average. After the latest wipe, numbers topped out at 7 hours. The crowd stayed above half that peak until the next wipe in 100% of its recent wipes.

When does [NSK] 21.10-28.10|BORDER-RUST| wipe?

With the force wipe, once a month, [NSK] 21.10-28.10|BORDER-RUST| wipes. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 6 days 21 hours ago the current world was made. A monthly wipe schedule is published in its tags.

Tags

Which tags does [NSK] 21.10-28.10|BORDER-RUST| carry, and what do they mean?

Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp200 (Max players): The server holds 200 slots; ts10 (Group limit): You may team up with at most 10; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server; jp0 (Custom tag): A plugin or the owner set this tag; Rust does not ship it from [NSK] 21.10-28.10|BORDER-RUST|. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show [NSK] 21.10-28.10|BORDER-RUST|?

These Rust Metrics lists carry [NSK] 21.10-28.10|BORDER-RUST|: Modded Rust servers, checked 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 week.

Population

Where does [NSK] 21.10-28.10|BORDER-RUST| sit in the rankings?

Ranking for [NSK] 21.10-28.10|BORDER-RUST|: #2,595 on seven-day player hours, top 12% of all ranked servers.

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

Current headcount on [NSK] 21.10-28.10|BORDER-RUST|: 0 players, 200 slots available. Check: players over seven days. Average 1, peak 8. Check: 48-hour peak. 15:00 UTC, 6 players on average.

Server details

Where does [NSK] 21.10-28.10|BORDER-RUST| sit?

No region tag on [NSK] 21.10-28.10|BORDER-RUST|. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 152.89.199.20:35100.

What Rust version is [NSK] 21.10-28.10|BORDER-RUST| on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by [NSK] 21.10-28.10|BORDER-RUST|. To get in, your game needs the same protocol; Steam applies the update.

How does [NSK] 21.10-28.10|BORDER-RUST| perform?

Over the last 48 hours the average was 71 server fps; the floor was 44. Reading: 116,510 entities at the highest. That covers buildings, deployables and everything else. Reading: 5,130 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.

Is [NSK] 21.10-28.10|BORDER-RUST| up, and how often does it stay up?

Check: connection. [NSK] 21.10-28.10|BORDER-RUST| is online at this moment. Check: restart. The uptime it reports puts the last restart about 3 hours ago. Uptime for the last 7 full days: 168 of 168 hours, or 100%. Reading: first seen 3 October 2026, recorded by Rust Metrics.

Settings and map

What settings and rules apply on [NSK] 21.10-28.10|BORDER-RUST|?

Check: gather rate. The name [NSK] 21.10-28.10|BORDER-RUST| does not state one. The cap on groups is 10 players. survival, standard play of gathering, building and raiding — that is the game mode. Combat and raiding against other players are on. The server browser lists it as Modded, where plugins or settings change how the game plays. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.

What map is [NSK] 21.10-28.10|BORDER-RUST| on?

Size 4,500 and seed 108205031: the game generates the procedural map on [NSK] 21.10-28.10|BORDER-RUST| from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Its map carries the name Custom Map.

Join

What do you do to join [NSK] 21.10-28.10|BORDER-RUST|?

To join: start Rust, press F1 and type client.connect 152.89.199.20:35100. Or press Launch Rust here and Steam opens the game and connects you. You can find its website at https://vk.ru/borderrust.

PLACARDS

Server tags

what each one means

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

Game

gmvanilla
Game mode Survival on vanilla settings.
mp200
Max players The server holds 200 slots.
ts10
Group limit You may team up with at most 10.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Game build reading: 168909.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

Other

jp0
Custom tag A plugin or the owner set this tag; Rust does not ship it.

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.