Live coverage · Rust server
Offline RUSTINGEZ_STAGING is not on the server list right now. The figures below are from when it was last seen, 29d ago.
The count
Embedded chart
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Embedded chart
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.
Embedded chart
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Coming up · wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 1h. The force wipe
This server has not put up a new map since the desk started watching it.
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.
The next wipe on RUSTINGEZ_STAGING is an estimate, drawn from the force wipe. Thursday 5 November at 19:00 UTC brings the force wipe, its next wipe and one that hits every Rust server. 30 days 21 hours have passed since this world was generated. A monthly wipe schedule is published in its tags.
These are the Rust Live Stats lists RUSTINGEZ_STAGING fits: Live Rust community servers and Vanilla Rust servers, live. Under the filters Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: Premium; Server tag: Monthly ^m, Vanilla ^v and Premium ^q; Group limit: 5 or more; Wipe schedule: Monthly it appears on the server list.
These are the tags RUSTINGEZ_STAGING makes public: gmrust (Game mode): Standard survival, in the Rust style; mp50 (Max players): The slot count is 50; ts8 (Group limit): Team cap: 8, which is the game default; v2634 (Protocol): You need protocol 2634 on your game to get in; cs166065 (Build): The game build is 166065; ptrak (Networking): The network layer is RakNet, the standard the game uses; $r? (Region code): The server sets no region code; ^m (Monthly): It wipes with Facepunch's force wipe, once each month; ^v (Vanilla): The rates, kits and rules are unchanged from what Facepunch ships; ^q (Premium): Rust's premium status is required to join. The current player count, the queue and the world's creation time also sit in the tags, shown at the top of this page.
RUSTINGEZ_STAGING reads offline at the moment; the last sighting was 29 days 21 hours ago.
Ranked by seven-day player hours, RUSTINGEZ_STAGING is #14,441, placing it in the top 60% of ranked servers.
No gather rate appears in the name RUSTINGEZ_STAGING. Eight players per group, which is the game's default. It runs survival, the standard game: gather, build, raid. Raiding and player combat are both permitted. The server browser lists it under Community. By its own label it is vanilla: the rates, kits and rules are unchanged from what Facepunch ships. Rust's premium status is required to join. Anti-cheat: VAC from Valve is enabled.
RUSTINGEZ_STAGING uses a procedural map, which the game generates.
No region is published by RUSTINGEZ_STAGING. Where the machine stands is not checked by Rust Live Stats; only the location a server states is shown. You can reach it at 190.206.235.241:28015.
The setup on RUSTINGEZ_STAGING is Rust network protocol 2634 and build 166065 with Windows. To join, your game must use the same protocol; Steam handles the update for you.
As of now, RUSTINGEZ_STAGING is offline; the last sighting was 29 days 21 hours ago. 0 of 168 hours were online in the last 7 full days, giving 0% uptime. Rust Live Stats has tracked it since 29 September 2026.
Enter client.connect 190.206.235.241:28015 in the console (F1 in Rust). Another way is Launch Rust and join on this page: it opens Rust through Steam and connects you. Rust's premium status is required to join.