Working its way up from the back of the class: #15,842 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
50/ 100
D
Holding steady: up 116 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 72% 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 RUST_LIVING_WORLD_LOCAL. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 93.152.223.17:28015.
Is RUST_LIVING_WORLD_LOCAL up, and how steady is its uptime?
You cannot join now: RUST_LIVING_WORLD_LOCAL is offline, last seen 19 days 20 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 9 October 2026.
Which Rust version is RUST_LIVING_WORLD_LOCAL running?
Rust network protocol 2634 and build 167231 on Windows is what RUST_LIVING_WORLD_LOCAL runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does RUST_LIVING_WORLD_LOCAL wipe its map?
The record holds too few of RUST_LIVING_WORLD_LOCAL's wipes to tell its rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 19 days 20 hours.
Player count
Where does RUST_LIVING_WORLD_LOCAL sit among Rust servers?
Over the last seven days, RUST_LIVING_WORLD_LOCAL has #15,842 for player hours, in the top 72% of all ranked servers.
What does the population on RUST_LIVING_WORLD_LOCAL look like?
RUST_LIVING_WORLD_LOCAL is offline at the moment; the last time it was seen was 19 days 20 hours ago.
Lists and filters
How should you read the tags on RUST_LIVING_WORLD_LOCAL?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): Join only if your game runs protocol 2634; cs167231 (Build): Build number: 167231; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): There is no region code on this server; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): Carbon provides the plugin framework here are the tags RUST_LIVING_WORLD_LOCAL 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 lists and filters on Rust Server Score show RUST_LIVING_WORLD_LOCAL?
Rust Server Score lists that include RUST_LIVING_WORLD_LOCAL: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
Server rules
What settings and rules apply on RUST_LIVING_WORLD_LOCAL?
The name of RUST_LIVING_WORLD_LOCAL gives no gather rate. With no change from the game default, groups take up to 8 players. survival is the mode 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. Carbon plugins are running on it. You are covered by VAC, Valve's anti-cheat.
RUST_LIVING_WORLD_LOCAL runs which map?
RUST_LIVING_WORLD_LOCAL runs a procedural map, which the game generates.
How to join
How do you get onto RUST_LIVING_WORLD_LOCAL?
To connect, start Rust, press F1, and type client.connect 93.152.223.17:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp1,ptrak,$r?,v2634,gmrust,cs167231,ts8,^z,^y
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp1
Max playersThe server holds 1 slots.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs167231
BuildBuild number: 167231.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonCarbon provides the plugin framework here.
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).