Working its way up from the back of the class: #15,491 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
32/ 100
F
Lost ground: down 5,565 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.
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.
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 67% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
·······
·······
·······
·······
·······
····
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.
usual gap1.4 daysbetween real wipes
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Sat 19 SepFri 18 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sat 19 Sep, 10:15 UTC40d ago
1
–
running
0
Fri 18 Sep, 01:40 UTC41d ago
1
–
1.4 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
ORAX TEST leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 82.39.133.212:28080 is the address to use.
How reliable is ORAX TEST, and is it up?
At this moment, ORAX TEST is offline; the last time it was seen was 36 days 15 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 15 September 2026.
Which Rust version is ORAX TEST running?
Rust network protocol 2633 and build 164530 on Linux is what ORAX TEST runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does ORAX TEST wipe, and how often?
There are too few wipes on record for ORAX TEST 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. 40 days 11 hours have passed since this world was made.
What happens on ORAX TEST when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 0 hours after it began.
Population
What position does ORAX TEST hold in the rankings?
In the top 67% of all ranked servers, ORAX TEST sits at #15,491 for player hours over the last seven days.
What does the population on ORAX TEST look like?
The last sighting of ORAX TEST was 36 days 15 hours ago, and it is offline right now.
Tags
What is meant by the tags on ORAX TEST?
The game's browser takes its cue from the tags ORAX TEST has set: gmrust (Game mode): Rust survival, played by the standard rules; mp5 (Max players): The server holds 5 slots; 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; cs164530 (Build): Build number: 164530; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon. 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 Rust Server Score filters and lists feature ORAX TEST?
Rust Server Score lists that include ORAX TEST: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
What settings and rules apply on ORAX TEST?
You will find no gather rate in the name of ORAX TEST. The group limit stays at the game's default of 8 players. survival is the mode here, 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 Carbon. VAC, Valve's anti-cheat, is enabled.
ORAX TEST runs which map?
A procedural map of size 3,500 and seed 1337, generated by the game, is what ORAX TEST runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map. You will see the map name listed as: Custom Map.
Getting in
How do you get onto ORAX TEST?
To connect, start Rust, press F1, and type client.connect 82.39.133.212:28080. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp5,ptrak,$r?,v2633,gmrust,cs164530,ts8,^z,^y
Game
gmrust
Game modeRust survival, played by the standard rules.
mp5
Max playersThe server holds 5 slots.
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.
cs164530
BuildBuild number: 164530.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is Carbon.
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.