On the class lists: D (48), with population over 48 hours and no performance mark.
Players now0/ 600% full
7-day average0peak 2
Rank#5,150top 23%
Last wipe6d agoweekly schedule
Next wipe12hFri 30 Oct, 09:31 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 60 on average. Plenty of space to grow.
Standingrank on player hours
77/ 100
B
Holds a respectable place: #5,150 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
79/ 100
B
Mostly smooth: 47 server fps on average.
Wipeskeeping the crowd after a wipe
20/ 100
F
Needs to keep more players after wipe day: 20% of wipes kept half their crowd.
Momentumrank now against a week ago
46/ 100
D
Slipped a little: down 417 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (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 23% of all ranked servers, and #343 of the trio servers (top 55%). Ranked on player hours over the last seven days.
Attendance: the wipe record
7 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
····WW·
····W··
····W··
····W··
····W··
····W··
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
a steady gap
Next wipe Friday 30 October, 09:31 UTC, in 12h.
Every 6 days 23 hours · medium confidence
usual gap6.9 daysbetween real wipes
on rhythm83%of its recent wipes
wipe-day peak2players, last three wipes
crowd held20%else halves by day 2.5
Coming wipes
12hFri 30 Oct, 09:31 UTC
6d 22hThu 5 Nov, 19:00 UTCFW
7d 12hFri 6 Nov, 09:01 UTC
14d 11hFri 13 Nov, 08:31 UTC
21d 11hFri 20 Nov, 08:01 UTC
28d 10hFri 27 Nov, 07:31 UTC
34d 22hThu 3 Dec, 19:00 UTCFW
35d 10hFri 4 Dec, 07:01 UTC
The first 48 hours of its last wipes
Fri 23 OctFri 16 OctFri 9 Oct
Players each hour, from the hour of the wipe. The latest peaked at 2, 41 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 23 Oct, 10:01 UTC6d ago
2
–
running
0
Fri 16 Oct, 10:31 UTC13d ago
2
halved by day 6
7 days
2
Fri 9 Oct, 10:05 UTC20d ago
3
✓ held half
7 days
0
Fri 2 Oct, 13:00 UTC27d ago
3
halved by day 1
6.9 days
0
Fri 25 Sep, 09:54 UTC34d ago
2
halved by day 2
7.1 days
0
Sat 19 Sep, 10:11 UTC40d ago
3
halved by day 3
6 days
2
Fri 18 Sep, 10:57 UTC41d ago
3
–
1 days
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
Which region is [Slo Duo Trio]Gochi-kawa based in?
You'll find no region listed by [Slo Duo Trio]Gochi-kawa. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 126.235.65.137:28015.
Is [Slo Duo Trio]Gochi-kawa up, and how steady is its uptime?
The server is up: [Slo Duo Trio]Gochi-kawa is online now. The uptime it reports puts the last restart at about 6 days 9 hours ago. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does [Slo Duo Trio]Gochi-kawa run?
The average over the last 48 hours was 47 server fps, and it never went below 16. Buildings, deployables and everything else in the world added up to as many as 96,934 entities. At its highest, it used 4,175 MB of memory. Lag is what players feel when fps is low and the entity count climbs.
Which Rust version is [Slo Duo Trio]Gochi-kawa running?
Rust network protocol 2635 and build 168909 on Windows is what [Slo Duo Trio]Gochi-kawa runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does [Slo Duo Trio]Gochi-kawa wipe, and how often?
The gap between [Slo Duo Trio]Gochi-kawa's wipes has been about 6.9 days recently. Friday 30 October at 09:31 UTC is the date set for its next wipe. It has been running its current world for 6 days 10 hours. Its tags state that it wipes weekly.
What happens on [Slo Duo Trio]Gochi-kawa when wipe day arrives?
Across its recent wipes, the busiest moments averaged 2 players. Peak numbers came 41 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 20% of its recent wipes. Day 2.5 is when it sank below half in the wipes that did not hold.
Player count
Where does [Slo Duo Trio]Gochi-kawa sit among Rust servers?
Over the last seven days, [Slo Duo Trio]Gochi-kawa has #5,150 for player hours, in the top 23% of all ranked servers. It comes #343 among servers in the trio group.
What does the population on [Slo Duo Trio]Gochi-kawa look like?
[Slo Duo Trio]Gochi-kawa is showing 0 players right now, with 60 slots in total. It peaked at 2 and averaged 0 players over the last seven days. The highest average in the last 48 hours came at 11:00 UTC, with 1 players.
Tags and filters
How should you read the tags on [Slo Duo Trio]Gochi-kawa?
The game's browser takes its cue from the tags [Slo Duo Trio]Gochi-kawa has set: gmrust (Game mode): Rust survival, played by the standard rules; mp60 (Max players): 60 slots are available; ts3 (Group limit): No team may go above 3; 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; ^w (Weekly): It wipes weekly; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them. 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 person or group runs [Slo Duo Trio]Gochi-kawa?
No other server we track uses the jp-rust.com hostname that [Slo Duo Trio]Gochi-kawa publishes.
Where does [Slo Duo Trio]Gochi-kawa appear in the Rust Server Score lists and filters?
These Rust Server Score lists count [Slo Duo Trio]Gochi-kawa among them: Best community servers, graded, Rust servers with a trio group limit and Vanilla Rust servers, graded. It shows under the following filters on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Weekly ^w and Vanilla ^v; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last week.
Map and rules
How is [Slo Duo Trio]Gochi-kawa set up, and what rules does it keep?
You will find no gather rate in the name of [Slo Duo Trio]Gochi-kawa. The cap on group size is 3 players (trio). survival is the mode here, gather, build and raid, as in the standard game. Fighting and raiding between players are both allowed. Under Community in the server browser you will find this community server. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. The server runs Valve's anti-cheat, VAC.
[Slo Duo Trio]Gochi-kawa runs which map?
A procedural map of size 4,000 and seed 15448158, generated by the game, is what [Slo Duo Trio]Gochi-kawa runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
How to join
How should you connect to [Slo Duo Trio]Gochi-kawa?
Enter client.connect 126.235.65.137:28015 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 asmp60,ptrak,$r?,v2635,^w,^v,gmrust,cs168909,ts3
Game
gmrust
Game modeRust survival, played by the standard rules.
mp60
Max players60 slots are available.
ts3
Group limitNo team may go above 3.
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.
Wipe schedule
^w
WeeklyIt wipes weekly.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
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 term to build on. Strongest in uptime (A+); population is the one to work on (F).