Hurtworld Server Not Showing in the Server List? Fixes That Work
A Hurtworld server missing from the browser usually has a closed query port (12881), a port mismatch in -exec, a firewall block or browser filters. Fix each.
Updated Oct 7, 2026 · 5 min read
On this page
If your Hurtworld server is running but not in the in game server list, the usual cause is the query port: the browser finds servers through the Steam query port (12881 by default), and if that port is closed, mismatched or blocked by a firewall, the server is invisible even though it works. Test by pressing F1 in game and typing connect your.ip:12871. If that joins, the game port is fine and you only need to fix the query side. If it does not join either, the problem is the server or its network.
Hurtworld's browser has also always been a bit slow and flaky, so a server can take a while to appear after a restart. Give it a few minutes and a couple of refreshes before you start changing things.

Step 1: Join by address first
Direct connect is the fastest diagnosis. Press F1 to open the console in Hurtworld and type:
connect 203.0.113.10:12871
Use your public IP and the game port from your host command. Then read the result:
| Result | What it means |
|---|---|
| You join | Server and game port work. The query port or browser is the issue |
| Timeout from outside your home, works on LAN | Port forwarding or firewall |
| Timeout everywhere, even locally | Server not running, crashed, or still loading |
Step 2: Check the ports in your startup line
Hurtworld only uses the ports you tell it to. Look at your -exec string:
-exec "host 12871;queryport 12881;maxplayers 20;servername My Server"
hostis the game port players connect to.queryportis what the Steam server browser talks to.
Two mistakes are common here. One is leaving queryport out of the line after copying a short example, so the server uses a default you did not forward. The other is two servers on one machine sharing the same query port, where only the first one to start gets listed. Give each server its own pair, for example 12871 and 12881, then 12872 and 12882.
Step 3: Forward and allow the right ports
| Port | Protocol | Purpose |
|---|---|---|
| 12871 | UDP and TCP | Game traffic |
| 12881 | UDP | Steam server browser query |
Forward both to the local IP of the PC running the server, and make sure that local IP does not change (set a DHCP reservation in the router). Then check the firewall:
- On Windows, Defender Firewall usually asks the first time
Hurtworld.exeruns. If someone clicked Cancel, the server is blocked. Add inbound rules for both ports, or allow the program in Allow an app through Windows Defender Firewall. - On Linux, open both with
ufw allow 12871andufw allow 12881/udp.
Our port forwarding guide has the router side in detail.
Step 4: Rule out carrier grade NAT
If the forwarding looks right and outside players still time out, your internet provider may not give you a public IPv4 address at all. Log into the router and compare its WAN IP to the address a "what is my IP" site shows. If they differ, you are behind carrier grade NAT and nothing you forward will reach the server. Our guide on how to tell if you are behind CGNAT explains the test and the options.
Step 5: Check the browser filters
Before blaming the network, make sure the browser is not hiding the server. Clear the search box and switch off any filter or sort that could drop it, such as filters on player count or ping. A brand new server with zero players and a far away player with a ping limit are both easy to filter out. Search for a distinctive part of your server name rather than the whole thing.
Step 6: Give it time after a restart
Steam's master list only learns about a server after it has been running and answering queries for a little while. Right after a restart, or after changing the name, it can take several minutes to show up, and the Hurtworld browser sometimes needs a few refreshes before servers appear at all. If direct connect works and the ports are right, waiting is often the whole fix.
Step 7: Check the version
If the game updated and your server did not, players on the new client will not see or join it. Run SteamCMD with +app_update 405100 validate to update the server, then restart. If you run uMod, reinstall the matching build afterwards, because the update replaces its files. See our uMod install guide.
Quick reference
| Symptom | Most likely cause |
|---|---|
| Direct connect works, not in list | Query port closed or missing from -exec |
| Second server never listed | Two servers sharing a query port |
| Works on LAN only | Port forwarding, firewall, or CGNAT |
| Listed for you, not for friends | Their browser filters or ping limit |
| Vanished after a game update | Server out of date |

The hosted way around it
Every step above except the browser filters is about your home network. On a GamezServers Hurtworld server, the game and query ports are assigned and opened for you on a fixed address with DDoS protection, so the server lists as soon as it finishes loading. Server name, max players and owner SteamID are panel fields, and auto update keeps it on the current build. Friends can always fall back to connect with the address shown in the panel. For a full self hosted walkthrough, see our Hurtworld setup guide.
FAQ
What is the Hurtworld query port?
12881 by default, set with queryport in the startup line. It must be open over UDP for the server to appear in the browser.
How do I join a Hurtworld server by IP?
Press F1 to open the console and type connect followed by the IP and game port, like connect 203.0.113.10:12871.
Why does my server show for me but not for my friends?
You may be seeing it through your local network. Friends outside need the ports forwarded. Also ask them to clear browser filters such as hide empty servers.
How long does it take a new Hurtworld server to appear?
Usually a few minutes after it finishes loading. Refresh the browser a couple of times before changing settings.
Skip the setup. Your own Hurtworld server.
Then $9.99/mo. Just trying it? $2.50 for 3 days