tgregister.com valid

Telegram Register

The public register of Telegram channels and groups, at

For agents: Public register of Telegram channels and groups with subscriber measurements, browsable by size, language and recency, plus methodology notes.

telegram channelstelegram groupssubscriber countschannel registertelegram analytics

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T21:54:01.567Z. Cached copy · Source on tgregister.com

# Telegram Register

> The public register of Telegram channels and groups, at
> https://tgregister.com. Independent, and not affiliated with or endorsed by
> Telegram. Every figure was read off a public Telegram surface by our own
> crawler on a date we record — nothing is licensed from an analytics vendor,
> copied from another directory, self-reported by a channel, modelled or
> estimated. As at 20 Oct 2026, 21:05 UTC the register holds 4,328,973 entries,
> 40,073,454 subscriber readings and 326,463,458 post view/reaction readings
> across 102,465,994 posts.

LAUNCHED 8 August 2026. robots.txt allows crawling of the whole site. Indexing
is decided separately, per page: the whole-register aggregate pages are
indexable, and a channel or group page is offered for indexing only once its own
measurement record has earned it (https://tgregister.com/methodology#indexing).
The history is still short: the oldest reading in the register was taken on 5
August 2026, so the whole history is about 76 days deep. Growth is reported over
the interval it was observed across, and is never extrapolated into a rate.

This file and https://tgregister.com/llms-full.txt are generated from the
database. Every count above was measured in one pass at 20 Oct 2026, 21:05 UTC
and is refreshed hourly. The counts move; do not cache them as facts about the
register.

## Start here

- [How we measure](https://tgregister.com/methodology): the four public surfaces we read, why readings from different surfaces never confirm each other, why view counts above 1,000 are approximate, and the claims we refuse to make. Read this before quoting any number from this site.
- [Browse the register](https://tgregister.com/browse): every entry we hold a subscriber measurement for, arranged by size band, by the language of its own posts, and by how recently it last published. A topic is also recorded on some entries, but it is an LLM classification of the channel's own text rather than a measurement, is labelled as such wherever it appears, and covers part of the register, with the share and the model that produced it printed on /browse — there are no topic browse pages yet.
- [Risers and fallers](https://tgregister.com/movers): what changed between two readings of the same page, by absolute subscribers and as a share of size. 3,329,316 entries currently qualify.
- [The groups register](https://tgregister.com/groups): a second register, covering public Telegram groups and supergroups with an exact member count on each — measured the same way as channels, published separately because groups carry no post archive.
- [Engagement baselines](https://tgregister.com/data/err-baselines): published ERR (views-to-subscribers) percentiles by subscriber band and language, so the comparison behind any engagement observation can be reproduced.
- [Most-cited entries](https://tgregister.com/cited): ranked by position in the measured citation graph — weighted PageRank over forward and mention edges. Forwarded-
…

Related sites

Other listed sites in Data and analytics. See the whole category →

Machine-readable: GET /v1/resolve?q=tgregister.com · GET /v1/domain/tgregister.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for tgregister.com:
1. POST https://agentwebmap.com/v1/sites/tgregister.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://tgregister.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/tgregister.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/tgregister.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.