Browse

Browse the register

2,802,188 entries we hold a subscriber measurement for, arranged three ways. Each way is a property we have measured — not a category anyone assigned.

A register that can only be searched is a register you have to already know the answer to. These are the three axes the data supports: how big a channel is, what language it publishes in, and how recently it last published. Every list is ordered by the latest measured subscriber count, largest first, and every figure below was read from the database when this page was built. A fourth surface asks a different question — not how big an entry is but which way it is going: risers and fallers.

By subscriber size

Fixed half-decade bands — each spans a factor of 3.16 — and they are not this page’s invention: they are the same bands the published engagement baselines are computed over, so a band page and the baseline for that band always describe the same population. A channel is placed by the most recent subscriber reading we hold for it, and a superseded reading never places it anywhere.

Entries is what the register holds in that band. With a baselineis how many of them have enough measured posts to carry an engagement figure, which is always a smaller number and is the population the median describes. The under-1,000 band has no baseline at all: the baseline dataset’s eligibility gate starts at 1,000 subscribers, so nothing is quoted for it rather than a neighbouring band’s figure being borrowed.

By language

Derived, not declared. Telegram publishes no language for a channel and neither does the channel: channel.lang is null for every entry in the register. What is measured is the language of each individual post, and a channel is listed under a language only when that language is the most common one across its own posts of the last 30 days and accounts for at least 60% of them. A channel whose month is a 40/35/25 mixture is not listed under any language, because it is not a channel in any one of them. This is exactly the rule the engagement baselines use to build their language cohorts, so the two never split the same channel two ways.

Posts measured is how many posts in the window carried that language across all of its channels — the evidence the label rests on, not a count of everything those channels published. Baseline cohorts is how many subscriber bands have a published engagement baseline for that language; a band needs at least 300 channels in the cell before one is computed, so most languages have none. Languages under 200 entries are listed here with their counts but are not given a page of their own: at that size a page would be a handful of rows under a heading, which is the thin-directory pattern this register exists not to publish.

By how recently it published

Measured against our own last visit, not against the clock. The crawler records when it last read each channel’s posts; the age below is the gap between that visit and the newest post it found. Stating it any other way would claim knowledge of what a channel did after we stopped looking.

The last row is not a bucket. Those entries are ones whose posts the crawler has not read yet, and they are counted apart from the dormant ones on purpose: “we have not looked” and “it has published nothing” are different statements, and only the second is ours to make. 1,874,870 entries were last read more than two days ago, so their bucket may be a boundary out of date.

By topic

Inferred, not measured — read this before the table.Every other dimension on this page is something a second person could recompute by hand from public data and get the identical answer. A topic is different: an on-box language model reads a channel’s own recent posts and assigns the closest of 31 fixed categories, with a confidence score attached. That is a classification, not a reading, and this register treats the two differently everywhere — a topic is never shown inside a table of measured figures without saying so, and it is not shown here as a link to a page of its own; see why below the table.

Coverage is partial and still growing. The classifier is working through the register gradually and has reached 52,240 of roughly 2,802,188 channels so far — under one percent. A channel with no row below has not been read by the classifier yet; that is not the same as the classifier finding nothing to say about it. Every classification so far comes from one model, Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1, written between 8 August 2026 and 13 August 2026.

No topic here links to a page of its own, and none is offered for search indexing.Even the largest category above is a thinner slice of the whole register than any other facet on this site publishes a page for, and the population behind it is still being written — a URL indexed today would name a set of channels that looks substantially different in a week, which is the same scaled-publishing risk this site’s channel-page index gate exists to keep off individual entries, applied here to a facet instead. A channel’s own classification, with the model and date that produced it, is shown on its own page instead.

What is deliberately not here

There is no browse by posting rate. The register does not hold every post a channel has published — for a typical entry it holds 18, one page of the public preview. “Posts in the last month” counted from that is a floor set by how deep our crawl reached, not a count of what the channel published, and banding channels by it would publish a property of the crawler as a property of the channel. Recency survives the same objection where a rate does not: the crawler always reads the newest page first, so the newest post we hold is the channel’s real newest post as at that visit, whatever sits unread behind it.

The register’s post coverage was last refreshed between 5 August 2026 and 13 August 2026, across 2,803,043 entries. How we measure.