Lexxer Map_test
Online 147.93.160.205:28815 checked 10m ago
Server instruments
last reading Thu 16:00 UTCPlayers now
0% full 7-day avgServer fps
48 h low 10 · below 20 is lag, below 10 is badEntities
48 h range 65,642–68,040 · memory 3,251 MBUptime
6 days 21 hours since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestTop 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 07:04 UTC27d ago | 0 | – | 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
the same kind of game, then region, group limit, rate and wipes- 153/500
- 126/100
- 194/225
- 97/700
- 221/700
- 348/350
Quick answers
from the figures on this pageWipe schedule
What happens on Lexxer Map_test when wipe day comes?
An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.
What wipe timing does Lexxer Map_test follow?
To tell the rhythm of Lexxer Map_test, too few of its wipes are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 27 days 10 hours ago the current world was made.
Tag meanings
Which tags does Lexxer Map_test carry, and what do they mean?
These are the tags Lexxer Map_test publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^q (Premium): Check: access. Premium players only; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does Lexxer Map_test appear in Rust Metrics lists and filters?
Rust Metrics lists featuring Lexxer Map_test: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Game mode: Premium; Server tag: Premium ^q, Modded ^z and Oxide ^o; Group limit: 5 or more.
Occupancy
What position does Lexxer Map_test hold among Rust servers?
Player hours over seven days put Lexxer Map_test at #15,327, in the top 69% of all ranked servers.
What is the population on Lexxer Map_test?
0 of 50 slots are filled on Lexxer Map_test right now. Seven-day reading: 0 players on average.
Server details
What location is Lexxer Map_test hosted in?
No region tag on Lexxer Map_test. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 147.93.160.205:28815.
What Rust version is Lexxer Map_test on?
Rust network protocol 2635 and build 168909 on Windows is the build Lexxer Map_test runs. Check: protocol. To join, your game must match; Steam handles the update.
How does Lexxer Map_test perform?
Over the last 48 hours the average was 40 server fps; the floor was 10. Reading: 68,040 entities at the highest. That covers buildings, deployables and everything else. Reading: 3,966 MB of memory at the highest. Lag, as players feel it, is low fps plus a climbing entity count.
Is Lexxer Map_test up, and how often does it stay up?
Reading: online. Lexxer Map_test answers right now. Check: restart. The uptime it reports puts the last restart about 6 days 21 hours ago. Uptime for the last 7 full days: 167 of 168 hours, or 99%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
How is Lexxer Map_test configured, and what rules are in force?
Reading the name gives no gather rate for Lexxer Map_test. No limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; gather, build and raid, as the game normally runs. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Check: access. Premium players only. Check: anti-cheat. VAC, Valve's system, is on.
What map is Lexxer Map_test on?
From seed 1337, the game generates the procedural map on Lexxer Map_test. Its size is 4,250. The map repeats when size and seed match. Open it on RustMaps from this page. Its map carries the name Custom Map.
Connection
What do you do to join Lexxer Map_test?
Check: join. Open Rust, press F1, then enter client.connect 147.93.160.205:28815. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. Check: access. Premium players only.