---
title: "Rust server lag or missing servers on Mac · Kilobat Guides"
url: "https://kilobat.app/guides/rust-network-lag-mac"
description: "Check Rust server location, browser queries, game ports and your Mac connection when a server is missing or laggy."
---

Websites and speed

# Rust server lag or missing servers on Mac

Rust servers can be run by different operators. A missing listing does not by itself mean your Mac is offline.

Applies to: Rust on macOS; check Facepunch and Steam’s current requirements. · Checked: 2 November 2026

## Symptoms

- The server browser shows few or no servers.
- One server is slow or cannot be reached.

## Likely causes

- **The server or its path.** Facepunch says geographic position, an attack on a server or packet loss can affect browser results.
- **Server discovery.** The client queries servers for details. A server that does not answer may not appear in the browser.
- **Local connection.** Wi-Fi interference or competing traffic can affect play.

## Check the browser and connection

1. Try other servers and another website to see whether the problem is specific to one server.
2. Check that you launched regular Rust, not the separate Staging Branch.
3. Facepunch says the browser collects servers from Steam, then asks each server for details.
4. Check the server’s actual location with its operator. Community servers need not use fixed official regions.
5. Compare Ethernet with Wi-Fi if possible. See [Test for packet loss on a Mac with ping](https://kilobat.app/guides/packet-loss-mac) for router and internet checks.
6. If you know a server’s address and port, Facepunch documents the in-game F1 console command `connect IP:Port`.

## How to fix it

1. Pause large transfers and repeat the test.
2. If Wi-Fi is the weaker path, see [Weak Wi-Fi signal on a Mac](https://kilobat.app/guides/weak-wifi-signal-mac).
3. For a missing server, ask its operator to check the server and query ports.
4. Check game and server versions before asking the operator or Facepunch support for help.

## With Kilobat

1. Try identifying the current match connection. macOS may not expose its address.

   ```
   kilobat games --match
   ```
2. A server that does not answer a ping may still accept game traffic.

## Questions

**Which server ports does Rust use?**

Facepunch documents UDP 28015 as the default game server port. The query port is separate and configurable. Server owners should check their actual configuration.

**Should a player forward UDP 28015?**

The documented server port is for hosting. A player should not add inbound forwarding merely to diagnose latency.

**Does Rust need a particular NAT type?**

The cited Facepunch sources do not state a universal NAT requirement. Ask the server operator about a specific connection problem.

**Are Rust servers fixed by official region?**

Server operators choose their hosting locations. Check the particular server rather than assuming one game-wide endpoint.

## Sources

- [Facepunch: No servers showing](https://support.facepunchstudios.com/hc/en-us/articles/360019452718-No-servers-showing)
- [Facepunch Rust Wiki: Creating a server](https://wiki.facepunch.com/rust/creating-a-server)
- [Facepunch Rust Wiki: Useful console commands](https://wiki.facepunch.com/rust/useful_commands)
- [Steam: Rust system requirements](https://store.steampowered.com/app/252490/Rust/)

Checked on 2 November 2026.

## Related guides

- [Test for packet loss on a Mac with ping](https://kilobat.app/guides/packet-loss-mac): Packet loss makes calls break up and pages stall.
- [Steam connection problems on Mac: checks for downloads and games](https://kilobat.app/guides/steam-connection-problems-mac): A Steam connection problem can come from the service, your network or software on the Mac.
- [Weak Wi-Fi signal on a Mac](https://kilobat.app/guides/weak-wifi-signal-mac): Signal strength and noise decide how fast and how stable the Wi-Fi link is.