Fig. 1Players on Lost In Rust Test ServerRG-S13509-01 · Sheet 1 of 10
Fig. 2
Server performance
Server fpsWipe
EntitiesWipe
Memory, MBWipe
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.
Fig. 2FPS, entities and memoryRG-S13509-02 · Sheet 2 of 10
Fig. 3
Rank
daily · 1 is best
RankRank in region
Top 61% of all ranked servers. Ranked on player hours over the last seven days.
Fig. 3Rank on player hours, dailyRG-S13509-03 · Sheet 3 of 10
Schedule
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap1.7 daysbetween real wipes
on rhythm25%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 1
The first 48 hours of its last wipes
Wed 21 OctTue 20 OctSun 18 Oct
Fig. 4Players each hour from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 21 hours in.
ScheduleExpected wipesRG-S13509-04 · Sheet 4 of 10
Log
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Wed 28 Oct, 00:17 UTC22h ago
–
–
running
0
Wed 21 Oct, 01:48 UTC7d ago
1
halved by day 1
6.9 days
0
Tue 20 Oct, 02:08 UTC8d ago
1
–
1 days
0
Sun 18 Oct, 14:20 UTC10d ago
1
–
1.5 days
0
Thu 15 Oct, 00:20 UTC13d ago
0
–
3.6 days
0
Tue 13 Oct, 02:07 UTC15d ago
2+1 queue
–
1.9 days
0
Mon 5 Oct, 23:57 UTC22d ago
1
halved by day 1
7.1 days
0
Sun 4 Oct, 15:37 UTC24d ago
2
–
1.3 days
1
Sat 3 Oct, 23:05 UTC24d ago
2
–
0.7 days
0
Sat 3 Oct, 02:31 UTC25d ago
2
–
0.9 days
1
Wed 30 Sep, 22:51 UTC27d ago
0
–
2.2 days
0
Tue 29 Sep, 00:22 UTC29d ago
1
–
1.9 days
0
Mon 28 Sep, 02:10 UTC30d ago
1
–
0.9 days
0
Tue 22 Sep, 02:25 UTC36d ago
3
halved by day 1
6 days
1
Tue 15 Sep, 10:14 UTC43d ago
0
–
6.7 days
1
Sun 13 Sep, 17:24 UTC45d ago
1
–
1.7 days
1
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.
Table 1Wipe logRG-S13509-05 · Sheet 5 of 10
Similar assemblies
Similar servers
the same kind of game, then region, group limit, rate and wipes
Is Lost In Rust Test Server online, and what uptime has been recorded?
Lost In Rust Test Server is up at this moment. The uptime it reports puts the last restart at about 12 hours ago. 85 of 168 hours up over the last 7 full days, which is 51% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
2.
Is Lost In Rust Test Server stable in the figures recorded?
30 server fps on average over the last 48 hours, and never under 30. Counted at its highest: 107,789 entities, buildings, deployables and the rest of the world included. 3,563 MB is the memory peak. What players feel as lag is low fps together with a climbing entity count.
3.
What location is recorded for Lost In Rust Test Server?
No region is published by Lost In Rust Test Server. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. You will find it at 64.40.8.191:29015.
4.
On which Rust version is Lost In Rust Test Server running?
On Linux, Lost In Rust Test Server runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles the update.
Population
5.
What does the population history show for Lost In Rust Test Server?
Current player count on Lost In Rust Test Server: 0. The seven-day mean is 0 players; the peak over the same period is 1. Averaged over the last 48 hours, the player count is highest at 00:00 UTC: 1 players.
6.
In the rankings, which position does Lost In Rust Test Server hold?
Player hours over seven days place Lost In Rust Test Server at #13,509, within the top 61% of ranked servers.
Wipe data
7.
What is recorded on Lost In Rust Test Server on wipe day?
At their busiest, its recent wipes drew 1 players on average. 21 hours after the latest wipe, the crowd peaked. Half that peak was held until the next wipe in 0% of its recent wipes. By day 1 the crowd had fallen below half on the wipes where it did not hold.
8.
Which times and days are wipes plotted at on Lost In Rust Test Server?
There is no next wipe to predict at Lost In Rust Test Server, which wipes at irregular times. At the monthly force wipe, which is next on Thursday 5 November at 19:00 UTC, a wipe hits every Rust server. The world it runs now was made 22 hours ago.
Map and rules
9.
Which rules and settings are recorded for Lost In Rust Test Server?
The name of Lost In Rust Test Server records no gather rate. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Plugins or settings change the game, and the browser lists it as Modded. Oxide plugins are run on it. Anti-cheat: VAC, from Valve, is on.
10.
Which map has Lost In Rust Test Server loaded?
Lost In Rust Test Server runs a procedural map of size 4,700 with seed 1337, generated by the game. Viewing on RustMaps, from this page, is possible: the same size and seed give the same map. The name of the map reads: Custom Map.
Tags
11.
On Rust Graphs, which lists and filters contain Lost In Rust Test Server?
The Rust Graphs lists that carry Lost In Rust Test Server are: Modded Rust servers. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 24 hours.
12.
Which meaning is attached to each tag on Lost In Rust Test Server?
Tags published by Lost In Rust Test Server, and read by the game's server browser: gmrust (Game mode): Survival in standard Rust style; mp0 (Max players): Slots: 0; ts8 (Group limit): The default team size of 8 applies; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): The region code field is empty; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): The game is changed by plugins or settings; the listing is Modded; oxidation (Custom tag): Set by the owner or a plugin, not by standard Rust. Shown at the top of this page are its current players, its queue and the age of its world, all carried in the tags.
Connect
13.
How is Lost In Rust Test Server joined?
In Rust, press F1 and type client.connect 64.40.8.191:29015 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you.
NotesAnswered from the figuresRG-S13509-09 · Sheet 9 of 10
Key
Server tags
what each one means
Published asmp0,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z,oxidation
Game
gmrust
Game modeSurvival in standard Rust style.
mp0
Max playersSlots: 0.
ts8
Group limitThe default team size of 8 applies.
v2635
ProtocolJoin only if your game is on protocol 2635.
cs168909
BuildBuild: 168909.
ptrak
NetworkingThe network layer is RakNet, the game's standard.
$r?
Region codeThe region code field is empty.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedThe game is changed by plugins or settings; the listing is Modded.
Other
oxidation
Custom tagSet by the owner or a plugin, not by 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.
KeyTag string decodedRG-S13509-10 · Sheet 10 of 10