Not ranked yet, so there is no place in the school to report.
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
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
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.
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
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 tag appears for [JP] 蜊鈴峇魑ｳ譴ｨ Server, but the name suggests Asia. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 133.204.86.128:28015.
Is [JP] 蜊鈴峇魑ｳ譴ｨ Server up, and how steady is its uptime?
At this moment, [JP] 蜊鈴峇魑ｳ譴ｨ Server is offline; the last time it was seen was 42 days 23 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.
On what Rust version does [JP] 蜊鈴峇魑ｳ譴ｨ Server sit?
The server [JP] 蜊鈴峇魑ｳ譴ｨ Server is on Rust network protocol 2633 and build 163794 under Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does [JP] 蜊鈴峇魑ｳ譴ｨ Server wipe its map?
The record holds too few of [JP] 蜊鈴峇魑ｳ譴ｨ Server's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 43 days 18 hours have passed since this world was made.
Player numbers
Where does [JP] 蜊鈴峇魑ｳ譴ｨ Server place in the wider field of Rust servers?
Over the last seven days, [JP] 蜊鈴峇魑ｳ譴ｨ Server has #15,465 for player hours, in the top – of all ranked servers.
How many players does [JP] 蜊鈴峇魑ｳ譴ｨ Server usually have?
[JP] 蜊鈴峇魑ｳ譴ｨ Server is offline at the moment; the last time it was seen was 42 days 23 hours ago.
Tags and filters
What is meant by the tags on [JP] 蜊鈴峇魑ｳ譴ｨ Server?
The game's browser takes its cue from the tags [JP] 蜊鈴峇魑ｳ譴ｨ Server has set: gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): The server holds 20 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): Build number: 163794; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 [JP] 蜊鈴峇魑ｳ譴ｨ Server?
Rust Server Score lists that include [JP] 蜊鈴峇魑ｳ譴ｨ Server: Modded Rust servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Map and rules
Which rules does [JP] 蜊鈴峇魑ｳ譴ｨ Server enforce, and what are its settings?
Nothing in the name of [JP] 蜊鈴峇魑ｳ譴ｨ Server states a gather rate. The default of 8 players applies as the group cap. It runs survival, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
[JP] 蜊鈴峇魑ｳ譴ｨ Server runs which map?
A procedural map, generated by the game, is what [JP] 蜊鈴峇魑ｳ譴ｨ Server runs.
Connecting
How should you connect to [JP] 蜊鈴峇魑ｳ譴ｨ Server?
To connect, start Rust, press F1, and type client.connect 133.204.86.128:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2633,gmrust,cs163794,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max playersThe server holds 20 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildBuild number: 163794.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under 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.
Not enough figures yet to write a report. Check back after a few days on the list.