On the class lists: F (39), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak 2
Rank#9,907top 45%
Last wipe26d agono schedule published
Next wipe–too few wipes 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 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,907 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
100/ 100
A+
Runs smoothly: 152 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
45/ 100
D
Slipped a little: down 927 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
No five-minute samples in the last two hours.
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 28 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. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W··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 gap3 daysbetween real wipes
wipe-day peak6players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Fri 2 OctTue 29 Sep
Players each hour, from the hour of the wipe. The latest peaked at 4, 25 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 2 Oct, 20:07 UTC26d ago
4
–
running
0
Tue 29 Sep, 20:21 UTC29d ago
7
halved by day 1
3 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
EU · groups of 300+ · 2x · weekly · 310 on average
348 / 1000
Quick answers
from the figures on this page
About the server
In what location does LRUST | x2 Vanilla+ | BP Share | Biweekly sit?
No region is published for LRUST | x2 Vanilla+ | BP Share | Biweekly. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 149.202.49.90:28015.
Is LRUST | x2 Vanilla+ | BP Share | Biweekly up, and how steady is its uptime?
Right now, LRUST | x2 Vanilla+ | BP Share | Biweekly is online. The uptime it reports puts the last restart at about 6 days 18 hours ago. It was up 92% of the time over the last 7 full days, 155 of 168 hours. It was first seen by Rust Server Score on 28 September 2026.
Does LRUST | x2 Vanilla+ | BP Share | Biweekly perform well?
It averaged 152 server fps over the last 48 hours, with a low of 108. Buildings, deployables and everything else in the world added up to as many as 49,839 entities. At its highest, it used 2,962 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does LRUST | x2 Vanilla+ | BP Share | Biweekly sit?
You will find LRUST | x2 Vanilla+ | BP Share | Biweekly on Rust network protocol 2634 and build 167781, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does LRUST | x2 Vanilla+ | BP Share | Biweekly wipe its map?
LRUST | x2 Vanilla+ | BP Share | Biweekly has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. The world it runs now was created 26 days.
What should you expect from wipe day on LRUST | x2 Vanilla+ | BP Share | Biweekly?
The average peak on its recent wipes was 6 players. The crowd on the latest wipe was largest 25 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 LRUST | x2 Vanilla+ | BP Share | Biweekly sit among Rust servers?
Over the last seven days, LRUST | x2 Vanilla+ | BP Share | Biweekly has #9,907 for player hours, in the top 45% of all ranked servers.
Is LRUST | x2 Vanilla+ | BP Share | Biweekly a busy server?
LRUST | x2 Vanilla+ | BP Share | Biweekly is showing 0 players right now, with 50 slots in total. It peaked at 2 and averaged 0 players over the last seven days.
Tags and filters
How should you read the tags on LRUST | x2 Vanilla+ | BP Share | Biweekly?
The game's browser takes its cue from the tags LRUST | x2 Vanilla+ | BP Share | Biweekly has set: gmrust (Game mode): Survival in the standard Rust style; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show LRUST | x2 Vanilla+ | BP Share | Biweekly?
These Rust Server Score lists count LRUST | x2 Vanilla+ | BP Share | Biweekly among them: 2x Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
Server rules
What settings and rules apply on LRUST | x2 Vanilla+ | BP Share | Biweekly?
Going by its name, LRUST | x2 Vanilla+ | BP Share | Biweekly runs 2x gather. The group limit stays at the game's default of 8 players. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. You are covered by VAC, Valve's anti-cheat.
Which map is in play on LRUST | x2 Vanilla+ | BP Share | Biweekly?
A procedural map of size 3,000 and seed 2142499688, generated by the game, is what LRUST | x2 Vanilla+ | BP Share | Biweekly runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto LRUST | x2 Vanilla+ | BP Share | Biweekly?
Enter client.connect 149.202.49.90:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs167781,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp50
Max playersThe server holds 50 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it under 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).