Insurgency Sandstorm Server Not Showing in Browser: 7 Fixes
Sandstorm server running but missing from the server browser? Check the GSLT, Game Stats token, query port 27131, map and scenario, filters and versions.
Updated Oct 7, 2026 · 7 min read
On this page
An Insurgency Sandstorm server that runs but never shows in the server browser almost always has one of four problems: a missing or wrong Steam server token (GSLT), no valid Game Stats token, a blocked or wrong query port (27131 UDP by default), or a server that never finished loading its map. Before changing anything, join it directly from the console with open IP:port. If that works, the server is fine and the problem is listing or filters.
First, test with a direct connect
This one step tells you which half of the problem you are in.
- In Sandstorm's settings, turn on the console.
- Press
~from the main menu. - Type
open 203.0.113.10:27102, using your server's IP and game port, and add?Password=yourpasswordif it has one.
| Result | What it means |
|---|---|
| You join | The server works. The browser listing is the problem. Go through fixes 1 to 3 and 6 |
| Connection times out | Nothing is reaching the game port. Check the server is running and the ports (fix 3 and 4) |
| You join a loading screen that never ends | The map or a mod failed to load (fix 4 and 5) |
| Version mismatch message | Server and client are on different builds (fix 7) |
Fix 1: Check the GSLT
The Steam game server login token tells Steam your server is legitimate. Without one, or with a bad one, Steam does not list it.
- Wrong app ID. This is the most common mistake. The token must be made for app 581320, the game itself, at steamcommunity.com/dev/managegameservers. The dedicated server download is app 581330, and a token made for that ID does not work.
- Token shared between servers. Each token can only be used by one running server. If a test server and your real one share a token, one of them drops off.
- Token reset or banned. On the same Steam page you can see whether your token is still valid and regenerate it. Paste the new one into
-GSLTToken=and restart.
Your Steam account also has to meet Steam's rules for creating tokens, such as not being limited. If the page will not let you create one, that is why.
Fix 2: Check the Game Stats token
Sandstorm's own stats service wants a second token, made by signing in with Steam at gamestats.sandstorm.game. It goes on the launch line with both of these:
-GameStats -GameStatsToken=YOUR_TOKEN
Leaving out -GameStats is an easy slip: the token alone does nothing. Without a valid Game Stats token, players also stop earning XP on your server, so it is worth fixing even if the server happens to appear.
Tokens can stop working, for example after you regenerate one on the site. If XP stopped and the server vanished from the list at the same moment, make a fresh token and restart.
Fix 3: Check the query port
The browser does not talk to your game port. Steam asks the server for its details on the query port, set with -QueryPort=, and the default is 27131 UDP. The game port is 27102 UDP by default.
| Port | Protocol | Used for |
|---|---|---|
| 27102 | UDP | Players joining (-Port) |
| 27131 | UDP | Steam listing and the browser (-QueryPort) |
If the query port is blocked by a firewall, not forwarded on your router, or used by another server on the same machine, the server runs and accepts direct connects but never appears. At home, forward both as UDP; our port forwarding guide walks through it. Two servers on one machine need different game and query ports each.
Fix 4: Make sure the map actually loaded
A server that is stuck loading is never listed. The console tells you when the server is really ready: look for this line after a start:
LogGameState: Match State Changed from LoadingAssets to WaitingToStart
If it never appears, the usual cause is a map and scenario that do not belong together. The launch line starts with both, such as Canyon?Scenario=Scenario_Crossing_Checkpoint_Insurgents, and the scenario must exist for that map. A Checkpoint scenario name on a map that only has versus scenarios, or a typo in the name, leaves the server stuck. Use a scenario from New World Interactive's server admin guide and copy it exactly, capital letters included.
Fix 5: Rule out mods
Modded servers download their mods from mod.io before loading the first map. If a mod fails to download, has been removed from mod.io, or needs a mod.io account the server is not signed into, the server never reaches a joinable state.
To test, remove -Mods from the launch line and restart. If the server appears, the problem is in your mod setup. Add mods back one at a time. Our guide to installing mods on a Sandstorm server covers the mod.io account step that catches most people.
Fix 6: Clear the browser filters
The in game browser hides plenty by default. Before assuming the server is broken:
- Switch to the Community tab rather than official servers.
- Turn off filters that hide full, empty or passworded servers.
- Clear mod, map and mode filters. A co-op server will not show while you filter for Push.
- Search for a distinctive word from your server name rather than scrolling.
- Give it a few minutes after a restart. New servers do not appear in the list the second they finish loading.
If a friend in another country can see it and you cannot, the cause is filters or ping limits on your side, not the server.
Fix 7: Match the versions
After a Sandstorm update, players' games update through Steam right away, while a server only updates when someone runs SteamCMD and restarts it. Until then, the server is on the old build and does not show up for players on the new one.
Update the server with app 581330 and restart:
steamcmd +login anonymous +app_update 581330 validate +quit
Remember that PC servers are for PC players only. Console versions of Sandstorm never see PC servers, whatever you do.
A quick checklist
| Check | Good |
|---|---|
| GSLT made for app 581320, unique to this server | Yes |
-GameStats -GameStatsToken= both on the launch line |
Yes |
| Query port 27131 UDP reachable, game port 27102 UDP reachable | Yes |
Console shows WaitingToStart after the map loads |
Yes |
| Server and players on the same build | Yes |
| Browser on Community, filters cleared | Yes |
Skipping the token and port problems
Most of this list is setup work that a host does for you. On an Insurgency Sandstorm server from GamezServers, the Steam server token is created for you, there is no router to forward, and auto update keeps the server on the current build when it restarts. You paste your Game Stats token into the panel, pick the default map and scenario, and the server is live in minutes with DDoS protection. If you would rather keep self hosting, the Sandstorm hosting guide covers the full launch line, and our admin commands guide covers running the server once players find it.
FAQ
Why can I join my Sandstorm server by IP but not see it in the browser?
The server works, so the listing is the problem: usually a wrong or missing GSLT, a missing Game Stats token, a blocked query port 27131, or a browser filter hiding it.
What app ID do I use for the Sandstorm GSLT?
581320, the game's app ID. The server download is 581330, which does not work for tokens.
What is the Insurgency Sandstorm query port?
27131 UDP by default, set with -QueryPort. The browser listing depends on it, so it must be open even if players connect on 27102.
Why did my server disappear after an update?
The game updated for players but the server is still on the old build. Update app 581330 with SteamCMD and restart the server.
Do I need the Game Stats token for the server to show?
It is what makes players earn XP on your server, and missing tokens are a common cause of servers not listing properly. Use one on any server you want people to find.
Skip the setup. Your own Insurgency: Sandstorm server.
Then $9.99/mo. Just trying it? $2.50 for 3 days