Telegram Numeric IDs Explained

The ID line on every @doublegram_lookup_bot result card in Telegram is the most important field. Positive IDs identify users and bots; negative IDs identify groups and channels — and unlike @usernames, they do not change when someone rebrands.

Every entity on Telegram has a numeric ID assigned by Telegram's servers. When @doublegram_lookup_bot succeeds, it always surfaces this ID because it is the most reliable way to refer to a person, bot, group, or channel across time and tools.

Why IDs matter

  • Permanent — IDs do not change when users rename themselves or drop their @username
  • API-native — Bots, integrations, and admin tools use IDs, not display names
  • Unique — One ID maps to exactly one entity type on Telegram
  • Always present — When Lookup succeeds, ID is the first field on the card

Sign convention

EntityID signNotes
User or bot Positive e.g. 987654321
Basic group Negative Shorter negative number
Supergroup / channel Negative (-100…) Modern large chats use -100 prefix form

@doublegram_lookup_bot accepts IDs with 7–13 digits (excluding the minus sign). Send the ID as a plain message in Telegram to search by number (see Search by Numeric ID in Telegram Lookup).

ID vs username

Numeric ID@username
Changes? No User can change or remove username
Human-readable? No Yes
Private users? Only if Telegram allows resolution Only if they set a public handle
Best for APIs? Yes Sometimes (public only)

Pro tip: Save the ID from Lookup when you moderate or automate — scripts and ban lists should use IDs, not display names.

Where Lookup shows IDs

  • Lookup Results card — first line after the header
  • My Data (/start menu) — your own Telegram user ID
  • Forward fallbacks — basic forward info when full resolution fails but Telegram still exposes chat/user ID in forward metadata
  • t.me/c/… links — Lookup derives a -100… chat ID from the URL path

When you cannot get an ID

  • Privacy-protected user forward — Telegram hides the user ID; only a name is shown
  • Strict privacy + ID search — Lookup may refuse ID-based user lookup
  • Unknown private chat — Negative ID not in resolver session → access error instead of ID confirmation

Quick reference

  • Users: positive ID
  • Groups/channels: negative ID
  • Lookup: send plain number or read from result card
  • Prefer ID over username for long-term records

You now have the full user-facing guide for @doublegram_lookup_bot on Telegram — from first search to reading every field on the result card.