malingowski.net (formerly PioneerX)
Online 71.211.149.100:28015 checked 9m ago
Server instruments
last reading Wed 06:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 126 · below 20 is lag, below 10 is badEntities
48 h range 79,156–95,887 · memory 2,235 MBUptime
21 h 4 min 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 59% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
force wipes onlyNext wipe Thursday 5 November, 19:00 UTC, in 8d 11h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC8d 11hFW
- WPT 2Thu 3 Dec, 19:00 UTC36d 11hFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 3, 17 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 22:33 UTC FW26d ago | 3 | – | 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- 124/500
- 127/100
- 131/225
- 57/700
- 4/200
- 32/1000
Quick answers
from the figures on this pageWipe timing
What happens on malingowski.net (formerly PioneerX) when wipe day comes?
An average of 3 players came at the busiest on its recent wipes. 17 hours after the wipe, the crowd peaked on the latest wipe.
What wipe timing does malingowski.net (formerly PioneerX) follow?
The only wipe for malingowski.net (formerly PioneerX) is the force wipe, once a month. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. The world in play was created 26 days 9 hours ago.
Tag meanings
How should you read the tags on malingowski.net (formerly PioneerX)?
Tags published by malingowski.net (formerly PioneerX), read by the game's server browser: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): The server holds 50 slots; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.
Where does malingowski.net (formerly PioneerX) appear in Rust Metrics lists and filters?
On Rust Metrics, malingowski.net (formerly PioneerX) sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Population
Where does malingowski.net (formerly PioneerX) sit in the rankings?
Player hours over seven days put malingowski.net (formerly PioneerX) at #13,133, in the top 59% of all ranked servers.
What is the population on malingowski.net (formerly PioneerX)?
Current headcount on malingowski.net (formerly PioneerX): 0 players, 50 slots available. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 0 players, at 21:00 UTC over the last 48 hours.
Server
Where does malingowski.net (formerly PioneerX) sit?
No region comes from malingowski.net (formerly PioneerX). Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 71.211.149.100:28015.
What Rust version is malingowski.net (formerly PioneerX) on?
Reading: malingowski.net (formerly PioneerX), Rust network protocol 2635 and build 168909, Linux. To get in, your game needs the same protocol; Steam applies the update.
Is performance on malingowski.net (formerly PioneerX) within range?
Check: fps. Average 147 server fps over the last 48 hours, low of 126. Within range. Reading: 95,887 entities at the highest. That covers buildings, deployables and everything else. Check: memory. Peak use was 2,652 MB. What players call lag comes from low fps and an entity count on the rise.
Is malingowski.net (formerly PioneerX) up, and how often does it stay up?
Check: connection. malingowski.net (formerly PioneerX) is online at this moment. Reading: uptime. About 21 hours ago it restarted, on its own count. Reading: 100% uptime over the last 7 full days. It was up 168 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Map and rules
What settings and rules apply on malingowski.net (formerly PioneerX)?
Check: gather rate. The name malingowski.net (formerly PioneerX) does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Anti-cheat reading: VAC on, Valve's system.
What map is malingowski.net (formerly PioneerX) on?
Check: map. Procedural, size 4,000, seed 205175, generated by the game on malingowski.net (formerly PioneerX). The map repeats when size and seed match. Open it on RustMaps from this page.
How to join
How do you connect to malingowski.net (formerly PioneerX)?
Press F1 in Rust and enter client.connect 71.211.149.100:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.