Working its way up from the back of the class: #16,857 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
unmarked
–
No rank a week ago to compare with.
A term to build on.
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, top 86% in EU. 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
Next wipe Thursday 5 November, 19:00 UTC, in 8d 2h.
The 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
The EU tag on L36 – Test Server 663 puts it in Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 46.225.103.39:28015.
How dependable is L36 – Test Server 663, and is it online at the moment?
The server is down: L36 – Test Server 663 is offline now, with the last sighting 28 days 16 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 29 September 2026.
Which Rust version is L36 – Test Server 663 running?
You will find L36 – Test Server 663 on Rust network protocol 2634 and build 166266, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
On what schedule does L36 – Test Server 663 reset?
The estimate for L36 – Test Server 663's next wipe comes from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe, when every Rust server resets. 28 days 16 hours have passed since this world was made. Its tags record that it wipes monthly.
Player count
Where does L36 – Test Server 663 sit among Rust servers?
Over the last seven days, L36 – Test Server 663 has #16,857 for player hours, in the top 71% of all ranked servers and #2,569 in Europe.
Is L36 – Test Server 663 a busy server?
It has been 28 days 16 hours since L36 – Test Server 663 was last seen, and it is offline right now.
Tags
What do L36 – Test Server 663's tags stand for?
You'll see L36 – Test Server 663 tagged with gmvanilla (Game mode): Survival, vanilla style; mp40 (Max players): 40 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs166266 (Build): Build number: 166266; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^m (Monthly): The server wipes once a month, with the force wipe from Facepunch; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^r (Roleplay): Roleplay is the focus here; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon; EU (Europe): In the server browser it appears under Europe in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show L36 – Test Server 663?
These Rust Server Score lists count L36 – Test Server 663 among them: European Rust servers, graded, Modded Rust servers, graded and Roleplay servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Roleplay ^r, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
Server rules
How is L36 – Test Server 663 set up, and what rules does it keep?
The name of L36 – Test Server 663 gives no gather rate. The default of 8 players applies as the group cap. roleplay is the mode here, jobs, towns and rules for roleplay. The server browser lists it as Modded: plugins or settings change how the game plays. The plugin count runs to Carbon. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. You are covered by VAC, Valve's anti-cheat.
How to join
How do you get onto L36 – Test Server 663?
Enter client.connect 46.225.103.39:28015 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 asmp40,ptrak,$r?,v2634,^z,^y,^m,^v,^r,EU,gmvanilla,cs166266,ts8
Game
gmvanilla
Game modeSurvival, vanilla style.
mp40
Max players40 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs166266
BuildBuild number: 166266.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^m
MonthlyThe server wipes once a month, with the force wipe from Facepunch.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Gameplay
^r
RoleplayRoleplay is the focus here.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is Carbon.
Region
EU
EuropeIn the server browser it appears under Europe.
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.