On the class lists: C− (55), with population over 48 hours and no performance mark.
Players now35/ 5007% full
7-day average21peak 49
Rank#1,089top 5%
Last wipe10d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
4/ 100
F
A quiet classroom so far: 21 of 500 on average. Plenty of space to grow.
Standingrank on player hours
95/ 100
A+
Well up the rankings: #1,089 on player hours.
Uptimehours on the list, last 48
19/ 100
F
Attendance needs work: on the list only 9 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 103 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
100/ 100
A+
Climbing fast: up 14,036 places this week.
A fair term, with more to come.
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
No five-minute samples in the last two hours.
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 14 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 5% 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
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······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 peak0players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 18 Oct, 15:46 UTC10d ago
0
–
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 reports the location a server gives; it does not check where the machine actually is. You can connect at 31.58.47.54:29115.
How reliable is ビビラスサーバー, and is it up?
At this moment, ビビラスサーバー is offline; the last time it was seen was 38 hours ago. According to its reported uptime, the last restart was about 6 hours ago. For the last 7 full days, it was up 62 of 168 hours, or 37% of the time. The first sighting by Rust Server Score was on 14 October 2026.
Is ビビラスサーバー smooth to play on?
The average over the last 48 hours was 103 server fps, and it never went below 83. Buildings, deployables and everything else in the world added up to as many as 86,452 entities. At its highest, it used 3,065 MB of memory. When fps is low and entities climb, that is lag to players.
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
On what schedule does ビビラスサーバー reset?
ビビラスサーバー 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. It has been running its current world for 10 days 15 hours.
What happens on ビビラスサーバー when wipe day arrives?
Across its recent wipes, the busiest moments averaged 0 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does ビビラスサーバー sit among Rust servers?
Over the last seven days, ビビラスサーバー has #1,089 for player hours, in the top 5% of all ranked servers.
Is ビビラスサーバー a busy server?
It has been 38 hours since ビビラスサーバー was last seen, and it is offline right now. The seven-day average is 21 players, with a peak of 49. The highest average in the last 48 hours came at 15:00 UTC, with 40 players.
Tags and filters
What do ビビラスサーバー's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp500 (Max players): 500 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): Join only if your game runs protocol 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded are the tags ビビラスサーバー publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does ビビラスサーバー appear in the Rust Server Score lists and filters?
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; Last wipe: In the last 2 weeks; Players now: At least 10; Average players: 10+ on average.
Rules and settings
Which rules does ビビラスサーバー enforce, and what are its settings?
The name of ビビラスサーバー gives no gather rate. With no change from the game default, groups take up to 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. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on ビビラスサーバー?
A procedural map of size 3,900 and seed 1337, generated by the game, is what ビビラスサーバー runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Map.
Connecting
How should you connect to ビビラスサーバー?
To connect, start Rust, press F1, and type client.connect 31.58.47.54:29115. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp500
Max players500 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolJoin only if your game runs protocol 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^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 fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).