Working its way up from the back of the class: #13,654 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
51/ 100
D
Moving up: up 181 places this week.
A term to build on.
Strongest in momentum (D); standing 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
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.
No daily history yet.
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 #479 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
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
You won't see a region from Dev Test Trio, whose region code is fra. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 102.132.245.88:27916.
How reliable is Dev Test Trio, and is it up?
You cannot join now: Dev Test Trio is offline, last seen 20 days 14 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 9 October 2026.
Which Rust version is Dev Test Trio running?
The server Dev Test Trio is on Rust network protocol 2634 and build 167231 under Linux. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
How frequently does Dev Test Trio wipe its map?
Dev Test Trio has not had enough wipes recorded to reveal its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 21 days 8 hours.
Player numbers
Where does Dev Test Trio sit among Rust servers?
Over the last seven days, Dev Test Trio has #13,654 for player hours, in the top 62% of all ranked servers. In the trio group, it ranks #479.
Is Dev Test Trio a busy server?
It has been 20 days 14 hours since Dev Test Trio was last seen, and it is offline right now.
Tags
What do Dev Test Trio's tags stand for?
You'll see Dev Test Trio tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp1 (Max players): 1 slots are available; ts3 (Group limit): A team can hold 3 players at most; v2634 (Protocol): Join only if your game runs protocol 2634; cs167231 (Build): This runs on build 167231; ptnone (Networking): 'none' is the network layer here; $rfra (Region code): Region code: fra; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; stok (Custom tag): A plugin or the owner set this tag; it is not a standard Rust one 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.
Which lists and filters on Rust Server Score show Dev Test Trio?
Rust Server Score lists that include Dev Test 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: Modded ^z; Group limit: Trio.
Server rules
How is Dev Test Trio set up, and what rules does it keep?
You will find no gather rate in the name of Dev Test 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. The server runs Valve's anti-cheat, VAC.
Which map is in play on Dev Test Trio?
The game generates a procedural map for Dev Test Trio.
How to join
How should you connect to Dev Test Trio?
To connect, start Rust, press F1, and type client.connect 102.132.245.88:27916. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asgmrust,ptnone,cs167231,$rfra,ts3,^z,mp1,v2634,stok,ts3
Game
gmrust
Game modeRust survival, played by the standard rules.
mp1
Max players1 slots are available.
ts3
Group limitA team can hold 3 players at most.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167231
BuildThis runs on build 167231.
ptnone
Networking'none' is the network layer here.
$rfra
Region codeRegion code: fra.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
stok
Custom tagA plugin or the owner set this tag; it is not a standard Rust one.
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 momentum (D); standing is the one to work on (F).