4Trust_____PvE_____DE/EN
Offline 176.57.174.158:29115 checked 34m ago
Server instruments
last reading Thu 07:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 2 · below 20 is lag, below 10 is badEntities
48 h range 62,730–82,474 · memory 1,582 MBUptime
3 h 58 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 58% 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 7d 10h. The force wipe · high confidence
Coming wipes
- WPT 1Thu 5 Nov, 19:00 UTC7d 10hFW
- WPT 2Thu 3 Dec, 19:00 UTC35d 10hFW
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 16 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Thu 1 Oct, 18:09 UTC FW27d ago | 2 | – | running | 0 |
| Thu 1 Oct, 08:42 UTC28d ago | 2 | – | 0.4 days | 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- 275/250
- 145/200
- 62/350
- 71/400
- 40/200
- 52/100
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on 4Trust_____PvE_____DE/EN?
At their busiest, its recent wipes drew 2 players on average. Peak crowd on the latest wipe: 16 hours in.
How often does 4Trust_____PvE_____DE/EN wipe, and when?
With the force wipe, once a month, 4Trust_____PvE_____DE/EN wipes. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world in play was created 27 days 14 hours ago. Its tags carry a monthly wipe schedule.
Lists and filters
Which tags does 4Trust_____PvE_____DE/EN carry, and what do they mean?
Tags published by 4Trust_____PvE_____DE/EN, read by the game's server browser: gmvanilla (Game mode): Check: mode. Vanilla survival; mp50 (Max players): Slots: 50; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): The server runs game build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): The region field is empty; ^m (Monthly): Check: wipe cycle. Monthly, alongside Facepunch's force wipe; ^v (Vanilla): The stock game: Facepunch's rates, kits and rules, unchanged; ^q (Premium): Entry needs Rust's premium status. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show 4Trust_____PvE_____DE/EN?
These Rust Metrics lists carry 4Trust_____PvE_____DE/EN: Rust community servers: live readings and Vanilla Rust servers, live. Check: filters. On the server list it appears under these: 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.
Occupancy
Where does 4Trust_____PvE_____DE/EN sit in the rankings?
Ranking for 4Trust_____PvE_____DE/EN: #12,822 on seven-day player hours, top 58% of all ranked servers.
How full does 4Trust_____PvE_____DE/EN get?
Status for 4Trust_____PvE_____DE/EN: offline. Last seen 34 minutes ago. Seven-day check: 0 players on average. Peak reading: 2. Average at the busiest hour was 0 players, at 20:00 UTC over the last 48 hours.
Server details
Which location does 4Trust_____PvE_____DE/EN run from?
No region comes from 4Trust_____PvE_____DE/EN. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 176.57.174.158:29115.
What Rust version is 4Trust_____PvE_____DE/EN on?
Reading: 4Trust_____PvE_____DE/EN, Rust network protocol 2635 and build 168909, Windows. Matching protocol is required to join. Let Steam update your game.
How does 4Trust_____PvE_____DE/EN perform?
Reading: 26 server fps on average across the last 48 hours. It never dropped below 2. Check: entities. The peak was 82,474, counting buildings, deployables and the rest of the world. Check: memory. Peak use was 2,081 MB. Lag, as players feel it, is low fps plus a climbing entity count.
What is the uptime on 4Trust_____PvE_____DE/EN, and is it online?
Check: connection. 4Trust_____PvE_____DE/EN is offline at this moment. Last contact was 34 minutes ago. Reading: uptime. About 3 hours ago it restarted, on its own count. Reading: 86% uptime over the last 7 full days. It was up 144 of 168 hours. The first sighting on Rust Metrics was 13 September 2026.
Map and rules
What settings and rules apply on 4Trust_____PvE_____DE/EN?
Check: gather rate. The name 4Trust_____PvE_____DE/EN does not state one. The group cap is 8 players, which is the default in the game. Mode check gives survival; standard play of gathering, building and raiding. Combat and raiding against other players are on. The server browser lists it under Community. The server calls itself vanilla, with this meaning: the stock game: Facepunch's rates, kits and rules, unchanged. Entry needs Rust's premium status. VAC is off. That is Valve's anti-cheat.
What map is 4Trust_____PvE_____DE/EN on?
Size 3,750 and seed 5678: the game generates the procedural map on 4Trust_____PvE_____DE/EN from them. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Join
How do you connect to 4Trust_____PvE_____DE/EN?
Check: join. Open Rust, press F1, then enter client.connect 176.57.174.158:29115. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you. Entry needs Rust's premium status.
