On the class lists: F (43), with population over 48 hours and no performance mark.
Players now0/ 1500% full
7-day average0peak –
Rank#15,353top 69%
Last wipe19d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 150 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,353 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
80/ 100
B+
Mostly smooth: 48 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 1,362 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (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 9 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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
No region is published for RustBandit.co - Vanilla. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 49.12.122.17:28022.
How dependable is RustBandit.co - Vanilla, and is it online at the moment?
The server is up: RustBandit.co - Vanilla is online now. The uptime it reports puts the last restart at about 20 hours ago. For the last 7 full days, it was up 167 of 168 hours, or 99% of the time. The first sighting by Rust Server Score was on 9 October 2026.
How well does RustBandit.co - Vanilla run?
The average over the last 48 hours was 48 server fps, and it never went below 6. Up to 117,758 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 3,559 MB. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is RustBandit.co - Vanilla on?
You will find RustBandit.co - Vanilla on Rust network protocol 2635 and build 168909, hosted on Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does RustBandit.co - Vanilla wipe its map?
The record holds too few of RustBandit.co - Vanilla's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 19 days 13 hours.
Player numbers
Where does RustBandit.co - Vanilla sit among Rust servers?
Over the last seven days, RustBandit.co - Vanilla has #15,353 for player hours, in the top 69% of all ranked servers.
What does the population on RustBandit.co - Vanilla look like?
With 150 slots available, RustBandit.co - Vanilla currently has 0 players. For the last seven days, the average number of players was 0.
Lists and filters
What is meant by the tags on RustBandit.co - Vanilla?
The game's browser takes its cue from the tags RustBandit.co - Vanilla has set: gmrust (Game mode): Rust survival, played by the standard rules; mp150 (Max players): The server holds 150 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. 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 lists and filters on Rust Server Score show RustBandit.co - Vanilla?
These Rust Server Score lists count RustBandit.co - Vanilla among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Vanilla and Modded; Server tag: Vanilla ^v, Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does RustBandit.co - Vanilla enforce, and what are its settings?
Nothing in the name of RustBandit.co - Vanilla states a gather rate. The group limit stays at the game's default of 8 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. By its own description it is vanilla: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
Which map is in play on RustBandit.co - Vanilla?
A procedural map of size 4,500 and seed 1564564, generated by the game, is what RustBandit.co - Vanilla runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to RustBandit.co - Vanilla?
To connect, start Rust, press F1, and type client.connect 49.12.122.17:28022. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp150,ptrak,$r?,v2635,^v,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp150
Max playersThe server holds 150 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
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 uptime (A); population is the one to work on (F).