Working its way up from the back of the class: #14,748 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,453 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.
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.
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 1 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 63% 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
No region is published for BizRust Test01.10. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 80.242.59.83:35080.
How dependable is BizRust Test01.10, and is it online at the moment?
At this moment, BizRust Test01.10 is offline; the last time it was seen was 27 days 15 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 1 October 2026, Rust Server Score saw it for the first time.
What Rust version is BizRust Test01.10 on?
You will find BizRust Test01.10 on Rust network protocol 2634 and build 166465, hosted on Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
When does BizRust Test01.10 wipe, and how often?
BizRust Test01.10 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 27 days 20 hours.
Player numbers
Where does BizRust Test01.10 place in the wider field of Rust servers?
In the top 63% of all ranked servers, BizRust Test01.10 sits at #14,748 for player hours over the last seven days.
How many players does BizRust Test01.10 usually have?
BizRust Test01.10 is offline at the moment; the last time it was seen was 27 days 15 hours ago.
Tags and filters
What do BizRust Test01.10's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1100 (Max players): The server holds 1,100 slots; ts300 (Group limit): No team may go above 300; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166465 (Build): This runs on build 166465; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^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 BizRust Test01.10 publishes, and the game's server browser reads them. 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 lists and filters on Rust Server Score show BizRust Test01.10?
These Rust Server Score lists count BizRust Test01.10 among them: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Map and rules
How is BizRust Test01.10 set up, and what rules does it keep?
Nothing in the name of BizRust Test01.10 states a gather rate. A group here can reach 300 players. You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map BizRust Test01.10 uses?
A custom map of size 4,500 is in use on BizRust Test01.10, and its published file can be downloaded from this page.
How to join
How do you get onto BizRust Test01.10?
Enter client.connect 80.242.59.83:35080 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. You can find its website at https://miragerust.gg/.
Server tags
what each one means
Published asmp1100,ptrak,$r?,v2634,gmrust,cs166465,ts300,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1100
Max playersThe server holds 1,100 slots.
ts300
Group limitNo team may go above 300.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166465
BuildThis runs on build 166465.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
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.