---
title: Rust Server Status Checker: Pop, Map & Latency
description: Rust server status checker: population as Rust's browser shows it, map, version and latency from three regions. Wrong port? It finds the query port. Free.
canonical: https://watchfor.io/rust-server-status
---

[Back to all free tools](/free-tools)

# Rust Server Status Checker

Check a Rust server's population, map, version and latency from three regions, counted the way Rust's own server browser counts them. Typed the game port? The checker tries the query ports hosts use (28015–28018) and tells you which one answered.

Result

No result yet

Fill in the form above and run it — the result appears here.

One check is a snapshot

## Monitor your Rust server 24/7

A monitor runs this same status query every minute, confirms an outage from several locations before anyone is woken up, and keeps what you just saw as history.

- Uptime and latency history From up to 20 locations in seven regions (how many depends on the plan), so 'it lags for Australia' is a number.
- Peak players and busy hours Player count over time and a heatmap of when people actually play, in your time zone.
- Map rotation and versions Which maps the server ran and when the version changed, without a plugin.
- Alerts that mean something Down (confirmed from several locations), high latency, empty, full, password turned on, VAC off.
- Discord without a bot A channel webhook, nothing to invite. Telegram, Slack and email work the same way.
- A status page for your community Players, map and busy hours on your own page, with a Join button for Steam and FiveM.

Game server monitoring is included from the [Starter plan](/pricing). This checker stays free.

[Start monitoring](/auth/sign-up)[How it works](/game-server-monitoring)

Only run these tools against systems you own or are authorized to test. Using them to scan or probe systems without permission violates our [Terms](/legal/terms).

## Server status by game

[Every game in one checker](/game-server-status-checker)

