Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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
No rank history yet.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
······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.
wipe-day peak2players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 13 Sep, 15:27 UTC46d ago
2
–
running
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
The name of RUST PVE [RU] beta 0.1 points to Europe, though no region tag is set. Rust Server Score takes the server's word for its location and does not trace the hardware. 203.16.163.249:20466 is the address to use.
Is RUST PVE [RU] beta 0.1 up, and how steady is its uptime?
The server is down: RUST PVE [RU] beta 0.1 is offline now, with the last sighting 45 days 22 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 13 September 2026.
What Rust version is RUST PVE [RU] beta 0.1 on?
The server RUST PVE [RU] beta 0.1 is on Rust network protocol 2633 and build 162929 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does RUST PVE [RU] beta 0.1 wipe its map?
There are too few wipes on record for RUST PVE [RU] beta 0.1 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. 46 days 3 hours have passed since this world was made.
What happens on RUST PVE [RU] beta 0.1 when wipe day arrives?
Recent wipes have peaked at 2 players on average. Peak numbers came 0 hours into the latest wipe.
Population
Where does RUST PVE [RU] beta 0.1 sit among Rust servers?
Over the last seven days, RUST PVE [RU] beta 0.1 has #15,138 for player hours, in the top – of all ranked servers.
How many players does RUST PVE [RU] beta 0.1 usually have?
The last sighting of RUST PVE [RU] beta 0.1 was 45 days 22 hours ago, and it is offline right now.
Tags and filters
What do RUST PVE [RU] beta 0.1's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp125 (Max players): Its slot count is 125; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs162929 (Build): Build number: 162929; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags RUST PVE [RU] beta 0.1 publishes, and the game's server browser reads them. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does RUST PVE [RU] beta 0.1 appear in the Rust Server Score lists and filters?
These Rust Server Score lists count RUST PVE [RU] beta 0.1 among them: European Rust servers, graded and Modded Rust servers, graded. You can find it under these server-list filters: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Rules and settings
What settings and rules apply on RUST PVE [RU] beta 0.1?
The name of RUST PVE [RU] beta 0.1 gives no gather rate. The group limit stays at the game's default of 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. 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.
Can you tell me which map RUST PVE [RU] beta 0.1 uses?
RUST PVE [RU] beta 0.1 runs a procedural map, which the game generates.
How to join
How should you connect to RUST PVE [RU] beta 0.1?
To connect, start Rust, press F1, and type client.connect 203.16.163.249:20466. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp125,ptrak,$r?,v2633,gmrust,cs162929,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp125
Max playersIts slot count is 125.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs162929
BuildBuild number: 162929.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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.
Not enough figures yet to write a report. Check back after a few days on the list.