Rust Server Ports: Complete Guide to Default Ports, Setup & Fixes (2025)

When setting up a Rust server, one of the most common questions server owners face is “Which ports does a Rust server use?”.

Getting your ports right is critical. If they’re misconfigured, players won’t be able to connect, your server won’t appear in the community list, and you might run into problems with RCON or Steam connectivity.

In this guide, we’ll cover:

• The default Rust server ports and what they do
• TCP vs UDP requirements
• How to set up port forwarding on your router or firewall
• Common Rust server port issues and how to fix them
• Advanced tweaks and best practices for server security

Whether you’re running a Rust dedicated server from home or hosting with a provider, understanding ports is essential to keeping your server online and visible.

What Are Rust Server Ports?

In networking, a port acts as a “doorway” through which data flows between computers. Every online service uses specific ports to send and receive information.

For Rust, this means:

• Game traffic (player connections)
• Query traffic (server listing visibility)
• RCON traffic (remote console management)
• Steam traffic (authentication and updates)

If any of these ports are blocked or misconfigured, your Rust server will run into connectivity issues.

Default Rust Server Ports (Quick Reference)

Here are the main ports you need to know when running a Rust server:

⚡ Tip: Always make sure these ports are open in both your firewall and your router’s port forwarding rules.

Rust Game Port (28015 UDP)

The Rust game port is the most important one. By default it’s set to 28015 UDP.

This port handles all direct game traffic:

• Player logins
• In-game actions and events
• World synchronisation between client and server

If this port is blocked, players won’t be able to connect to your server, even if it appears in the server browser.

Change it with:

+server.port 28015

Rust RCON Port (28016 TCP/UDP)

RCON (Remote Console) allows you to control your Rust server remotely. By default, RCON uses 28016.

Through RCON you can:

• Manage players (kick/ban)
• Run server commands
• Monitor performance
• Install plugins or manage mods

Most RCON tools require TCP, but some configurations also listen on UDP. Always allow both to be safe.

Change it with:

+rcon.port 28016
+rcon.password "YourStrongPassword"

Rust Web RCON (28017 TCP)

Some Rust setups also use 28017 TCP for Web RCON, which lets you manage the server via a web interface or certain control panels.

Not all servers need this, but if your host or tool mentions Web RCON, this is the port it usually uses.

Rust Query Port (27015 UDP)

The query port is what allows your server to appear in the Rust server browser under “Community Servers.”

By default, it’s set to 27015 UDP.

If this port isn’t open:

• Your server will run, but players can only connect via direct IP.
• Your server won’t show up in the Rust community list.

Change it with:

+server.queryport 27015

Steam Ports for Rust

Besides the main Rust ports, you also need to allow certain Steam ports for authentication and updates. These include:

• TCP 27014–27050 – Steam downloads and updates
• UDP 27000–27031 – Steam game traffic
• UDP 4380 – Additional Steam connectivity

Most hosting providers already have these open. If you’re self-hosting, make sure your firewall/router rules cover them.

How to Open Rust Server Ports (Port Forwarding)

If you’re running a Rust server at home or on a VPS, you’ll need to forward the right ports.

Step 1: Log Into Your Router

• Access your router admin panel (usually 192.168.1.1 or 192.168.0.1).
• Find Port Forwarding or NAT Rules.

Step 2: Add Port Rules

Forward the following:

• 28015 UDP – Game traffic
• 28016 TCP/UDP – RCON
• 27015 UDP – Server query

Example entry:

Service: Rust Game
Port Range: 28015
Protocol: UDP
IP Address: [Server’s internal IP]

Step 3: Save and Reboot

• Save changes
• Restart router and server

Rust Server Firewall Setup

Even with ports forwarded, your firewall might block traffic.

On Windows (Windows Defender Firewall)

1. Open Windows Defender Firewall
2. Go to Advanced Settings
3. Add new Inbound Rules for:
   • 28015 UDP
   • 28016 TCP/UDP
   • 27015 UDP

On Linux (UFW Example)

sudo ufw allow 28015/udp
sudo ufw allow 28016/tcp
sudo ufw allow 28016/udp
sudo ufw allow 27015/udp

Common Rust Port Issues & Fixes

1. Server Not Showing in Browser

• Likely 27015 UDP isn’t open.
• Double-check firewall/router rules.

2. Players Can’t Connect

• Check 28015 UDP is open.
• Test direct connection:client.connect YOUR.IP:28015
  

3. RCON Not Working

• Confirm 28016 TCP is open.
• Make sure you’re using the correct password.

4. Port Conflicts

• If another service is using the same port, Rust won’t bind.
• Change ports in your server.cfg or launch parameters.

Advanced Port Configuration for Rust Servers

If you’re hosting multiple Rust servers on the same machine, you’ll need to use different ports for each instance.

Example:

• Server 1: +server.port 28015 +server.queryport 27015 +rcon.port 28016
• Server 2: +server.port 28025 +server.queryport 27025 +rcon.port 28026

Always keep at least 10 port numbers apart to avoid overlap.

Security Best Practices

• Never leave RCON exposed without a strong password
• Use a firewall to limit RCON access to your own IP
• Consider a DDoS protection solution (Rust servers are frequent targets)
• Avoid hosting multiple critical services on the same machine with default ports

FAQs About Rust Server Ports

Do I need to forward ports for a hosted Rust server?
No – if you use a game server hosting provider like EUGameHost, all required ports are already configured.

What is the Rust server port by default?
The default Rust game port is 28015 UDP.

Why is my Rust server not showing up?
Most likely your query port (27015 UDP) isn’t open or your firewall is blocking it.

Can I change the default Rust ports?
Yes, use +server.port and +server.queryport in your launch parameters.

Which port does Rust RCON use?
By default, 28016 TCP/UDP.