guide · player lookup
How to look up a FiveM player
Names change: the in-game name is picked at connect, a Discord username takes two clicks to replace. What does not change are the identifiers — the identity traces a player leaves when they connect to your server. This guide covers what each identifier is, where it appears, and what each one can actually tell you.
The identifiers a server actually sees
When a player connects, a FiveM server sees not one name but a list of identifiers. They are not all equally reliable:
license
A hash of the Cfx.re account and the most stable entry on the list: present on every connect, unchanged whether Steam is running or not. It is the backbone of tracking a player across servers — which is why ban archives key on it.
steam
The SteamID64 in hexadecimal — but it only appears if the player launched the game with Steam running. Its absence proves nothing; its presence hands you a public Steam profile.
discord
The player’s Discord user ID, attached when Discord is open on the desktop. It is the most informative identifier, because a readable history lives on the Discord side: account age, server memberships, roles.
xbl / live (arşivde)
Xbox Live and Microsoft account identities. Note: they are no longer listed in Cfx.re’s current identifier table; they appear in older connection and ban records. Argos keeps them in the archive and uses them in reverse lookup, because they still help match an older record — players change their Windows account far less often than their Steam one.
fivem
The numeric ID of the Cfx.re forum account. Missing for players without one; for the rest, it is a door into their forum history.
ip
You see the IP of a player connecting to your own server in your own console — that is normal. But an IP is a poor key for identity: it rotates on home connections, is shared on mobile networks, and changes in a second with a VPN. Argos never exposes IPs.
Where to find them on your own server
You do not have to hunt for them — they are already recorded. If you run txAdmin, the player profile page lists every identifier. The server console prints the same list on every connect. Frameworks like ESX and QBCore key their player rows on the license; your users table is your identifier archive.
The habit that pays off: when you ban a player, store their identifiers alongside the reason. Names change and accounts get deleted; the license stays. Six months later, the answer to “is this new account the old cheater” is the row you saved that day.
What each identifier can tell you
Steam → a public profile
Convert the hex to a SteamID64 (steamid.io does it in one step) and append it to steamcommunity.com/profiles/. Account age, playtime, VAC status and alias history are open on most profiles. A private profile is a data point too.
Discord ID → a readable history
The account creation date is computed from the ID itself. On top of that come memberships in monitored communities, customer roles in cheat shops, and name and avatar history — the signals covered in detail in the whitelist guide.
License → cross-server relationships
There is no public directory; its value emerges in shared archives. If the same license appears in another server’s ban record, the “clean” account in front of you is that record’s continuation. No single server can build that relationship from its own data alone.
Character name → the weakest link
Search by name exists, but keep it for last: names get borrowed, imitated and collided. A name match is a starting point; always rest the decision on a hard identifier.
Where Argos fits — and where it does not
Argos collapses the scattered part of the steps above into one query. Searching by Discord ID is free: account history, monitored-community memberships, ban records, a risk score. The Premium Identify tool works in reverse — when all you hold is a license, Steam or Xbox Live identifier, or a character name, it finds the Discord accounts carrying that trace in the archive. The archive currently spans 400,000+ tracked identities and 110,000+ ban records.
What Argos is NOT
Argos is not a directory of all of FiveM. It sees the communities it monitors and the ban archives of co-operating servers; an empty result means “no record”, not “innocent”. No query ever shows an IP address. And nobody’s computer is scanned — what is read is identity relationships and history, not machines.
What you can type in, and what comes back
You hold one value and want to know what you can do with it. The answer depends on which kind of value you have — and mixing the kinds up is the most common reason a lookup returns nothing.
- A Discord ID (a 17–19 digit number) — the most direct input. Screened against shared ban records and alt-account links, and the form the no-account batch tool takes.
- A license or license2 value — a Rockstar licence hash. Reverse searchable inside the records that captured it. The two can be the same value and can differ, so “license2 is empty, therefore no record” is wrong.
- A fivem value — the Cfx.re account id, an integer. This is what a forum thread asking “what is my Cfx.re ID” means, and it is not the same thing as a licence.
- A Steam hex (steam:110000…) — convert it to decimal and it becomes a SteamID64 that opens a profile. That identifies the Steam account, not a FiveM account.
- A discord: value from a connect log — that is already a Discord ID. Drop the prefix and screen it directly.
What comes back: a record, or the absence of one — never an identity resolution. No input type here returns a name, an avatar or an IP. And each type resolves into a different account universe: a licence match is not a Discord match, and a Steam match is not a Cfx.re match.
Frequently asked
Can I find who a license identifier belongs to?
Not on its own — a license is a hash of a Cfx.re account and there is no public directory of them. What you can find is a relationship: if the same license appears in a ban record on another server, or has been seen alongside a Discord account, that record leads you to the identity. Argos’s Identify tool does exactly that: it searches the archive’s ban records and link data for the identifier.
Can I get a player’s IP address?
Not through Argos — under any circumstances. IP addresses that arrive with ban records are never sent to the client; they are only counted as present or absent. You already see the IPs of players connecting to your own server in your own console; there is no legitimate use for hunting the IP of a player on someone else’s server.
How do I turn a Steam hex identifier into a profile?
FiveM writes the Steam identity in hexadecimal: steam:110000... Convert that value to decimal and you get the SteamID64 starting with 7656119; steamcommunity.com/profiles/<SteamID64> goes straight to the profile. Converters like steamid.io do this in one step.
Will the person know they were looked up?
No. A lookup runs only against Argos’s own archive; no request touches the target’s Discord account, Steam profile or game, and nobody is notified.
If the result is empty, are they clean?
No — an empty result means “no record in the monitored communities and shared archives”, not “never cheated”. Argos sees the communities it monitors and the ban archives of co-operating servers, not all of FiveM. Read an empty result together with the other signals: account age, server memberships, behaviour.
Are these lookups free?
A Discord ID lookup is free — 5 per day on the free tier. Reverse search by identifier (license, Steam, Xbox Live, character name) is a Premium feature, because it runs across the whole archive. Xbox Live is still supported in reverse lookup even though Cfx.re no longer lists it among the identifiers a connection presents — older records contain it.
How do I find a FiveM player by their ID?
If you have a Discord ID, query it directly: the records are tied to the Discord identity, so you get where the player has been seen and whether they carry a ban record. If all you have is an in-game trace (license, Steam, character name), that needs a reverse search, which matches the identifier against the records in the archive and works back to a linked Discord account.
How do I find my own FiveM identifier?
An identifier comes from what the server reads at connect time, not from anything on your machine, so there is no client-side "list my identifiers" screen. On your own server you can read the output of `GetPlayerIdentifiers` or your connect logs. You cannot see your identifier as recorded on someone else’s server — that server’s logs are not open to you.
How do I check a FiveM player?
By establishing identity and searching the records. The strongest keys are the license and the Discord ID; a record found through either is hard evidence. A name similarity is only a signal — a reason to investigate, not a reason to punish. Running the check as the player connects lets you decide before they are inside.
What does a FiveM identifier look like?
It depends on the type: license and license2 are long hashes tied to a Cfx.re account, Steam arrives in hexadecimal (`steam:110000…`) and converts to a SteamID64, and the Discord identifier is simply the Discord user ID. All of them are read at connect time and are unaffected by the player changing their display name — which is exactly why you query an identifier rather than a name.
What are the FiveM identifier types and how do they differ?
Cfx.re’s identifier table lists six: `license` and `license2` (Rockstar Online Services license; license2 is the ROS license for players using Steam and can be the same value as license), `steam` (Steam ID, hexadecimal), `discord` (Discord user ID), `fivem` (Cfx user ID) and `ip` (IPv4 address). Which ones arrive depends on the player’s linked accounts; none is a name, and none changes when the player renames.
How do I find someone’s FiveM account?
Start from whatever identity you already hold. If you have their Discord ID, query it directly — the records are keyed to the Discord identity. If you only have a game trace (license, Steam hex, character name), a reverse search matches that identifier against the archive and works back toward a linked Discord account.
What can I learn from someone’s FiveM license?
A license on its own resolves to nothing public: no directory maps a license to a person. What it gives you is a relationship — whether the same license appears in a ban record on another server, or has been seen alongside a Discord account. That link is what turns an anonymous hash into an identity, and it exists only if a community recorded it.
How do I convert a FiveM Steam hex identifier to a SteamID?
FiveM writes Steam in hexadecimal, for example `steam:110000112345678`. Convert that hex value to decimal and you get the SteamID64 beginning with 7656119; `steamcommunity.com/profiles/<SteamID64>` opens the public profile. Converters such as steamid.pro or steamid.io do it in one step. This works because the hex value IS the account number — it is a conversion, not a lookup.
What is a cfx.re ID?
It is the `fivem` identifier: a Cfx.re account id, and the "Cfx.re ID" a forum thread asking "what is my Cfx.re ID" means. It is an integer, it is read from the connect log, and it is a different thing from a license — a match on one is not a match on the other. You find your own the same way you find any identifier: in your own server console, not in the FiveM client.
Can I look up a FiveM player by Discord ID?
Yes, and it is the most direct route: records are tied to Discord identity, so a Discord ID returns which servers the person has been seen in and whether there is a ban record. That is also the form the no-account batch tool takes, up to ten IDs at once. A FiveM-only trace — a license, a Steam hex, a character name — needs a reverse search instead.
Why do license and license2 return different results?
Because they can be two different values for the same player. Cfx.re documents license2 as the ROS licence for people who use Steam, and states it can be the same value as license. Sometimes both arrive and match, sometimes only one does. So an empty license2 result is not "no record" — search licence and licence2 separately before concluding anything, and never treat one as the other when matching.