On the class lists: F (42), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#9,983top 45%
Last wipe6d agoweekly schedule
Next wipe17hFri 30 Oct, 12:13 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
55/ 100
C−
Working its way up from the back of the class: #9,983 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: 120 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
59/ 100
C−
Moving up: up 1,713 places this week.
A term to build on.
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 45% of all ranked servers, and #444 of the trio servers (top 71%). Ranked on player hours over the last seven days.
Attendance: the wipe record
7 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
····W··
···FW··
····W··
····W··
····W··
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Friday 30 October, 12:13 UTC, in 17h.
Every Friday at 12:13 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 2
Coming wipes
17hFri 30 Oct, 12:13 UTC
7d 0hThu 5 Nov, 19:00 UTCFW
7d 17hFri 6 Nov, 12:13 UTC
14d 17hFri 13 Nov, 12:13 UTC
21d 17hFri 20 Nov, 12:13 UTC
28d 17hFri 27 Nov, 12:13 UTC
35d 0hThu 3 Dec, 19:00 UTCFW
35d 17hFri 4 Dec, 12:13 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 12:13 UTC6d ago
2
–
running
0
Fri 16 Oct, 12:14 UTC13d ago
3
halved by day 2
7 days
0
Fri 9 Oct, 12:13 UTC20d ago
0
–
7 days
0
Fri 2 Oct, 12:16 UTC27d ago
0
–
7 days
0
Thu 1 Oct, 18:24 UTCFW28d ago
2
–
0.7 days
0
Fri 25 Sep, 12:16 UTC34d ago
0
–
6.3 days
0
Fri 18 Sep, 12:13 UTC41d ago
0
–
7 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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30?
You won't find a region tag on [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30, but its name indicates Asia. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 160.251.176.12:28015.
How reliable is [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30, and is it up?
You can join now: [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 is online. According to its reported uptime, the last restart was about 4 days 12 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
It averaged 120 server fps over the last 48 hours, with a low of 120. Up to 45,530 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 2,439 MB. When fps is low and entities climb, that is lag to players.
What Rust version is [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 on?
Rust network protocol 2635 and build 168909 on Linux is what [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 runs. Steam updates your game for you, but you need the same protocol to join.
Resets
On what schedule does [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 reset?
Its wipe pattern: [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 wipes every Friday at 12:13 UTC. Friday 30 October at 12:13 UTC is the date set for its next wipe. 6 days 6 hours have passed since this world was made. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30?
Recent wipes have peaked at 2 players on average. Peak numbers came 0 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. Day 2 is when it sank below half in the wipes that did not hold.
Population
Where does [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 sit among Rust servers?
Over the last seven days, [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 has #9,983 for player hours, in the top 45% of all ranked servers. It comes #444 among servers in the trio group.
Is [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 a busy server?
Right now, 0 players are on [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30, which has 50 slots. The seven-day average is 0 players, with a peak of 2.
Lists and filters
How should you read the tags on [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 slots; ts3 (Group limit): No team may go above 3; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every week; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30?
These Rust Server Score lists count [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 among them: 2x Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last week; Gather rate: 2x.
Server rules
How is [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 set up, and what rules does it keep?
Going by its name, [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 runs 2x gather. The cap on group size is 3 players (trio). It runs survival, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30?
The game generates the procedural map on [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30 at size 3,000 with seed 98864358. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
How to join
What is the way to join [JP] NVRIN | 2x Trio | 毎週金曜21時WIPE | 次回 10/30?
To connect, start Rust, press F1, and type client.connect 160.251.176.12:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. You can find its website at https://nvrin.com/rust/.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2635,^w,gmrust,cs168909,ts3,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 slots.
ts3
Group limitNo team may go above 3.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every week.
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.
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 term to build on. Strongest in performance (A+); population is the one to work on (F).