On the class lists: C+ (67), with population over 48 hours and no performance mark.
Players now1/ 2000% full
7-day average1peak 8
Rank#2,570top 12%
Last wipe6d agomonthly schedule
Next wipe8d 22hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
1/ 100
F
A quiet classroom so far: 1 of 200 on average. Plenty of space to grow.
Standingrank on player hours
88/ 100
A−
Holds a respectable place: #2,570 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 69 server fps on average.
Wipeskeeping the crowd after a wipe
100/ 100
A+
Holds its players well after a wipe: 100% of wipes kept half their crowd.
Momentumrank now against a week ago
51/ 100
D
Moving up: up 31 places this week.
A steady term.
Strongest in performance (A+); population is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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
RankRank in region
Top 12% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
··W····
··W····
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 8d 22h.
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
8d 22hThu 5 Nov, 19:00 UTCFW
36d 22hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Wed 21 OctWed 14 OctWed 7 Oct
Players each hour, from the hour of the wipe. The latest peaked at 8, 7 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is [NSK] 21.10-29.10|BORDER-RUST| based in?
[NSK] 21.10-29.10|BORDER-RUST| leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 152.89.199.20:35100.
How reliable is [NSK] 21.10-29.10|BORDER-RUST|, and is it up?
You can join now: [NSK] 21.10-29.10|BORDER-RUST| is online. About 2 days 20 hours ago, it restarted, based on the uptime it reports. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 3 October 2026.
Does [NSK] 21.10-29.10|BORDER-RUST| perform well?
It never fell below 44 server fps in the last 48 hours, averaging 69. Buildings, deployables and everything else in the world added up to as many as 114,619 entities. At its highest, it used 5,130 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
On what Rust version does [NSK] 21.10-29.10|BORDER-RUST| sit?
You will find [NSK] 21.10-29.10|BORDER-RUST| on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
On what schedule does [NSK] 21.10-29.10|BORDER-RUST| reset?
Once a month, [NSK] 21.10-29.10|BORDER-RUST| wipes with the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 6 days 15 hours have passed since this world was made. Its tags list a monthly wipe schedule.
What should you expect from wipe day on [NSK] 21.10-29.10|BORDER-RUST|?
Across its recent wipes, the busiest moments averaged 6 players. Peak numbers came 7 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 100% of its recent wipes.
Population
Where does [NSK] 21.10-29.10|BORDER-RUST| sit among Rust servers?
In the top 12% of all ranked servers, [NSK] 21.10-29.10|BORDER-RUST| sits at #2,570 for player hours over the last seven days.
How many players does [NSK] 21.10-29.10|BORDER-RUST| usually have?
[NSK] 21.10-29.10|BORDER-RUST| is showing 1 players right now, with 200 slots in total. Averaging 1 players over seven days, it peaked at 8. The busiest time in the last 48 hours was 15:00 UTC, with an average of 6 players.
Lists and filters
What is meant by the tags on [NSK] 21.10-29.10|BORDER-RUST|?
You'll see [NSK] 21.10-29.10|BORDER-RUST| tagged with gmvanilla (Game mode): Survival, vanilla style; mp200 (Max players): 200 slots are available; ts10 (Group limit): No team may go above 10; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; jp0 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature [NSK] 21.10-29.10|BORDER-RUST|?
These Rust Server Score lists count [NSK] 21.10-29.10|BORDER-RUST| among them: Modded Rust servers, graded. 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.
Map and rules
What settings and rules apply on [NSK] 21.10-29.10|BORDER-RUST|?
Nothing in the name of [NSK] 21.10-29.10|BORDER-RUST| states a gather rate. A group here can reach 10 players. You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on [NSK] 21.10-29.10|BORDER-RUST|?
[NSK] 21.10-29.10|BORDER-RUST| runs a game-generated procedural map at size 4,500, seed 108205031. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. You will see the map name listed as: Custom Map.
Getting in
How do you get onto [NSK] 21.10-29.10|BORDER-RUST|?
Enter client.connect 152.89.199.20:35100 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://vk.ru/borderrust.
Server tags
what each one means
Published asmp200,ptrak,jp0,$r?,v2635,^m,gmvanilla,cs168909,ts10,^o^z
Game
gmvanilla
Game modeSurvival, vanilla style.
mp200
Max players200 slots are available.
ts10
Group limitNo team may go above 10.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Other
jp0
Custom tagNot one of Rust's standard tags, it comes from a plugin or the owner.
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.
A steady term. Strongest in performance (A+); population is the one to work on (F).