Working its way up from the back of the class: #14,977 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
42/ 100
F
Slipped a little: down 2,505 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in momentum (F); 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.
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.
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 69% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
··W····
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 7 Oct, 03:45 UTC20d ago
1
–
running
0
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 LuxsServer. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 45.44.117.114:28015 is the address to use.
How reliable is LuxsServer, and is it up?
The server is down: LuxsServer is offline now, with the last sighting 15 days 1 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 14 September 2026.
Which Rust version is LuxsServer running?
The server LuxsServer is on Rust network protocol 2634 and build 166652 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does LuxsServer wipe, and how often?
LuxsServer 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. The world it runs now was created 20 days 21 hours.
What happens on LuxsServer when wipe day arrives?
Recent wipes have peaked at 1 players on average. 1 hours after the latest wipe began, the crowd hit its peak.
Player count
Where does LuxsServer sit among Rust servers?
Over the last seven days, LuxsServer has #14,977 for player hours, in the top 69% of all ranked servers.
What does the population on LuxsServer look like?
The last sighting of LuxsServer was 15 days 1 hours ago, and it is offline right now.
Lists and filters
What do LuxsServer's tags stand for?
You'll see LuxsServer tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set in the browser, which picks them up from the server. 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 LuxsServer appear in the Rust Server Score lists and filters?
Rust Server Score lists that include LuxsServer: Best community servers, graded. It shows under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Rules and settings
How is LuxsServer set up, and what rules does it keep?
You will find no gather rate in the name of LuxsServer. With no change from the game default, groups take up to 8 players. It runs survival, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
LuxsServer runs which map?
A procedural map, generated by the game, is what LuxsServer runs.
Connecting
How do you get onto LuxsServer?
To connect, start Rust, press F1, and type client.connect 45.44.117.114:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersThe server holds 10 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
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); standing is the one to work on (F).