QuixLan
Offline 172.56.41.192:28015 checked 24d ago
Server instruments
no direct query in 48 hoursPlayers now
33% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 66% 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.
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
the same kind of game, then region, group limit, rate and wipes- 352/425
- 22/250
- 41/250
- 144/200
- 63/200
- 65/100
Quick answers
from the figures on this pageReset cycle
What wipe timing does QuixLan follow?
Its rhythm cannot be told from the wipes of QuixLan on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 24 days 11 hours ago.
Tag meanings
Which tags does QuixLan carry, and what do they mean?
These are the tags QuixLan publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp3 (Max players): Slots: 3; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): The server runs game build 166652; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Which lists and filters on Rust Metrics show QuixLan?
Rust Metrics lists featuring QuixLan: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Occupancy
What position does QuixLan hold among Rust servers?
Player hours over seven days put QuixLan at #15,034, in the top 66% of all ranked servers.
How full does QuixLan get?
Reading for QuixLan: offline at this moment; last seen 24 days 10 hours ago.
Server
Where does QuixLan sit?
Reading: location. QuixLan gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 172.56.41.192:28015.
What Rust version is QuixLan on?
Reading: QuixLan, Rust network protocol 2634 and build 166652, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is QuixLan up, and how often does it stay up?
Check: connection. QuixLan is offline at this moment. Last contact was 24 days 10 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 3 October 2026.
Settings and map
What rules does QuixLan enforce, and what are its settings?
No gather rate appears in the name: QuixLan. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is QuixLan on?
Check: map. Procedural, generated by the game, on QuixLan.
Join
What do you do to join QuixLan?
Press F1 in Rust and enter client.connect 172.56.41.192:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.