Working its way up from the back of the class: #15,905 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
28/ 100
F
Lost ground: down 7,018 places this week. A strong wipe could turn it round.
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.
AveragePeak
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 30 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···F···
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
force wipes only
Next wipe Thursday 5 November, 19:00 UTC, in 7d 23h.
The force wipe · high confidence
wipe-day peak0players, last three wipes
Coming wipes
7d 23hThu 5 Nov, 19:00 UTCFW
35d 23hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
No hourly players around its wipes yet.
Players each hour, from the hour of the wipe. The latest peaked at 0, 19 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 19:00 UTCFW27d ago
0
–
running
2
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
You won't find a region tag on RUST PVE [RU] bete 0.1, but its name indicates Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 93.85.224.86:28015 is the address to use.
How reliable is RUST PVE [RU] bete 0.1, and is it up?
The server is down: RUST PVE [RU] bete 0.1 is offline now, with the last sighting 26 days 5 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 27 September 2026.
On what Rust version does RUST PVE [RU] bete 0.1 sit?
You will find RUST PVE [RU] bete 0.1 on Rust network protocol 2634 and build 166494, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does RUST PVE [RU] bete 0.1 reset?
The force wipe each month is the only wipe RUST PVE [RU] bete 0.1 takes. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. The world it runs now was created 27 days.
What should you expect from wipe day on RUST PVE [RU] bete 0.1?
Recent wipes have peaked at 0 players on average. Peak numbers came 19 hours into the latest wipe.
Population
Where does RUST PVE [RU] bete 0.1 place in the wider field of Rust servers?
Over the last seven days, RUST PVE [RU] bete 0.1 has #15,905 for player hours, in the top 70% of all ranked servers.
What does the population on RUST PVE [RU] bete 0.1 look like?
It has been 26 days 5 hours since RUST PVE [RU] bete 0.1 was last seen, and it is offline right now.
Tags
What do RUST PVE [RU] bete 0.1's tags stand for?
The game's browser takes its cue from the tags RUST PVE [RU] bete 0.1 has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp500 (Max players): Its slot count is 500; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166494 (Build): Build number: 166494; 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. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does RUST PVE [RU] bete 0.1 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RUST PVE [RU] bete 0.1 among them: European Rust servers, graded and Modded Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does RUST PVE [RU] bete 0.1 enforce, and what are its settings?
Nothing in the name of RUST PVE [RU] bete 0.1 states a gather rate. With no change from the game default, groups take up to 8 players. You get survival here, gather, build and raid, as in 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.
Can you tell me which map RUST PVE [RU] bete 0.1 uses?
RUST PVE [RU] bete 0.1 runs a game-generated procedural map at size 3,600, seed 1234567. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
What is the way to join RUST PVE [RU] bete 0.1?
Enter client.connect 93.85.224.86: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 asmp500,ptrak,$r?,v2634,gmrust,cs166494,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp500
Max playersIts slot count is 500.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166494
BuildBuild number: 166494.
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. Even marks across the subjects, from F to F.