Offline 183.197.173.148:28017 checked 24d ago
FAZE UP!
Connect
srv = rust.server("183.197.173.148:27017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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 best
srv.rank.plot(invert=True) # 1 is bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.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 1, 1 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Mon 5 Oct, 02:15 UTC24d ago | 1 | NaN | running | 1 |
# 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 183.197.173.148:28017
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 5 Oct 2026, 03:20 UTC
- hostname
- –
- first seen
- 4 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | [US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | NA · no group limit · biweekly · 252 on average | 263/2000 |
| 1 | [EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom Weapo | EU · no group limit · biweekly · 243 on average | 236/2000 |
| 2 | Chrayntopia ♡ ︎PvE | RP | PvP | NA · groups of 8+ · biweekly · 105 on average | 83/200 |
| 3 | 【炮炮PVE启蒙】纯净｜特色｜突袭｜技能 | EA · groups of 16+ · biweekly · 59 on average | 17/200 |
| 4 | [PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendl | groups of 30+ · monthly · 54 on average | 63/300 |
| 5 | TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10 | EU · groups of 30+ · biweekly · 49 on average | 0/100 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does FAZE UP! rank?
Player hours over seven days put FAZE UP! at #15,986, in the top 71% of the ranked set.
How many players does FAZE UP! hold at once?
FAZE UP! returns no live count at this refresh, having last been seen 24 days 16 hours ago.
Server facts
What is the Rust version on FAZE UP!?
Rust network protocol 2634 and build 166652 on Windows is what FAZE UP! runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is FAZE UP!, and is it up?
Offline now for FAZE UP!, last seen 24 days 16 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 4 October 2026.
Where does FAZE UP! sit?
There is no region published for FAZE UP!. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 183.197.173.148:28017.
Settings and map
Which settings and rules does FAZE UP! run?
The name FAZE UP! carries no gather rate. Eight players per group: that is the game's default, and it applies here. Recorded as pve, no combat between players. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has FAZE UP! selected?
The game generates its map: procedural, on FAZE UP!.
Wipe data
On what schedule does FAZE UP! wipe?
A rhythm cannot be read from the wipes of FAZE UP! on record, which are too few. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 24 days 19 hours ago, and that is the one in play.
On FAZE UP!, what happens on wipe day?
The average peak over recent wipes is 1 players. Peak population on the latest wipe came 1 hours in.
Lists and tags
Which Rust Data filters and lists contain FAZE UP!?
The Rust Data lists that FAZE UP! fits are: Modded Rust servers and Rust PvE servers. It appears under these filters on the server list: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on FAZE UP!?
The game's server browser reads these tags from FAZE UP!: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Build number: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^p (PvE): No player-versus-player combat; the danger comes from the world; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): Modded listing: the game is changed by plugins or settings. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Connecting
What is the way to join FAZE UP!?
In Rust, F1 opens the console: type client.connect 183.197.173.148:28017. Launch Rust on this page does the same by opening the game through Steam and connecting.