On the class lists: C− (56), with population over 48 hours and no performance mark.
Players now1/ 1010% full
7-day average1peak 1
Rank#10,278top 46%
Last wipe7d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
7/ 100
F
A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
54/ 100
D
Working its way up from the back of the class: #10,278 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
59/ 100
C−
Moving up: up 1,781 places this week.
A term to build on.
Strongest in momentum (C−); 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
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 46% 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
AREA13_DEV 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 101.179.194.43:28015.
Is AREA13_DEV up, and how steady is its uptime?
The server is down: AREA13_DEV is offline now, with the last sighting 6 days 4 hours ago. It was up 3% of the time over the last 6 full days, 5 of 144 hours. The first sighting by Rust Server Score was on 22 October 2026.
What Rust version is AREA13_DEV on?
Rust network protocol 2635 and build 168909 on Windows is what AREA13_DEV runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does AREA13_DEV wipe, and how often?
There are too few wipes on record for AREA13_DEV to show a 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 7 days 6 hours.
Population
Where does AREA13_DEV place in the wider field of Rust servers?
Over the last seven days, AREA13_DEV has #10,278 for player hours, in the top 46% of all ranked servers.
How many players does AREA13_DEV usually have?
AREA13_DEV is offline at the moment; the last time it was seen was 6 days 4 hours ago. Averaging 1 players over seven days, it peaked at 1.
Tags and filters
What do AREA13_DEV's tags stand for?
You'll see AREA13_DEV tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): 10 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): Oxide (uMod) provides the plugin framework here; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does AREA13_DEV appear in the Rust Server Score lists and filters?
Rust Server Score lists that include AREA13_DEV: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Server rules
How is AREA13_DEV set up, and what rules does it keep?
The name of AREA13_DEV gives no gather rate. The group limit stays at the game's default of 8 players. You get survival here, 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. You are covered by VAC, Valve's anti-cheat.
AREA13_DEV runs which map?
A procedural map, generated by the game, is what AREA13_DEV runs.
Getting in
How do you get onto AREA13_DEV?
Enter client.connect 101.179.194.43: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 asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max players10 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideOxide (uMod) provides the plugin framework here.
^z
ModdedThe game is changed by plugins or settings; you will find it 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. Strongest in momentum (C−); population is the one to work on (F).