On the class lists: C+ (68), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average2peak 6
Rank#2,433top 11% · #254 in EA
Last wipe11d agobiweekly schedule
Next wipe2d 10hFri 30 Oct, 08:51 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
2/ 100
F
A quiet classroom so far: 2 of 100 on average. Plenty of space to grow.
Standingrank on player hours
89/ 100
A−
Holds a respectable place: #2,433 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: 139 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
84/ 100
B+
Climbing fast: up 1,652 places this week.
A good 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 2 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 11% of all ranked servers, top 46% in EA, and #140 of the quad servers (top 17%). 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
from its schedule tag
Next wipe Friday 30 October, 08:51 UTC, in 2d 10h.
Its biweekly schedule tag · low confidence
wipe-day peak2players, last three wipes
Coming wipes
2d 10hFri 30 Oct, 08:51 UTC
8d 20hThu 5 Nov, 19:00 UTCFW
16d 10hFri 13 Nov, 08:51 UTC
30d 10hFri 27 Nov, 08:51 UTC
36d 20hThu 3 Dec, 19:00 UTCFW
44d 10hFri 11 Dec, 08:51 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 5 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 16 Oct, 08:51 UTC11d ago
2
–
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
Where in the world is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?
You'll see [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け listed in Asia, tagged EA. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 162.43.16.74:28015.
How reliable is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け, and is it up?
You can join now: [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is online. The uptime it reports puts the last restart at about 6 hours ago. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. The first sighting by Rust Server Score was on 2 October 2026.
How well does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け run?
It never fell below 75 server fps in the last 48 hours, averaging 139. Up to 58,066 entities were in the world, covering buildings, deployables and the rest. Up to 3,470 MB of memory was used. When fps is low and entities climb, that is lag to players.
On what Rust version does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け sit?
You will find [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け on Rust network protocol 2635 and build 168909, hosted on Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け wipe, and how often?
The prediction follows its tag, because too few of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け's wipes are on record to confirm the schedule. Expect the next wipe on Friday 30 October at 08:51 UTC. It has been running its current world for 11 days 13 hours. Its tags say it wipes every two weeks.
What happens on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け when wipe day arrives?
Recent wipes have peaked at 2 players on average. The crowd on the latest wipe was largest 5 hours after it began.
Population
Where does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け place in the wider field of Rust servers?
In Asia, [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け is #254, and overall it is #2,433 on player hours over the last seven days, in the top 11% of all ranked servers. It comes #140 among servers in the quad group.
Is [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け a busy server?
Right now, 0 players are on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け, which has 100 slots. It peaked at 6 and averaged 2 players over the last seven days. The highest average in the last 48 hours came at 17:00 UTC, with 3 players.
Tags
What is meant by the tags on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?
The game's browser takes its cue from the tags [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け has set: gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): 100 slots are available; ts4 (Group limit): No team may go above 4; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): The server wipes on a two-week cycle; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; EA (East Asia): The server browser lists it under East Asia. 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 Rust Server Score filters and lists feature [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?
Rust Server Score lists that include [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け: Best community servers, graded and Vanilla Rust servers, graded. These filters bring it up on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Biweekly ^b and Vanilla ^v; Group limit: Quad; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Map and rules
Which rules does [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け enforce, and what are its settings?
The name of [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け gives no gather rate. The cap on group size is 4 players (quad). You get survival here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. The vanilla label is its own: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
[JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け runs which map?
The game generates the procedural map on [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け at size 3,500 with seed 1029781210. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
What is the way to join [JP] Tokyo Vanilla Server | Quad/Bi-Weekly/初心者向け?
Enter client.connect 162.43.16.74:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://discord.com/invite/hZYNS9UNHS.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^b,^v,EA,gmrust,cs168909,ts4
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max players100 slots are available.
ts4
Group limitNo team may go above 4.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
Region
EA
East AsiaThe server browser lists it under East Asia.
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 good term. Strongest in performance (A+); population is the one to work on (F).