Rust Stuck on "Receiving Data" or Loading? Server and Player Fixes

When players get stuck on "Receiving data" while joining a Rust server, the server is sending them the world state (every building block, deployable and entity near them) and the transfer is not finishing. If only one player hangs, it is usually their game cache or PC. If everyone hangs on the same server, the cause is on the server: a custom map that does not download, a huge entity count, or a plugin choking the join. The loading text tells you which stage failed, so start there.

The loading stages in order

Rust shows each step of a join at the bottom of the loading screen:

Ask the player for the exact stage, or watch the F1 console on your own PC while you join. The last line printed before the hang is the clue.

When only one player is stuck

This is the most common case. Everyone else joins fine, so the server is healthy.

1. Wait a few minutes once. The first join after a map wipe can sit on Loading level for a long time while the client builds the map and caches assets, especially on a hard drive instead of an SSD.
2. Clear the cached map. Close Rust, open the install folder (Steam > Rust > Manage > Browse local files) and delete the files in the maps folder. The client downloads or generates them again on the next join. A half written map file from an interrupted join causes endless Loading level.
3. Verify game files in Steam. Damaged asset bundles stall loading at random points.
4. Check RAM. Rust uses a lot of memory on large maps. Close browsers and other games. A PC with 8 GB often struggles, 16 GB is the realistic minimum for big servers.
5. Turn off VPNs. A connection that drops packets can stall Receiving data while the game still shows connected.

When everyone is stuck on Downloading map

This only happens on servers with a custom map, set with server.levelurl. The client must download the .map file from that link before it can load.

Check these:

• The link must be a direct download. Paste it into a browser. It should start downloading the .map file at once, not open a page with a download button. Dropbox links need dl=1 at the end, and many file sharing pages do not offer direct links at all.
• The file must still be there. Expired or deleted links leave every player stuck on Downloading map.
• It must be the same file the server loaded. If you replaced the map file on the host but not on the server, or the other way round, players get a mismatch. Update both together.

The map size, seed and custom maps guide covers setting up levelurl correctly.

When everyone is slow on Receiving data

Receiving data gets slower as the world fills up. Late in a wipe, a server with hundreds of thousands of entities can take a long time to send a player the area around a big base, and a player who logs out inside a huge compound has the longest wait.

Check the entity count in the server console:

serverinfo

Look at the entity count and the server FPS in the output. Compare it with earlier in the wipe. If it keeps climbing and joins keep getting slower, clean up:

• Make sure decay and upkeep are on (decay.scale 1 is the default), so abandoned bases disappear.
• Remove abandoned structures and spam builds with admin tools or a cleanup plugin.
• Lower the cap on deployables and building with a plugin if your server is modded with high gather rates, which build up entities fast.

The lag and low FPS guide goes deeper into entity counts and what is too many.

When a plugin hangs the join

On Oxide or Carbon servers, plugins run code when a player connects: loading their data, drawing UI, checking permissions. A plugin with an error at that point can leave players on Receiving data forever, or kick them right as they spawn.

1. Watch the server console while a player joins. Look for errors that name a plugin, like Failed to call hook 'OnPlayerConnected' or OnPlayerSleepEnded.
2. Unload the named plugin with oxide.unload <Name> (or c.unload <Name> on Carbon) and ask the player to join again.
3. If it works, update the plugin or contact its author. Plugins often break right after a monthly Rust update.

If there are no errors but joins still hang, unload plugins that draw big UI on join (welcome screens, shops, HUDs) one by one.

After an update or wipe

On force wipe day, the client and server both change. Common join hangs that week:

• The server is still on the old build while players have updated, or the other way round.
• Oxide or Carbon has not been reinstalled after the update, so plugins are half loaded.
• Players' cached maps from last wipe conflict with the new map. Clearing the maps folder fixes it.

Follow the steps in updating on force wipe day in order and most of these never happen.

A smoother option

Most join hangs come down to a heavy world, a broken plugin or a bad map link. On a GamezServers Rust server, the live console shows plugin errors as players connect, the file manager and SFTP let you swap a map file or a plugin in a minute, and one click backups mean you can roll back if a cleanup goes wrong. The game updates from the panel on wipe day. You can switch between vanilla, Oxide and Carbon from the panel too. See the Oxide server page or the Rust game page.

FAQ

How long should Rust take on Receiving data?

On a healthy server, a few seconds to under a minute. Several minutes on every join means the server has a very high entity count or a plugin problem.

Why am I stuck on Loading level on only one server?

That server uses a map your client has cached badly, often a custom map. Delete the files in the Rust maps folder and join again.

Does more server RAM fix slow loading?

Only if the server is running out of memory. The usual causes are entity count and plugins, which more RAM does not fix.

Can a player's base make loading slow for others?

Yes. Players who spawn near a huge compound receive all of it first. Decay and cleanup keep this in check.