Working its way up from the back of the class: #13,697 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
32/ 100
F
Lost ground: down 4,896 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 62% of all ranked servers, and #480 of the trio servers (top 79%). Ranked on player hours over the last seven days.
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
Next wipe Tuesday 3 November, 18:40 UTC, in 5d 13h.
Weekly: 7 days after its last 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
serv | Duo/Trio leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 62.220.50.25:28015 is the address to use.
How dependable is serv | Duo/Trio, and is it online at the moment?
At this moment, serv | Duo/Trio is offline; the last time it was seen was 21 days 11 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 6 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. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
How frequently does serv | Duo/Trio wipe its map?
The estimate for serv | Duo/Trio's next wipe comes from weekly: 7 days after its last wipe. Tuesday 3 November at 18:40 UTC is the date set for its next wipe. The world it runs now was created 22 days 10 hours. Wipes are scheduled weekly, according to its tags.
Population
Where does serv | Duo/Trio sit among Rust servers?
Over the last seven days, serv | Duo/Trio has #13,697 for player hours, in the top 62% of all ranked servers. It comes #480 among servers in the trio group.
Is serv | Duo/Trio a busy server?
It has been 21 days 11 hours since serv | Duo/Trio was last seen, and it is offline right now.
Tags and filters
How should you read the tags on serv | Duo/Trio?
You'll see serv | Duo/Trio tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp150 (Max players): The server holds 150 slots; ts3 (Group limit): A team can hold 3 players at most; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs166652 (Build): This runs on build 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): There is no region code on this server; ^w (Weekly): Wipes come once a week; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does serv | Duo/Trio appear in the Rust Server Score lists and filters?
These Rust Server Score lists count serv | Duo/Trio among them: Modded Rust servers, graded and Rust servers with a trio group limit. It shows under the following filters on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: Trio; Wipe schedule: Weekly.
Rules and settings
What settings and rules apply on serv | Duo/Trio?
The name of serv | Duo/Trio gives no gather rate. The cap on group size is 3 players (trio). survival is the mode here, gather and build and raid: the standard game. You can raid other players and fight them. The server browser lists it as Modded: plugins or settings change how the game plays. Oxide plugins are running on it. You are covered by VAC, Valve's anti-cheat.
Which map is in play on serv | Duo/Trio?
A procedural map, generated by the game, is what serv | Duo/Trio runs.
Getting in
How do you get onto serv | Duo/Trio?
To connect, start Rust, press F1, and type client.connect 62.220.50.25: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 modeRust survival, played by the standard rules.
mp150
Max playersThe server holds 150 slots.
ts3
Group limitA team can hold 3 players at most.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeThere is no region code on this server.
Wipe schedule
^w
WeeklyWipes come once a week.
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.