RustSettings & Admin
Teleport on Your Rust Server
Teleport players as an admin with Rust commands, then give players /home and /tpr with the NTeleportation plugin.
This guide covers the teleport commands Facepunch documents for admins, then how to give your players teleports such as /home to a base or /tpr to a friend with the NTeleportation plugin.
Plugin checked against NTeleportation 1.9.6 by nivex (released August 2026) on uMod, October 2026. The built-in commands come from Facepunch's Useful Console Commands wiki page.
Teleport a player as an admin
Join your server as an owner or moderator, press F1 to open Rust's console in game and type:
teleport 76561198000000001 76561198000000002The wiki says that with two players entered, the first is teleported to the second, and that a Steam64ID is more accurate than a name. Run status in the same console to see each player's ID. Rust server.cfg and admin commands lists the other everyday admin commands.
Teleport yourself
These commands, also typed into the F1 console, act on your own character. All of them need admin:
Give players teleports with NTeleportation
- Open the Plugins tab, search the Store for NTeleportation and press Install. How to install Oxide/uMod plugins on your Rust server has the details, including switching a plain server to Oxide first.
- On Oxide, a plugin installed onto a running server stays unloaded until you Restart the server or type
oxide.load NTeleportationin the Console. On Carbon it loads by itself. Look forLoaded plugin NTeleportationbefore you go on. - Players need permissions before the commands work for them. Grant the two main ones to everybody:
oxide.grant group default nteleportation.home
oxide.grant group default nteleportation.tprThose are the Oxide commands. On Carbon, the same two lines start with c.grant instead:
c.grant group default nteleportation.home
c.grant group default nteleportation.tprOn Carbon the oxide.grant form prints nothing and changes nothing.
Permissions only exist once the plugin has loaded, which is why step 2 comes first. Owners and moderators can use the admin commands without a permission, because the plugin's Usable By Admins and Usable By Moderators settings are both true by default.
What players can type
A home has to be on a foundation: the plugin tells you "You can only use a home location on a foundation!", and that you or a friend must own the house. Out of the box each player may save 2 homes, and /home and /tpr each have a 600 second cooldown, a 15 second countdown and a daily limit of 5. Change them in the plugin's Home and TPR settings: on Installed, press Config on NTeleportation, then Save and Reload plugin.
Admin commands from the plugin
In chat, admins get /tp "player" to go to a player, /tp "player" "target" to move one player to another, /tp x y z for coordinates, and /tpsave "name" with /tpl "name" to save and use a named location.
Run /tphelp in chat to see which command groups the plugin offers, and /tpinfo to see the cooldowns that apply to you.
Common problems
- "You are not allowed to use this command!" The player lacks the permission. Grant it as above.
- The permission "doesn't exist". The plugin hasn't loaded. Restart or run
oxide.load NTeleportation(Oxide) orc.load NTeleportation(Carbon; it usually loads by itself). - A teleport is refused or interrupted. Players are told "You can't teleport from a safezone!", "You can't teleport while seated!" or "Your teleport was interrupted!". The switches behind these are under Settings > Interrupt TP in the plugin's config, and Safe Zone, Mounted and Hurt are all true by default.
Related guides

Set the Message of the Day on Rust
Set the server description, greet players on spawn with Welcomer and repeat chat announcements with Advert Messages on Rust.
4 min read
Change Crafting Speed on Your Rust Server
Set a crafting speed multiplier on Rust with the Crafting Controller plugin, with its commands and permissions, plus the game's craft.instant.
4 min read
Change the Time of Day on Your Rust Server
Set the in-game clock with env.time, hold it with env.progresstime, and use two scheduled commands to keep it after a restart.
4 min read