Working its way up from the back of the class: #15,831 on player hours.
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
27/ 100
F
Lost ground: down 7,380 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
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
Top 72% of all ranked servers, and #510 of the trio servers (top 83%). 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 Thursday 29 October, 15:11 UTC, in 42m.
Its weekly schedule tag · low confidence
wipe-day peak1players, last three wipes
Coming wipes
42mThu 29 Oct, 15:11 UTC
7d 4hThu 5 Nov, 19:00 UTCFW
14d 0hThu 12 Nov, 15:11 UTC
21d 0hThu 19 Nov, 15:11 UTC
28d 0hThu 26 Nov, 15:11 UTC
35d 4hThu 3 Dec, 19:00 UTCFW
42d 0hThu 10 Dec, 15:11 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 8 Oct, 15:11 UTC20d ago
1
–
running
1
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
serv | Duo/Trio leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 62.220.51.189:28015 is the address to use.
How reliable is serv | Duo/Trio, and is it up?
You cannot join now: serv | Duo/Trio is offline, last seen 20 days 18 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 7 October 2026.
Which Rust version is serv | Duo/Trio running?
The server serv | Duo/Trio is on Rust network protocol 2634 and build 166652 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
On what schedule does serv | Duo/Trio reset?
Its tag sets the prediction, as the record holds too few of serv | Duo/Trio's wipes to confirm its schedule. Expect the next wipe on Thursday 29 October at 15:11 UTC. 22 days 19 hours have passed since this world was made. Its tags state that it wipes weekly.
What happens on serv | Duo/Trio when wipe day arrives?
Recent wipes have peaked at 1 players on average. The crowd on the latest wipe was largest 0 hours after it began.
Player count
Where does serv | Duo/Trio sit among Rust servers?
Over the last seven days, serv | Duo/Trio has #15,831 for player hours, in the top 72% of all ranked servers. In the trio group, it ranks #510.
How many players does serv | Duo/Trio usually have?
It has been 20 days 18 hours since serv | Duo/Trio was last seen, and it is offline right now.
Tags
How should you read the tags on serv | Duo/Trio?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp150 (Max players): 150 slots are available; ts3 (Group limit): No team may go above 3; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): Build number: 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^w (Weekly): It wipes weekly; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags serv | Duo/Trio 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 serv | Duo/Trio appear in the Rust Server Score lists and filters?
Rust Server Score lists that include serv | Duo/Trio: Modded Rust servers, graded and Rust servers with a trio group limit. You can find it under these server-list filters: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly.
Server rules
Which rules does serv | Duo/Trio enforce, and what are its settings?
You will find no gather rate in the name of serv | Duo/Trio. The cap on group size is 3 players (trio). It runs survival, gather and build and raid: 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. Oxide plugins are running on it. VAC, Valve's anti-cheat, is enabled.
serv | Duo/Trio runs which map?
The game generates a procedural map for serv | Duo/Trio.
How to join
How do you get onto serv | Duo/Trio?
To connect, start Rust, press F1, and type client.connect 62.220.51.189:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp150,ptrak,$r?,v2634,^w,gmrust,cs166652,ts3,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp150
Max players150 slots are available.
ts3
Group limitNo team may go above 3.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildBuild number: 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyIt wipes weekly.
Mods and access
^o
OxidePlugin framework: 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.
A term to build on. Even marks across the subjects, from F to F.