Working its way up from the back of the class: #15,478 on player hours.
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
41/ 100
F
Slipped a little: down 2,714 places this week. Nothing a good wipe can't fix.
A term to build on.
Even marks across the subjects, from F to 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.
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
Top 68% 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
Which region is [DEV-OXIDE] Maestrea plugin test based in?
You'll find no region listed by [DEV-OXIDE] Maestrea plugin test. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 98.128.242.189:28025.
Is [DEV-OXIDE] Maestrea plugin test up, and how steady is its uptime?
The server is down: [DEV-OXIDE] Maestrea plugin test is offline now, with the last sighting 38 days 9 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 19 September 2026.
On what Rust version does [DEV-OXIDE] Maestrea plugin test sit?
Rust network protocol 2633 and build 164530 on Linux is what [DEV-OXIDE] Maestrea plugin test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does [DEV-OXIDE] Maestrea plugin test reset?
The record holds too few of [DEV-OXIDE] Maestrea plugin test's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 39 days 20 hours.
Population
Where does [DEV-OXIDE] Maestrea plugin test place in the wider field of Rust servers?
Over the last seven days, [DEV-OXIDE] Maestrea plugin test has #15,478 for player hours, in the top 68% of all ranked servers.
What does the population on [DEV-OXIDE] Maestrea plugin test look like?
[DEV-OXIDE] Maestrea plugin test is offline at the moment; the last time it was seen was 38 days 9 hours ago.
Tags
How should you read the tags on [DEV-OXIDE] Maestrea plugin test?
You'll see [DEV-OXIDE] Maestrea plugin test tagged with gmvanilla (Game mode): You play vanilla survival here; mp5 (Max players): Its slot count is 5; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs164530 (Build): This runs on build 164530; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^p (PvE): The danger comes from the world, not from other players; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does [DEV-OXIDE] Maestrea plugin test appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [DEV-OXIDE] Maestrea plugin test: Modded Rust servers, graded and Rust PvE servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on [DEV-OXIDE] Maestrea plugin test?
The name of [DEV-OXIDE] Maestrea plugin test gives no gather rate. With no change from the game default, groups take up to 8 players. pve is the mode here, no PvP between players. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on [DEV-OXIDE] Maestrea plugin test?
A procedural map, generated by the game, is what [DEV-OXIDE] Maestrea plugin test runs.
How to join
What is the way to join [DEV-OXIDE] Maestrea plugin test?
Enter client.connect 98.128.242.189:28025 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 asmp5,ptrak,$r?,v2633,^p,gmvanilla,cs164530,ts8,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp5
Max playersIts slot count is 5.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs164530
BuildThis runs on build 164530.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Gameplay
^p
PvEThe danger comes from the world, not from other players.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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. Even marks across the subjects, from F to F.