Working its way up from the back of the class: #15,308 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 133 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.
AveragePeak
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 70% 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
Luna Raid - LGS3 test leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 148.227.97.55:28185 is the address to use.
Is Luna Raid - LGS3 test up, and how steady is its uptime?
You cannot join now: Luna Raid - LGS3 test is offline, last seen 9 days 15 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 17 October 2026.
What Rust version is Luna Raid - LGS3 test on?
You will find Luna Raid - LGS3 test on Rust network protocol 2634 and build 167781, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does Luna Raid - LGS3 test wipe its map?
Luna Raid - LGS3 test has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 14 days 14 hours have passed since this world was made.
Population
Where does Luna Raid - LGS3 test sit among Rust servers?
Over the last seven days, Luna Raid - LGS3 test has #15,308 for player hours, in the top 70% of all ranked servers.
How many players does Luna Raid - LGS3 test usually have?
It has been 9 days 15 hours since Luna Raid - LGS3 test was last seen, and it is offline right now.
Tags
What is meant by the tags on Luna Raid - LGS3 test?
gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): Its slot count is 20; ts64 (Group limit): No team may go above 64; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; you will find it under Modded are the tags Luna Raid - LGS3 test publishes, and the game's server browser reads them. 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.
Where does Luna Raid - LGS3 test appear in the Rust Server Score lists and filters?
These Rust Server Score lists count Luna Raid - LGS3 test among them: 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.
Rules and settings
Which rules does Luna Raid - LGS3 test enforce, and what are its settings?
You will find no gather rate in the name of Luna Raid - LGS3 test. The limit for a group is 64 players. survival is the mode here, gather and build and raid: the standard game. Raiding and PvP are both permitted. 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.
Connecting
How should you connect to Luna Raid - LGS3 test?
Enter client.connect 148.227.97.55:28185 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 asmp20,ptrak,$r?,v2634,gmrust,cs167781,ts64,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max playersIts slot count is 20.
ts64
Group limitNo team may go above 64.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set here.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^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 (D); standing is the one to work on (F).