Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 347 places this week. Nothing a good wipe can't fix.
A term to build on.
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
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····W·
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
usual gap0.4 daysbetween real wipes
wipe-day peak0players, last three wipes
The first 48 hours of its last wipes
Sat 19 SepSat 19 Sep
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 19 Sep, 20:22 UTC39d ago
0
–
running
0
Sat 19 Sep, 10:30 UTC40d ago
0
–
0.4 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
You'll find no region listed by Wipeborn RustNav tier2. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 109.38.151.222:28215.
How dependable is Wipeborn RustNav tier2, and is it online at the moment?
At this moment, Wipeborn RustNav tier2 is offline; the last time it was seen was 39 days 7 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 18 September 2026.
Which Rust version is Wipeborn RustNav tier2 running?
Rust network protocol 2633 and build 164530 on Linux is what Wipeborn RustNav tier2 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does Wipeborn RustNav tier2 reset?
There are too few wipes on record for Wipeborn RustNav tier2 to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 39 days 21 hours.
What should you expect from wipe day on Wipeborn RustNav tier2?
The average peak on its recent wipes was 0 players. 0 hours after the latest wipe began, the crowd hit its peak.
Player numbers
Where does Wipeborn RustNav tier2 place in the wider field of Rust servers?
Over the last seven days, Wipeborn RustNav tier2 has #15,481 for player hours, in the top – of all ranked servers.
What does the population on Wipeborn RustNav tier2 look like?
It has been 39 days 7 hours since Wipeborn RustNav tier2 was last seen, and it is offline right now.
Lists and filters
What is meant by the tags on Wipeborn RustNav tier2?
The game's browser takes its cue from the tags Wipeborn RustNav tier2 has set: gmrust (Game mode): Survival in the standard Rust style; mp8 (Max players): 8 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): Join only if your game runs protocol 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature Wipeborn RustNav tier2?
These Rust Server Score lists count Wipeborn RustNav tier2 among them: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
What settings and rules apply on Wipeborn RustNav tier2?
The name of Wipeborn RustNav tier2 gives no gather rate. With no change from the game default, groups take up to 8 players. It runs survival, gather and build and raid: the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. The server runs Valve's anti-cheat, VAC.
Which map is in play on Wipeborn RustNav tier2?
Wipeborn RustNav tier2 runs a procedural map, which the game generates.
Connecting
How should you connect to Wipeborn RustNav tier2?
To connect, start Rust, press F1, and type client.connect 109.38.151.222:28215. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp8,ptrak,$r?,v2633,gmrust,cs164530,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp8
Max players8 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolJoin only if your game runs protocol 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework here.
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.