On the class lists: F (39), with population over 48 hours and no performance mark.
Players now0/ 10% full
7-day average0peak –
Rank#15,323top 69%
Last wipe30d agomonthly schedule
Next wipe7d 7hThu 5 Nov, 19:00 UTC FW
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 1 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,323 on player hours.
Uptimehours on the list, last 48
77/ 100
B
Missed a few lessons: on the list 37 of the last 48 hours.
Performanceserver fps, last 48 hours
98/ 100
A+
Runs smoothly: 59 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 198 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in performance (A+); 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.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 29 Sep. 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
Next wipe Thursday 5 November, 19:00 UTC, in 7d 7h.
The 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
Rust START Server leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 212.22.93.190:28014.
How dependable is Rust START Server, and is it online at the moment?
The server is down: Rust START Server is offline now, with the last sighting 10 hours ago. About 17 days 16 hours ago, it restarted, based on the uptime it reports. It was up 167 of 168 hours over the last 7 full days, which is 99% of the time. On 29 September 2026, Rust Server Score saw it for the first time.
How well does Rust START Server run?
The average over the last 48 hours was 59 server fps, and it never went below 48. Buildings, deployables and everything else in the world added up to as many as 89,164 entities. At its highest, it used 9,357 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does Rust START Server sit?
The server Rust START Server is on Rust network protocol 2633 and build 165217 under Windows. Steam updates your game for you, but you need the same protocol to join.
Resets
How frequently does Rust START Server wipe its map?
The next wipe on Rust START Server is a projection from the force wipe. When every Rust server wipes, it is the force wipe on Thursday 5 November at 19:00 UTC, and that is its next wipe. 30 days have passed since this world was made. Its tags record that it wipes monthly.
Player numbers
What position does Rust START Server hold in the rankings?
In the top 69% of all ranked servers, Rust START Server sits at #15,323 for player hours over the last seven days.
What does the population on Rust START Server look like?
It has been 10 hours since Rust START Server was last seen, and it is offline right now. For the last seven days, the average number of players was 0.
Tags and filters
How should you read the tags on Rust START Server?
The game's browser takes its cue from the tags Rust START Server has set: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): Its slot count is 1; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): Facepunch's force wipe sets the rhythm: one wipe a month; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which lists and filters on Rust Server Score show Rust START Server?
Rust Server Score lists that include Rust START Server: Modded Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
Rules and settings
How is Rust START Server set up, and what rules does it keep?
You will find no gather rate in the name of Rust START Server. The default of 8 players applies as the group cap. It runs survival, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Oxide. VAC, Valve's anti-cheat, is enabled.
Which map is in play on Rust START Server?
The game generates the procedural map on Rust START Server at size 4,000 with seed 291650. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How do you get onto Rust START Server?
Enter client.connect 212.22.93.190:28014 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?,v2633,^m,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max playersIts slot count is 1.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyFacepunch's force wipe sets the rhythm: one wipe a month.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as 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 performance (A+); population is the one to work on (F).