DWG RG-S15339Server sheetchecked 14m ago
Lexxer Map_test
Online 147.93.160.205:28815 checked 14m ago
Players
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
Top 69% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Not 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
| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 2 Oct, 07:04 UTC26d 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
Quick answers
Server data
What uptime is recorded for Lexxer Map_test, and is it up?
Lexxer Map_test is up at this moment. About 6 days 1 hours ago is when it last restarted, measured from the uptime it reports. For the last 7 full days the record is 168 of 168 hours up, 100% of the time. The first sighting of it by Rust Graphs was on 13 September 2026.
How does Lexxer Map_test perform, as measured?
Average server fps over the last 48 hours is 50; the lowest was 10. Counted at its highest: 68,026 entities, buildings, deployables and the rest of the world included. The highest memory use recorded is 3,584 MB. Players feel low fps and a climbing entity count as lag.
What location is recorded for Lexxer Map_test?
No region is published by Lexxer Map_test. Rust Graphs shows where a server says it is; the place the machine stands is not looked up. You will find it at 147.93.160.205:28815.
What Rust version is recorded for Lexxer Map_test?
Rust network protocol 2635 and build 168909 on Windows: that is what Lexxer Map_test runs. The same protocol is required for joining, and Steam updates your game to it.
Population
What does the population history show for Lexxer Map_test?
Current player count on Lexxer Map_test: 0, of 50 slots. The seven-day mean on this server is 0 players.
In the rankings, which position does Lexxer Map_test hold?
Player hours over seven days place Lexxer Map_test at #15,339, within the top 69% of ranked servers.
Schedules
What is recorded on Lexxer Map_test on wipe day?
At their busiest, its recent wipes drew 0 players on average. At 0 hours after the latest wipe the crowd was at its peak.
What wipe schedule has been recorded for Lexxer Map_test?
Lexxer Map_test's rhythm cannot be told yet: too few of its wipes are on record. The next monthly force wipe is on Thursday 5 November at 19:00 UTC, and it wipes every Rust server. The world it runs now was made 26 days 15 hours ago.
Map and rules
What settings and rules apply on Lexxer Map_test?
Gather rate for Lexxer Map_test: not stated in the name. No limit is published beyond the default: 8 players per group. survival, the standard game: gather, build, raid, is the game mode. Raiding and player combat are permitted. Listed as Modded in the server browser: the game is changed by plugins or settings. Plugins run: Oxide. Rust's premium status is required to join. Anti-cheat: VAC, from Valve, is on.
Which map has Lexxer Map_test loaded?
Lexxer Map_test runs a procedural map of size 4,250 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 map is named as follows: Custom Map.
Lists and filters
Where does Lexxer Map_test appear among the Rust Graphs lists and filters?
The Rust Graphs lists that carry Lexxer Map_test are: Modded Rust servers. On the server list, these filters bring it up: Type: Modded; Game mode: Premium; Server tag: Premium ^q, Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meaning is attached to each tag on Lexxer Map_test?
Tags published by Lexxer Map_test, and read by the game's server browser: gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): Slots: 50; ts8 (Group limit): The team limit is 8, which is the game default; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): Region code not set; ^q (Premium): Rust's premium status is required to join; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it is listed under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Connect
What is the way to connect to Lexxer Map_test?
In Rust, press F1 and type client.connect 147.93.160.205:28815 in the console. Launch Rust on this page also works: Rust opens through Steam and connects you. Rust's premium status is required to join.
Server tags
Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,^q,ts8,^o^z
Game
gmrust
mp50
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^q
^o
^z
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.