On the class lists: F (40), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 1
Rank#7,784top 35% · #1140 in NA
Last wipe22h agobiweekly schedule
Next wipe7d 15hThu 5 Nov, 19:00 UTC FW
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
65/ 100
C+
Working its way up from the back of the class: #7,784 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
97/ 100
A+
Runs smoothly: 58 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
40/ 100
F
Slipped a little: down 1,634 places this week. Nothing a good wipe can't fix.
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.
AveragePeakWipe
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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 35% of all ranked servers, top 61% in NA. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
····W··
···W···
···W···
·······
··W·
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 5 November, 19:00 UTC, in 7d 15h.
The force wipe · high confidence
usual gap7 daysbetween real wipes
on rhythm20%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
Coming wipes
7d 15hThu 5 Nov, 19:00 UTCFW
13d 1hWed 11 Nov, 05:05 UTC
27d 1hWed 25 Nov, 05:05 UTC
35d 15hThu 3 Dec, 19:00 UTCFW
41d 1hWed 9 Dec, 05:05 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 8 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 28 Oct, 05:05 UTC22h ago
–
–
running
0
Thu 15 Oct, 00:07 UTC14d ago
1
halved by day 1
13.2 days
1
Thu 8 Oct, 00:07 UTC21d ago
2
halved by day 4
7 days
0
Fri 2 Oct, 18:35 UTC26d ago
1
halved by day 1
5.2 days
0
Fri 2 Oct, 06:08 UTC26d ago
1
–
0.5 days
0
Thu 24 Sep, 00:07 UTC35d ago
0
–
8.3 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
In what location does [US] Mello Rust | Vanilla Bi-weekly sit?
You'll find [US] Mello Rust | Vanilla Bi-weekly in North America, tagged NA, with region code us5. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 91.229.114.140:28015.
How reliable is [US] Mello Rust | Vanilla Bi-weekly, and is it up?
The server is up: [US] Mello Rust | Vanilla Bi-weekly is online now. According to its reported uptime, the last restart was 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 13 September 2026.
Does [US] Mello Rust | Vanilla Bi-weekly perform well?
It averaged 58 server fps over the last 48 hours, with a low of 20. Up to 88,656 entities were in the world, covering buildings, deployables and the rest. Up to 2,900 MB of memory was used. Players feel lag when fps drops and entities pile up.
On what Rust version does [US] Mello Rust | Vanilla Bi-weekly sit?
Rust network protocol 2635 and build 168909 on Linux is what [US] Mello Rust | Vanilla Bi-weekly runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does [US] Mello Rust | Vanilla Bi-weekly reset?
Its tag sets the prediction, as the record holds too few of [US] Mello Rust | Vanilla Bi-weekly's wipes to confirm its schedule. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 22 hours have passed since this world was made. A fortnightly wipe schedule appears in its tags.
What happens on [US] Mello Rust | Vanilla Bi-weekly when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 0 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. In the other wipes it slipped under half by day 1.
Player numbers
Where does [US] Mello Rust | Vanilla Bi-weekly sit among Rust servers?
In North America, [US] Mello Rust | Vanilla Bi-weekly is #1,140, and overall it is #7,784 on player hours over the last seven days, in the top 35% of all ranked servers.
What does the population on [US] Mello Rust | Vanilla Bi-weekly look like?
[US] Mello Rust | Vanilla Bi-weekly is showing 0 players right now, with 50 slots in total. It peaked at 1 and averaged 0 players over the last seven days. The highest average in the last 48 hours came at 22:00 UTC, with 1 players.
Lists and filters
How should you read the tags on [US] Mello Rust | Vanilla Bi-weekly?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $rus5 (Region code): us5 is the region code this server uses; ^b (Biweekly): Every two weeks it wipes; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon; NA (North America): You will find it under North America in the browser; sc1 (Custom tag): Not one of Rust's standard tags, it comes from a plugin or the owner are the tags [US] Mello Rust | Vanilla Bi-weekly publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does [US] Mello Rust | Vanilla Bi-weekly appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [US] Mello Rust | Vanilla Bi-weekly among them: Modded Rust servers, graded and North America Rust servers, graded. It shows under the following filters on the server list: Region: North America; Type: Vanilla and Modded; Server tag: Biweekly ^b, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
Server rules
What settings and rules apply on [US] Mello Rust | Vanilla Bi-weekly?
The name of [US] Mello Rust | Vanilla Bi-weekly gives no gather rate. The group limit stays at the game's default of 8 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. The plugin count runs to Carbon. By its own description it is vanilla: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [US] Mello Rust | Vanilla Bi-weekly uses?
[US] Mello Rust | Vanilla Bi-weekly runs a game-generated procedural map at size 3,500, seed 1730058098. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How should you connect to [US] Mello Rust | Vanilla Bi-weekly?
To connect, start Rust, press F1, and type client.connect 91.229.114.140:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$rus5,v2635,^z,^y,^b,^v,NA,gmrust,cs168909,sc1,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$rus5
Region codeus5 is the region code this server uses.
Wipe schedule
^b
BiweeklyEvery two weeks it wipes.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonThe plugin framework in use is Carbon.
Region
NA
North AmericaYou will find it under North America in the browser.
Other
sc1
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 term to build on. Strongest in performance (A+); population is the one to work on (F).