A quiet classroom so far: 0 of 50 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,348 on player hours.
Uptimehours on the list, last 48
4/ 100
F
Attendance needs work: on the list only 2 of the last 48 hours.
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
unmarked
–
No rank a week ago to compare with.
A term to build on.
Strongest in standing (F); 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.
No daily history yet.
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 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
Where in the world is Rust Devblog 299 [No-Steam / Oxide]?
The region code for Rust Devblog 299 [No-Steam / Oxide] is eu2, but no region is published. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 91.235.145.236:28015.
How reliable is Rust Devblog 299 [No-Steam / Oxide], and is it up?
You cannot join now: Rust Devblog 299 [No-Steam / Oxide] is offline, last seen 45 hours ago. It was up 0 of 24 hours over the last 1 full day, which is 0% of the time. It was first seen by Rust Server Score on 26 October 2026.
What Rust version is Rust Devblog 299 [No-Steam / Oxide] on?
The server Rust Devblog 299 [No-Steam / Oxide] is on Rust network protocol 2594 and build 128111 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does Rust Devblog 299 [No-Steam / Oxide] wipe, and how often?
There are too few wipes on record for Rust Devblog 299 [No-Steam / Oxide] to show a rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 2 days 10 hours.
Population
Where does Rust Devblog 299 [No-Steam / Oxide] sit among Rust servers?
Over the last seven days, Rust Devblog 299 [No-Steam / Oxide] has #15,348 for player hours, in the top 69% of all ranked servers.
Is Rust Devblog 299 [No-Steam / Oxide] a busy server?
The last sighting of Rust Devblog 299 [No-Steam / Oxide] was 45 hours ago, and it is offline right now. A seven-day average of 0 players applies here.
Tags and filters
How should you read the tags on Rust Devblog 299 [No-Steam / Oxide]?
The game's browser takes its cue from the tags Rust Devblog 299 [No-Steam / Oxide] has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2594 (Protocol): The game protocol is 2594, so your game must match that version to join; cs128111 (Build): The game build is 128111; ptrak (Networking): RakNet handles it, the game's default network layer; $reu2 (Region code): eu2 is the region code this server uses; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under 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.
Where does Rust Devblog 299 [No-Steam / Oxide] appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Rust Devblog 299 [No-Steam / Oxide] among them: 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; Last wipe: In the last 3 days.
Server rules
How is Rust Devblog 299 [No-Steam / Oxide] set up, and what rules does it keep?
The name of Rust Devblog 299 [No-Steam / Oxide] gives no 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. 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. VAC, Valve's anti-cheat, is not enabled.
Can you tell me which map Rust Devblog 299 [No-Steam / Oxide] uses?
The game generates a procedural map for Rust Devblog 299 [No-Steam / Oxide].
Getting in
What is the way to join Rust Devblog 299 [No-Steam / Oxide]?
Enter client.connect 91.235.145.236: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,$reu2,v2594,gmrust,cs128111,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2594
ProtocolThe game protocol is 2594, so your game must match that version to join.
cs128111
BuildThe game build is 128111.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$reu2
Region codeeu2 is the region code this server uses.
Mods and access
^o
OxidePlugin framework: 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. Strongest in standing (F); population is the one to work on (F).