On the class lists: C (61), with population over 48 hours and no performance mark.
Players now0/ 5000% full
7-day average0peak 6
Rank#5,247top 24%
Last wipe26d agono schedule published
Next wipe8d 7hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 500 on average. Plenty of space to grow.
Standingrank on player hours
76/ 100
B
Holds a respectable place: #5,247 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 97 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
71/ 100
B−
Climbing fast: up 2,244 places this week.
A steady term.
Strongest in performance (A+); population is the one to work on (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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 24% 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 8d 7h.
The force wipe · high confidence
wipe-day peak3players, last three wipes
Coming wipes
8d 7hThu 5 Nov, 19:00 UTCFW
36d 7hThu 3 Dec, 19:00 UTCFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 17 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 1 Oct, 22:11 UTCFW26d ago
3
–
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
You won't find a region tag on ビビラスデバッグサーバー, but its name indicates Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 162.43.36.237:29015.
How dependable is ビビラスデバッグサーバー, and is it online at the moment?
The server is up: ビビラスデバッグサーバー is online now. According to its reported uptime, the last restart was about 15 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. It was first seen by Rust Server Score on 13 September 2026.
Does ビビラスデバッグサーバー perform well?
The average over the last 48 hours was 97 server fps, and it never went below 56. At its peak, it held 83,002 entities, including buildings, deployables and all else in the world. Memory use reached up to 3,223 MB. Lag is what players feel when fps is low and the entity count climbs.
What Rust version is ビビラスデバッグサーバー on?
The server ビビラスデバッグサーバー is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does ビビラスデバッグサーバー wipe its map?
Once a month, ビビラスデバッグサーバー wipes with the force wipe. The force wipe on Thursday 5 November at 19:00 UTC is its next wipe, when all Rust servers wipe. 26 days 13 hours have passed since this world was made.
What happens on ビビラスデバッグサーバー when wipe day arrives?
The average peak on its recent wipes was 3 players. Peak numbers came 17 hours into the latest wipe.
Player numbers
Where does ビビラスデバッグサーバー place in the wider field of Rust servers?
In the top 24% of all ranked servers, ビビラスデバッグサーバー sits at #5,247 for player hours over the last seven days.
What does the population on ビビラスデバッグサーバー look like?
ビビラスデバッグサーバー is showing 0 players right now, with 500 slots in total. The seven-day average is 0 players, with a peak of 6. Over the last 48 hours, the peak hour was 12:00 UTC, averaging 3 players.
Tags
What is meant by the tags on ビビラスデバッグサーバー?
You'll see ビビラスデバッグサーバー tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp500 (Max players): Its slot count is 500; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): Build number: 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show ビビラスデバッグサーバー?
Rust Server Score lists that include ビビラスデバッグサーバー: Modded Rust servers, graded. You can find it under these server-list filters: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
What settings and rules apply on ビビラスデバッグサーバー?
The name of ビビラスデバッグサーバー gives no gather rate. The default of 8 players applies as the group cap. It runs survival, 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
ビビラスデバッグサーバー runs which map?
ビビラスデバッグサーバー runs a game-generated procedural map at size 3,900, seed 1337. A matching size and seed produce the same map, viewable on RustMaps from this page. You will see the map name listed as: Custom Map.
How to join
How do you get onto ビビラスデバッグサーバー?
Enter client.connect 162.43.36.237:29015 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?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp500
Max playersIts slot count is 500.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildBuild number: 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxidePlugin framework: 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.
A steady term. Strongest in performance (A+); population is the one to work on (F).