RUST METRICSFlight deck · live data
Data live Servers11,841 Players73,926 Populated3,704 Fresh wipes 3 h221 Scan5 min
‹ All servers188.226.117.47:28015
Offline Full Queue Fresh wipe Wipe due No query

MapBaker

Offline 188.226.117.47:28015 checked 8d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 0 /1

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,423top 69%
Last wipe8d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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 4 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k4 Oct7 Oct10 Oct22 Oct25 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 21 Oct, 12:31 UTC8d ago 0 – 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Reset cycle

What happens on MapBaker when wipe day comes?

The busiest point of its recent wipes drew 0 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does MapBaker wipe, and when?

Its rhythm cannot be told from the wipes of MapBaker on record: there are too few. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 8 days 1 hours ago.

Tags

How should you read the tags on MapBaker?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from MapBaker. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does MapBaker appear in Rust Metrics lists and filters?

These Rust Metrics lists carry MapBaker: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

What position does MapBaker hold among Rust servers?

Player hours over seven days put MapBaker at #15,423, in the top 69% of all ranked servers.

What player count does MapBaker carry?

Reading for MapBaker: offline at this moment; last seen 8 days ago.

Operator and location

Where does MapBaker sit?

No region tag on MapBaker. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 188.226.117.47:28015.

What Rust version is MapBaker on?

Rust network protocol 2634 and build 166652 on Windows is the build MapBaker runs. Matching protocol is required to join. Let Steam update your game.

How reliable is MapBaker, and is it online now?

Check: connection. MapBaker is offline at this moment. Last contact was 8 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 4 October 2026, recorded by Rust Metrics.

Rules and settings

How is MapBaker configured, and what rules are in force?

Reading the name gives no gather rate for MapBaker. No limit is set beyond the default. Groups take up to 8 players. survival, standard play of gathering, building and raiding — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Under Community in the server browser you will find it. Check: anti-cheat. VAC, Valve's system, is on.

What map is MapBaker on?

Size 1,000 and seed 1337: the game generates the procedural map on MapBaker from them. View it on RustMaps from this page: matching size and seed give an identical map.

How to join

How can you get onto MapBaker?

Press F1 in Rust and enter client.connect 188.226.117.47:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs166652,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166652
Build Game build reading: 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.