On the class lists: F (35), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 1
Rank#15,204top 69%
Last wipe1d agoweekly schedule
Next wipe5d 18hMon 2 Nov, 13:33 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 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,204 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 194 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
48/ 100
D
Slipped a little: down 706 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 27 Sep. 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, and #616 of the quad servers (top 75%). Ranked on player hours over the last seven days.
Attendance: the wipe record
9 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
W··F···
W··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 Monday 2 November, 13:33 UTC, in 5d 18h.
Its weekly schedule tag · low confidence
usual gap3.4 daysbetween real wipes
on rhythm50%of its recent wipes
wipe-day peak0players, last three wipes
crowd held0%else halves by day 1
Coming wipes
5d 18hMon 2 Nov, 13:33 UTC
9d 0hThu 5 Nov, 19:00 UTCFW
12d 18hMon 9 Nov, 13:33 UTC
19d 18hMon 16 Nov, 13:33 UTC
26d 18hMon 23 Nov, 13:33 UTC
33d 18hMon 30 Nov, 13:33 UTC
37d 0hThu 3 Dec, 19:00 UTCFW
40d 18hMon 7 Dec, 13:33 UTC
The first 48 hours of its last wipes
Mon 19 OctThu 15 OctMon 12 Oct
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
Mon 26 Oct, 13:33 UTC1d ago
–
–
running
0
Mon 19 Oct, 13:31 UTC8d ago
0
–
7 days
0
Thu 15 Oct, 13:32 UTC12d ago
1
halved by day 1
4 days
0
Mon 12 Oct, 13:31 UTC15d ago
0
–
3 days
0
Thu 8 Oct, 13:32 UTC19d ago
1
halved by day 1
4 days
0
Mon 5 Oct, 13:31 UTC22d ago
0
–
3 days
0
Thu 1 Oct, 17:58 UTCFW26d ago
1
halved by day 1
3.8 days
0
Mon 28 Sep, 18:11 UTC29d ago
5
halved by day 1
3 days
0
Sun 27 Sep, 20:56 UTC29d ago
5
–
0.9 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
Which region is [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu based in?
No region is published for [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 84.13.141.108:28015.
How reliable is [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu, and is it up?
The server is up: [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu is online now. The uptime it reports puts the last restart at about 27 hours ago. It was up 79% of the time over the last 7 full days, 133 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
How well does [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu run?
It averaged 194 server fps over the last 48 hours, with a low of 163. Buildings, deployables and everything else in the world added up to as many as 41,268 entities. Up to 1,887 MB of memory was used. When fps is low and entities climb, that is lag to players.
On what Rust version does [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu sit?
Rust network protocol 2635 and build 167781 on Linux is what [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu wipe, and how often?
Too few wipes on [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu are recorded to confirm the schedule, so its tag guides the prediction. It is due to wipe next on Monday 2 November at 13:33 UTC. It has been running its current world for 29 hours. Wipes are scheduled weekly, according to its tags.
What happens on [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu when wipe day arrives?
The average peak on its recent wipes was 0 players. 0 hours after the latest wipe began, the crowd hit its peak. Half the peak held until the next wipe in 0% of its recent wipes. In the other wipes it slipped under half by day 1.
Player count
Where does [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu sit among Rust servers?
In the top 69% of all ranked servers, [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu sits at #15,204 for player hours over the last seven days. It comes #616 among servers in the quad group.
Is [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu a busy server?
Right now, 0 players are on [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu, which has 100 slots. Averaging 0 players over seven days, it peaked at 1. Over the last 48 hours, the peak hour was 14:00 UTC, averaging 0 players.
Tags
How should you read the tags on [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu?
The game's browser takes its cue from the tags [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): The server holds 100 slots; ts4 (Group limit): No team may go above 4; v2635 (Protocol): Join only if your game runs protocol 2635; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^w (Weekly): Wipes come once a week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; WA (West Asia): In the server browser it appears under West Asia. 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 [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu?
These Rust Server Score lists count [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu among them: 2x Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Weekly; Last wipe: In the last 3 days; Gather rate: 2x.
Map and rules
How is [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu set up, and what rules does it keep?
Going by its name, [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu runs 2x gather. The cap on group size is 4 players (quad). survival is the mode here, 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. The server runs Valve's anti-cheat, VAC.
A procedural map of size 2,650 and seed 66666666, generated by the game, is what [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How should you connect to [ME] Oasis 2x | Quad | Shared BPs | Vanilla+ | Mon/Thu?
To connect, start Rust, press F1, and type client.connect 84.13.141.108:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,WA,gmrust,cs167781,ts4,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersThe server holds 100 slots.
ts4
Group limitNo team may go above 4.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
Region
WA
West AsiaIn the server browser it appears under West Asia.
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).