Working its way up from the back of the class: #15,285 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 156 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.
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.
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 18 Oct. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% of all ranked servers. 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
In what location does RTP 2.1.0 - disposable server tests sit?
RTP 2.1.0 - disposable server tests leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 91.197.6.152:26384.
How reliable is RTP 2.1.0 - disposable server tests, and is it up?
The server is down: RTP 2.1.0 - disposable server tests is offline now, with the last sighting 9 days 17 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 18 October 2026, Rust Server Score saw it for the first time.
On what Rust version does RTP 2.1.0 - disposable server tests sit?
Rust network protocol 2634 and build 167781 on Linux is what RTP 2.1.0 - disposable server tests runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
On what schedule does RTP 2.1.0 - disposable server tests reset?
There are too few wipes on record for RTP 2.1.0 - disposable server tests to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. 10 days 5 hours have passed since this world was made.
Population
What position does RTP 2.1.0 - disposable server tests hold in the rankings?
Over the last seven days, RTP 2.1.0 - disposable server tests has #15,285 for player hours, in the top 69% of all ranked servers.
Is RTP 2.1.0 - disposable server tests a busy server?
It has been 9 days 17 hours since RTP 2.1.0 - disposable server tests was last seen, and it is offline right now.
Tags
How should you read the tags on RTP 2.1.0 - disposable server tests?
gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): 1 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167781 (Build): Build number: 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Plugin framework: Carbon are the tags RTP 2.1.0 - disposable server tests publishes, and the game's server browser reads 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 Rust Server Score filters and lists feature RTP 2.1.0 - disposable server tests?
Rust Server Score lists that include RTP 2.1.0 - disposable server tests: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Rules and settings
How is RTP 2.1.0 - disposable server tests set up, and what rules does it keep?
You will find no gather rate in the name of RTP 2.1.0 - disposable server tests. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in 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. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
RTP 2.1.0 - disposable server tests runs which map?
The game generates the procedural map on RTP 2.1.0 - disposable server tests at size 1,000 with seed 424242. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Connecting
How do you get onto RTP 2.1.0 - disposable server tests?
Enter client.connect 91.197.6.152:26384 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 asmp1,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max players1 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonPlugin framework: Carbon.
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).