On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 500% full
7-day average0peak –
Rank#15,339top 69%
Last wipe48d agoweekly schedule
Next wipe22hThu 29 Oct, 20:32 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 50 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,339 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
66/ 100
C+
Slows down under load at times: 40 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 166 places this week. Nothing a good wipe can't fix.
A term to build on.
Strongest in uptime (A); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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, measured since 17 Sep. 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
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 29 October, 20:32 UTC, in 22h.
Weekly: 7 days after its last 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
Where in the world is PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN?
You won't see a region from PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN, whose region code is us1. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 64.40.8.156:23014.
How dependable is PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN, and is it online at the moment?
The server is up: PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN is online now. About 20 hours ago, it restarted, based on the uptime it reports. It was up 100% of the time over the last 7 full days, 168 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
Is PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN smooth to play on?
It never fell below 38 server fps in the last 48 hours, averaging 40. At its peak, it held 87,124 entities, including buildings, deployables and all else in the world. Up to 2,790 MB of memory was used. Players feel lag when fps drops and entities pile up.
On what Rust version does PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN sit?
You will find PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN on Rust network protocol 2633 and build 163493, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Resets
How frequently does PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN wipe its map?
The estimate for PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN's next wipe comes from weekly: 7 days after its last wipe. Expect the next wipe on Thursday 29 October at 20:32 UTC. It has been running its current world for 48 days 1 hours. Wipes are scheduled weekly, according to its tags.
Player numbers
What position does PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN hold in the rankings?
Over the last seven days, PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN has #15,339 for player hours, in the top 69% of all ranked servers.
Is PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN a busy server?
With 50 slots available, PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN currently has 0 players. For the last seven days, the average number of players was 0.
Lists and filters
What do PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN's tags stand for?
You'll see PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN tagged with gmvanilla (Game mode): You play vanilla survival here; mp50 (Max players): 50 slots are available; ts100 (Group limit): No team may go above 100; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163493 (Build): Build number: 163493; ptrak (Networking): RakNet handles it, the game's default network layer; $rus1 (Region code): us1 is the region code this server uses; ^w (Weekly): Wipes come once a week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded 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.
Who operates PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN?
The same operator most likely runs PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN and the 2 other servers we track that also publish a theprojectlazarus.com hostname.
Which lists and filters on Rust Server Score show PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN?
These Rust Server Score lists count PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN among them: Modded Rust servers, graded. These filters bring it up on the server list: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
Rules and settings
Which rules does PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN enforce, and what are its settings?
The name of PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN gives no gather rate. You can play in groups of up to 100 players. You get survival here, gather and build and raid: the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Can you tell me which map PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN uses?
The game generates the procedural map on PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN at size 3,500 with seed 1. Because size and seed match, the map is the same each time, and this page links to it on RustMaps. The name of the map reads: Custom Mods / FPS+ / 4 Max.
Getting in
How should you connect to PRIVATE TEST SERVER - PROJECT LAZARUS - DO NOT JOIN?
To connect, start Rust, press F1, and type client.connect 64.40.8.156:23014. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp50,ptrak,$rus1,v2633,^w,gmvanilla,cs163493,ts100,^o^z
Game
gmvanilla
Game modeYou play vanilla survival here.
mp50
Max players50 slots are available.
ts100
Group limitNo team may go above 100.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163493
BuildBuild number: 163493.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$rus1
Region codeus1 is the region code this server uses.
Wipe schedule
^w
WeeklyWipes come once a week.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits 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 uptime (A); population is the one to work on (F).