mischers3
Offline 46.114.194.36:28015 checked 44d ago
Server instruments
no direct query in 48 hoursPlayers now
0% 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 bestWipe 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- 234/250
- 14/250
- 17/250
- 142/200
- 46/200
- 40/100
Quick answers
from the figures on this pageWipe schedule
What wipe timing does mischers3 follow?
Its rhythm cannot be told from the wipes of mischers3 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. 53 days 22 hours ago the current world was made.
Tag meanings
How should you read the tags on mischers3?
These are the tags mischers3 publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): Slots: 10; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Protocol 2633: join only on the same game version; cs162929 (Build): Game build reading: 162929; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does mischers3 appear in Rust Metrics lists and filters?
Rust Metrics lists featuring mischers3: Rust community servers: live readings. Check: filters. On the server list it appears under these: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Player count
How full does mischers3 get?
mischers3 is not responding; status offline, last seen 44 days 14 hours ago.
Server
Which location does mischers3 run from?
No region tag on mischers3. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 46.114.194.36:28015.
What Rust version is mischers3 on?
Version check: Rust network protocol 2633 and build 162929 on Windows, run by mischers3. Matching protocol is required to join. Let Steam update your game.
How reliable is mischers3, and is it online now?
mischers3 reports offline. The last reading came 44 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 13 September 2026.
Rules and settings
What settings and rules apply on mischers3?
Check: gather rate. The name mischers3 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. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Check: anti-cheat. VAC, Valve's system, is on.
What map is mischers3 on?
Procedural map on mischers3, made by the game's generator.
How to join
How do you connect to mischers3?
Press F1 in Rust and enter client.connect 46.114.194.36:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.