On the class lists: D (52), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average2peak 12
Rank#2,231top 10% · #216 in EA
Last wipe5d agoweekly schedule
Next wipe1d 4hFri 30 Oct, 11:07 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
90/ 100
A
Well up the rankings: #2,231 on player hours.
Uptimehours on the list, last 48
96/ 100
A+
Excellent attendance: on the list 46 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 124 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
73/ 100
B−
Climbing fast: up 1,016 places this week.
A fair term, with more to come.
Strongest in performance (A+); wipes are 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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 10% of all ranked servers, top 38% in EA, and #155 of the duo servers (top 37%). Ranked on player hours over the last seven days.
Attendance: the wipe record
6 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
····W··
···FW··
····W··
·······
····W··
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
fixed weekdays
Next wipe Friday 30 October, 11:07 UTC, in 1d 4h.
Every Friday at 11:07 UTC · high confidence
usual gap7 daysbetween real wipes
on rhythm80%of its recent wipes
wipe-day peak9players, last three wipes
crowd held0%else halves by day 3
Coming wipes
1d 4hFri 30 Oct, 11:07 UTC
7d 12hThu 5 Nov, 19:00 UTCFW
8d 4hFri 6 Nov, 11:07 UTC
15d 4hFri 13 Nov, 11:07 UTC
22d 4hFri 20 Nov, 11:07 UTC
29d 4hFri 27 Nov, 11:07 UTC
35d 12hThu 3 Dec, 19:00 UTCFW
36d 4hFri 4 Dec, 11:07 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 9 OctFri 2 Oct
Players each hour, from the hour of the wipe. The latest peaked at 12, 2 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 11:07 UTC5d ago
12
–
running
0
Fri 9 Oct, 11:07 UTC19d ago
9
halved by day 3
14 days
0
Fri 2 Oct, 11:07 UTC26d ago
5
halved by day 2
7 days
1
Thu 1 Oct, 22:10 UTCFW27d ago
5
–
0.5 days
0
Fri 25 Sep, 11:07 UTC33d ago
7
halved by day 3
6.5 days
1
Sun 20 Sep, 14:41 UTC38d ago
9
halved by day 3
4.9 days
2
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 Main | Solo/Duo | Driftive.jp?
You'll see JP Main | Solo/Duo | Driftive.jp listed in Asia, tagged EA. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 160.236.116.1:28024.
Is JP Main | Solo/Duo | Driftive.jp up, and how steady is its uptime?
You can join now: JP Main | Solo/Duo | Driftive.jp is online. The uptime it reports puts the last restart at about 6 hours ago. It was up 160 of 168 hours over the last 7 full days, which is 95% of the time. The first sighting by Rust Server Score was on 13 September 2026.
Does JP Main | Solo/Duo | Driftive.jp perform well?
The average over the last 48 hours was 124 server fps, and it never went below 49. At its peak, it held 76,809 entities, including buildings, deployables and all else in the world. At its highest, it used 2,519 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does JP Main | Solo/Duo | Driftive.jp sit?
You will find JP Main | Solo/Duo | Driftive.jp on Rust network protocol 2635 and build 168909, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
On what schedule does JP Main | Solo/Duo | Driftive.jp reset?
The wipe rhythm on JP Main | Solo/Duo | Driftive.jp is every Friday at 11:07 UTC. It is due to wipe next on Friday 30 October at 11:07 UTC. The world it runs now was created 5 days 19 hours. Its tags state that it wipes weekly.
What happens on JP Main | Solo/Duo | Driftive.jp when wipe day arrives?
Across its recent wipes, the busiest moments averaged 9 players. 2 hours after the latest wipe began, the crowd hit its peak. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. Day 3 is when it sank below half in the wipes that did not hold.
Population
What position does JP Main | Solo/Duo | Driftive.jp hold in the rankings?
Over the last seven days, JP Main | Solo/Duo | Driftive.jp has #2,231 for player hours, in the top 10% of all ranked servers and #216 in Asia. It comes #155 among servers in the duo group.
Is JP Main | Solo/Duo | Driftive.jp a busy server?
JP Main | Solo/Duo | Driftive.jp is showing 0 players right now, with 100 slots in total. The seven-day average is 2 players, with a peak of 12. Over the last 48 hours, the peak hour was 13:00 UTC, averaging 6 players.
Tags
How should you read the tags on JP Main | Solo/Duo | Driftive.jp?
gmvanilla (Game mode): You play vanilla survival here; mp100 (Max players): 100 slots are available; ts2 (Group limit): No team may go above 2; 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): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^w (Weekly): Wipes come once a week; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; EA (East Asia): In the server browser it appears under East Asia are the tags JP Main | Solo/Duo | Driftive.jp 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 JP Main | Solo/Duo | Driftive.jp appear in the Rust Server Score lists and filters?
Rust Server Score lists that include JP Main | Solo/Duo | Driftive.jp: Duo servers, marked like a report, Best community servers, graded and Vanilla Rust servers, graded. It shows under the following filters on the server list: Region: Asia; Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Weekly ^w and Vanilla ^v; Group limit: Duo; Wipe schedule: Weekly; Last wipe: In the last week.
Map and rules
How is JP Main | Solo/Duo | Driftive.jp set up, and what rules does it keep?
Nothing in the name of JP Main | Solo/Duo | Driftive.jp states a gather rate. The cap on group size is 2 players (duo). survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. Vanilla is what it calls itself: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
Which map is in play on JP Main | Solo/Duo | Driftive.jp?
A procedural map of size 3,500 and seed 261884878, generated by the game, is what JP Main | Solo/Duo | Driftive.jp runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
How do you get onto JP Main | Solo/Duo | Driftive.jp?
Enter client.connect 160.236.116.1:28024 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://discord.com/invite/2HJNcdUZBu.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^w,^v,EA,gmvanilla,cs168909,ts2
Game
gmvanilla
Game modeYou play vanilla survival here.
mp100
Max players100 slots are available.
ts2
Group limitNo team may go above 2.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyWipes come once a week.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Region
EA
East AsiaIn the server browser it appears 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 fair term, with more to come. Strongest in performance (A+); wipes are the one to work on (F).