- [Minecraft server status](/minecraft-server-status)
- [CS2 server status](/cs2-server-checker)
- [FiveM server status](/fivem-server-status)
- [Garry's Mod server status](/gmod-server-status)
- [DayZ server status](/dayz-server-checker)
- [Valheim server status](/valheim-server-status)
- [Project Zomboid server status](/project-zomboid-server-status)
- [7 Days to Die server status](/7-days-to-die-server-status)
- [Enshrouded server status](/enshrouded-server-status)
- [SA-MP server status](/samp-server-status)
- [MTA:SA server status](/mta-sa-server-status)

[How Rust server monitoring works](/game-server-monitoring/rust)

## What is Rust Server Status Checker ?

Rust servers answer Steam's server query on their query port — and that is where most status checks go wrong: the port players join (28015 by default) is usually not the one that answers. Enter whichever you have; when it's silent, the checker tries the query ports hosts use and tells you which one answered.

The population is read the way Rust's own browser reads it, from the server's cp / mp tags, not the raw count byte that caps at 255. You also get the map, version, the player list when the server shares it, and the latency from three regions — handy on wipe day.

## How it works

The checker asks the server the question its own server browser asks — no plugin, no RCON, nothing installed:

- 1 Pick the protocol from the game — Steam games answer the A2S query over UDP, Minecraft Java the server list ping over TCP (after following the _minecraft._tcp SRV record, like the game), Bedrock its unconnected ping over UDP, FiveM and RedM their HTTP endpoints, SA-MP and open.mp the SA-MP query, MTA the All-Seeing Eye query.
- 2 Ask from three regions at once — The nearest probe location and two others on different continents send the same query in parallel. Each reports whether a valid status came back and how long the round trip took.
- 3 Find the port when the one you typed is silent — Many games answer queries on a different port than players join on. When nothing answers, the nearest location tries the ports that game's servers usually use — at most four ports in all, taken from the game's own table, never a scan — and tells you which one answered.
- 4 Read what the server says about itself — Name, players and slots, bots, map, version, password and VAC flags, the MOTD, and the player list when the server shares one. Names, scores, play time and ping only — never player identifiers or addresses.

Identical checks within 45 seconds share one answer, and each server can be checked a few times a minute by everyone together, so the tool can't be used to flood a server with queries.

## When you'd use it

### "Is the server down or is it just me?"

A player says they can't find the server. Check it from three regions: if all three get the status, the problem is on the player's side (their network, an outdated client, a full server); if none do, it's the server.

### After a restart, wipe or update

You pushed a new map or version. Confirm the server is back, on the map you expect, with the version players will need — before the Discord fills with questions.

### Finding the query port

Your host's panel shows the game port and the server browser can't see the server. Enter the address with any port; the checker tries that game's usual query ports and tells you which one answered — the one a server list or a monitor needs.

### Choosing a host location

The latency from three continents — what a server browser shows as ping — tells you who will play comfortably. A server at 25 ms from Frankfurt and 180 ms from Virginia is a European server, whatever the listing says.

## Reading the result

### Population

From the same tags Rust's server browser shows. If the raw A2S count differs (some servers inflate it), the checker notes both.

### Map

Procedural maps report Procedural Map ; custom maps report their own name — the quickest way to confirm a wipe went out with the right map.

## Rust ports

Rust's ports, from the launch line:

Setting Default What it is

+server.port 28015 Game port (UDP) — what players join

+server.queryport set by host Steam query port; hosts use 28015–28018 and others

+rcon.port 28016 RCON — not a query port, never asked

## Common pitfalls

### Checking the game port instead of the query port

Rust, DayZ, ARK, Valheim and MTA answer status queries on a port of their own. A silent game port proves nothing; the checker tries the usual query ports, and your host's panel lists the real one (Rust: +server.queryport ).

### A DDoS filter that drops queries from data centres

Some hosts filter UDP queries that don't come from residential addresses. The server then looks offline to every server list while players still join. If all three regions get no answer but you can play, ask the host to allow the query.

### Treating 'online' as 'joinable'

A status reply means the server process answers. Whether players get in also depends on the game port, the password, whitelists and mods. For FiveM in particular, the HTTP answer doesn't prove the UDP game port is open.

### Expecting player names everywhere

Counts always come back; names don't. CS2 shares them only with host_players_show 2 , Bedrock never sends a list, SA-MP stops at 100 players, many Minecraft networks replace the sample with text. The checker says which case you are looking at.

## Monitor your Rust server 24/7

This checker answers for this minute. A monitor asks the same question every minute from several locations, keeps the history and tells your Discord when the answer changes. Game server monitoring is included from the [Starter plan](/pricing); the checker stays free.

[Start monitoring](/auth/sign-up)[How it works](/game-server-monitoring)

## Frequently asked questions

What is my Rust server's query port? Whatever +server.queryport says in the launch line; hosts often use 28016, 28017 or 28018. Enter the game port if that's all you have — the checker tries the usual query ports and reports the one that answered.

Why does the player count differ from the raw number? Rust reports its real population in the cp / mp tags, which is what the in-game browser shows. The A2S player byte stops at 255 and some servers inflate it; the checker uses the tags.

Can I check a server on console (PS5 / Xbox)? No. Console Rust servers aren't reachable with the Steam query — this is for PC servers.

Will checking my server affect players? No. A status query is one small UDP packet, the same thing every server list sends many times a minute.

Can I get a Discord alert when my Rust server goes down? Yes — with a game server monitor. It runs this same query every minute from several locations, confirms an outage before it alerts, and posts to a Discord channel through a webhook (no bot to invite), or to Telegram, Slack or email. It also tracks players, maps and latency over time and can give your community a status page with a Join button. Game server monitoring is included from the Starter plan; see [pricing](/pricing).

Is the checker free? Yes, with no login: 10 checks an hour per IP address, and each server can be checked a few times a minute by everyone together, so nobody can use it to flood a server.

## Related network tools

- [Game Server Status CheckerCheck any game server the way its own server browser does — CS2, Rust, Minecraft Java and Bedrock, FiveM, RedM, SA-MP, MTA, DayZ, Valheim and 20+ more. See the name, players and slots, map, version, password and VAC, the player list, and the latency from three regions at once. Wrong port? It tries the game's usual query ports and tells you where the server answered.](/game-server-status-checker)
- [PingPing any host or IP address online from a real server — round-trip time (min / avg / max), jitter and packet loss, in seconds.](/ping-test)
- [TracerouteRun a traceroute online — trace the network path to any host hop by hop, with packet loss and average latency at each hop (MTR-style).](/traceroute-online)
- [Port CheckerCheck whether a TCP port is open on any host or IP from the public internet, and optionally grab the server banner.](/port-checker)

---

Canonical page: https://watchfor.io/rust-server-status · Site guide: https://watchfor.io/llms.txt
