On the class lists: F (34), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,290top 69%
Last wipe26d agono schedule published
Next wipe–no wipe seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 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,290 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
37/ 100
F
Slipped a little: down 3,988 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); 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.
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 3 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
You'll find no region listed by RustServer_670. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 160.251.213.151:28015.
Is RustServer_670 up, and how steady is its uptime?
You cannot join now: RustServer_670 is offline, last seen 4 days 13 hours ago. For the last 7 full days, it was up 83 of 168 hours, or 49% of the time. On 3 October 2026, Rust Server Score saw it for the first time.
What Rust version is RustServer_670 on?
Rust network protocol 2634 and build 166652 on Linux is what RustServer_670 runs. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
How frequently does RustServer_670 wipe its map?
There are too few wipes on record for RustServer_670 to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 26 days 12 hours have passed since this world was made.
Player numbers
What position does RustServer_670 hold in the rankings?
In the top 69% of all ranked servers, RustServer_670 sits at #15,290 for player hours over the last seven days.
Is RustServer_670 a busy server?
RustServer_670 is offline at the moment; the last time it was seen was 4 days 13 hours ago. For the last seven days, the average number of players was 0.
Lists and filters
What do RustServer_670's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp50 (Max players): 50 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; 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): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set; ^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 are the tags RustServer_670 publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Where does RustServer_670 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include RustServer_670: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
What settings and rules apply on RustServer_670?
You will find no gather rate in the name of RustServer_670. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in 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. The server runs Valve's anti-cheat, VAC.
Which map is in play on RustServer_670?
The game generates the procedural map on RustServer_670 at size 3,000 with seed 30230. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Connecting
How should you connect to RustServer_670?
To connect, start Rust, press F1, and type client.connect 160.251.213.151:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$r?,v2634,gmrust,cs166652,ts8,^o^z
Game
gmrust
Game modeRust survival, played by the standard rules.
mp50
Max players50 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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 (F); population is the one to work on (F).