Working its way up from the back of the class: #15,710 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
20/ 100
F
Lost ground: down 9,354 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.
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 71% 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 RobloxMC (Rust frontend) based in?
You'll find no region listed by RobloxMC (Rust frontend). Rust Server Score reports the location a server gives; it does not check where the machine actually is. 131.107.1.140:28015 is the address to use.
How reliable is RobloxMC (Rust frontend), and is it up?
The server is down: RobloxMC (Rust frontend) is offline now, with the last sighting 20 days 18 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 6 October 2026.
On what Rust version does RobloxMC (Rust frontend) sit?
You will find RobloxMC (Rust frontend) on Rust network protocol 2634 and build 166586, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Resets
When does RobloxMC (Rust frontend) wipe, and how often?
RobloxMC (Rust frontend) has not had enough wipes recorded to reveal 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 26 days 6 hours.
Population
Where does RobloxMC (Rust frontend) sit among Rust servers?
Over the last seven days, RobloxMC (Rust frontend) has #15,710 for player hours, in the top 71% of all ranked servers.
How many players does RobloxMC (Rust frontend) usually have?
It has been 20 days 18 hours since RobloxMC (Rust frontend) was last seen, and it is offline right now.
Tags and filters
How should you read the tags on RobloxMC (Rust frontend)?
gmrust (Game mode): Rust survival, played by the standard rules; mp8 (Max players): 8 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs166586 (Build): This runs on build 166586; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^p (PvE): This is player against world: players do not fight each other; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon are the tags RobloxMC (Rust frontend) 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.
Which Rust Server Score filters and lists feature RobloxMC (Rust frontend)?
Rust Server Score lists that include RobloxMC (Rust frontend): Modded Rust servers, graded and Rust PvE servers, graded. These filters bring it up on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Carbon ^y; Group limit: 5 or more.
Rules and settings
What settings and rules apply on RobloxMC (Rust frontend)?
You will find no gather rate in the name of RobloxMC (Rust frontend). With no change from the game default, groups take up to 8 players. pve is the mode here, no PvP between players. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is not enabled.
RobloxMC (Rust frontend) runs which map?
A procedural map, generated by the game, is what RobloxMC (Rust frontend) runs.
Connecting
How do you get onto RobloxMC (Rust frontend)?
Enter client.connect 131.107.1.140: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 asmp8,ptrak,$r?,v2634,^z,^y,^p,gmrust,cs166586,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp8
Max players8 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166586
BuildThis runs on build 166586.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Gameplay
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under 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.