Working its way up from the back of the class: #16,869 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
46/ 100
D
Slipped a little: down 1,397 places this week. Nothing a good wipe can't fix.
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 71% 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
Rust 2293 Local Test leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. 91.181.115.226:27015 is the address to use.
Is Rust 2293 Local Test up, and how steady is its uptime?
You cannot join now: Rust 2293 Local Test is offline, last seen 29 days 19 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. On 29 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Rust 2293 Local Test sit?
Rust network protocol 2293 on Windows is what Rust 2293 Local Test runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe cycle
How frequently does Rust 2293 Local Test wipe its map?
Rust 2293 Local Test has not had enough wipes recorded to reveal 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 92 days 20 hours.
Player numbers
What position does Rust 2293 Local Test hold in the rankings?
In the top 71% of all ranked servers, Rust 2293 Local Test sits at #16,869 for player hours over the last seven days.
What does the population on Rust 2293 Local Test look like?
The last sighting of Rust 2293 Local Test was 29 days 19 hours ago, and it is offline right now.
Tags
What do Rust 2293 Local Test's tags stand for?
The game's browser takes its cue from the tags Rust 2293 Local Test has set: gmrust (Game mode): Survival in the standard Rust style; mp1 (Max players): Its slot count is 1; v2293 (Protocol): The game protocol is 2293, so your game must match that version to join; ptrak (Networking): This is RakNet: the network layer Rust normally uses; oxide (Oxide): The plugin framework in use is Oxide (uMod); modded (Modded): Plugins or settings alter the game, so it sits under Modded; h532c2936 (Custom tag): The owner or a plugin created this tag, so it is not standard Rust; stok (Custom tag): The owner or a plugin created this tag, so it is not standard Rust. 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 2293 Local Test?
These Rust Server Score lists count Rust 2293 Local Test among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded.
Rules and settings
What settings and rules apply on Rust 2293 Local Test?
You will find no gather rate in the name of Rust 2293 Local Test. No group limit is published. survival is the mode here, gather and build and raid: 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. You are not covered by VAC, Valve's anti-cheat.
Can you tell me which map Rust 2293 Local Test uses?
The game generates a procedural map for Rust 2293 Local Test.
How to join
How should you connect to Rust 2293 Local Test?
Enter client.connect 91.181.115.226:27015 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,v2293,h532c2936,stok,gmrust,oxide,modded
Game
gmrust
Game modeSurvival in the standard Rust style.
mp1
Max playersIts slot count is 1.
v2293
ProtocolThe game protocol is 2293, so your game must match that version to join.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
Mods and access
oxide
OxideThe plugin framework in use is Oxide (uMod).
modded
ModdedPlugins or settings alter the game, so it sits under Modded.
Other
h532c2936
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
stok
Custom tagThe owner or a plugin created this tag, so it is not standard Rust.
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).