Channel
@telegram
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · What this channel posts · View velocity · Posts · Citations · Telegram's recommendations · Domains linked from posts · Cross-platform identity · Referenced elsewhere · Cite this entry
9,461,698subscribers
-441,082 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among the largest entries.
| Telegram ID | -1001005640892 |
|---|---|
| Type | Channel |
| Username | @telegram |
| Description | The official Telegram on Telegram. Much recursion. Very Telegram. Wow. |
| Created | 21 September 2015 — measured — Telegram's own channel record (MTProto) |
| First recorded | 5 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 37 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/telegram |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear word for word on 1 other registered channel. They sit inside a group of 3 channels that share the same post bodies with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @telegram/190 · this entry19 Sept 2022, 15:13 UTC | @GbTelegram_app/3419 Sept 2022, 23:25 UTC | 1.00 | 8.2 hours |
| @telegram/191 · this entry19 Sept 2022, 15:13 UTC | @GbTelegram_app/3519 Sept 2022, 23:25 UTC | 1.00 | 8.2 hours |
| @telegram/192 · this entry19 Sept 2022, 15:13 UTC | @GbTelegram_app/3619 Sept 2022, 23:25 UTC | 1.00 | 8.2 hours |
| @telegram/193 · this entry19 Sept 2022, 15:14 UTC | @GbTelegram_app/3719 Sept 2022, 23:25 UTC | 1.00 | 8.2 hours |
| @telegram/194 · this entry19 Sept 2022, 15:14 UTC | @GbTelegram_app/3819 Sept 2022, 23:25 UTC | 1.00 | 8.2 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @GbTelegram_app | 5 (5/5 hand-verifiable sample passed) | 1.00 | 8.2 hours | this entry (5–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 388 comparable posts for this entry, running 22 September 2015 to 19 July 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 3, the earliest publisher we hold is @telegram — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 7 August 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 06:39 | 9,461,698 | -71,983 |
| 17 Sept 2026, 12:55 | 9,533,681 | -14,047 |
| 15 Sept 2026, 13:38 | 9,547,728 | -11,272 |
| 13 Sept 2026, 21:21 | 9,559,000 | -18,462 |
| 12 Sept 2026, 03:57 | 9,577,462 | -15,171 |
| 9 Sept 2026, 23:00 | 9,592,633 | -27,753 |
| 6 Sept 2026, 18:59 | 9,620,386 | -23,779 |
| 4 Sept 2026, 07:57 | 9,644,165 | -12,280 |
| 2 Sept 2026, 20:24 | 9,656,445 | -10,834 |
| 1 Sept 2026, 18:38 | 9,667,279 | -12,396 |
| 31 Aug 2026, 17:07 | 9,679,675 | -7,914 |
| 30 Aug 2026, 19:37 | 9,687,589 | -10,555 |
| 29 Aug 2026, 19:49 | 9,698,144 | -10,730 |
| 28 Aug 2026, 20:06 | 9,708,874 | -8,798 |
| 27 Aug 2026, 21:04 | 9,717,672 | -11,539 |
| 26 Aug 2026, 22:14 | 9,729,211 | -11,347 |
| 25 Aug 2026, 21:27 | 9,740,558 | -6,998 |
| 24 Aug 2026, 19:29 | 9,747,556 | -17,012 |
| 23 Aug 2026, 04:08 | 9,764,568 | -13,447 |
| 21 Aug 2026, 17:58 | 9,778,015 | first reading |
430 posts held, back to 21 September 2015 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 4,229 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 430 posts for this entry, the most recent from 26 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 28 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 18 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
How fast this channel’s own posts pick up views, from re-reading them repeatedly in the hours and days after they were published rather than the single reading most entries on this register get. Coverage is early and only a small minority of channels hold it at all — a gap in this section means the post has not been re-read again yet, not that nothing happened.
Computed from 5 of this channel’s own posts over the last 30 days: across 5 of this channel’s own posts with a clear reading, a typical one reaches half of its last-observed view count within 9.7 hours of being posted; the median 24-hour reach across those posts is 437,000 views — 4.58% of this channel’s own subscriber count (90th percentile 487,400).
| Post | Readings | Latest reading | Curve | 24h reach | Half of last-observed views by |
|---|---|---|---|---|---|
| /46026 Aug 2026, 19:12 UTC | 16874 minutes – 7 days old | 810,000 views ~no reaction reading | 3.0 hours: 232,000 → 6.0 hours: 295,000 → 12 hours: 401,000 → 24 hours: 505,000 → 2 days: 584,000 → 7 days: 809,000still climbing at last reading | 505,000measured | 12 hours |
| /45926 Aug 2026, 19:12 UTC | 16274 minutes – 7 days old | 730,000 views ~no reaction reading | 3.0 hours: 213,000 → 6.0 hours: 269,000 → 12 hours: 365,000 → 24 hours: 461,000 → 2 days: 532,000 → 7 days: 730,000still climbing at last reading | 461,000measured | 12 hours |
| /45826 Aug 2026, 19:12 UTC | 15075 minutes – 7 days old | 511,000 views ~no reaction reading | 3.0 hours: 167,000 → 6.0 hours: 209,000 → 12 hours: 280,000 → 24 hours: 345,000 → 2 days: 391,000 → 7 days: 510,000still climbing at last reading | 345,000measured | 9.7 hours |
| /45726 Aug 2026, 19:11 UTC | 14975 minutes – 7 days old | 494,000 views ~no reaction reading | 3.0 hours: 166,000 → 6.0 hours: 207,000 → 12 hours: 276,000 → 24 hours: 340,000 → 2 days: 384,000 → 7 days: 493,000still climbing at last reading | 340,000measured | 9.3 hours |
| /45626 Aug 2026, 19:11 UTC | 15575 minutes – 7 days old | 623,000 views ~no reaction reading | 3.0 hours: 209,000 → 6.0 hours: 264,000 → 12 hours: 354,000 → 24 hours: 437,000 → 2 days: 494,000 → 7 days: 623,000still climbing at last reading | 437,000measured | 9.1 hours |
| /45526 Aug 2026, 19:11 UTC | 15276 minutes – 7 days old | 645,000 views ~no reaction reading | 3.0 hours: 219,000 → 6.0 hours: 267,000 → 12 hours: 370,000 → 24 hours: 458,000 → 2 days: 517,000 → 7 days: 645,000still climbing at last reading | 458,000measured | 8.9 hours |
Curve is every standard checkpoint we hold a reading for (+1h, +3h, +6h, +12h, +24h, +48h, +7d after posting) — measured where a real reading landed close enough to that age, interpolated where it did not but readings on both sides let one be worked out between them. Nothing is ever extrapolated past the last real reading. Latest reading is the newest view and reaction count we hold for the post, side by side, so a gap between how views and reactions moved is visible without following it into the Observations section above. 24h reach is that one checkpoint on its own, labelled the same way. Half of last-observed views is the age at which a post’s view count crossed half of the highest figure we have read for it so far — an upper bound when the very first reading was already past half (we cannot see the actual crossing), and biased low while the post is still climbing, since “half of final” is dividing by a number that has not finished growing yet. Both caveats are printed inline wherever they apply, never silently dropped.
For all the info from today's update and a look back at 13 years of Telegram features — check out our blog: https://telegram.org/blog/welcome-messages-buttons-TG-13 August Features 1 • 2 • 3 • 4 • 5 • More
Signed Gifts. You can now add your signature and a comment to gifts you buy via the gift marketplace. August Features 1 • 2 • 3 • 4 • 5 • More
Placeholders for App Updates. If a user with an outdated app encounters a new feature, they can now instantly tap to download the latest update. August Features 1 • 2 • 3 • 4 • 5 • More
Inline Documents. The rich text editor now supports inline documents, files and music anywhere in your text. August Features 1 • 2 • 3 • 4 • 5 • More
Buttons Inside Messages. Developers are now able to put multiple buttons inside a message and create custom flows. August Features 1 • 2 • 3 • 4 • 5 • More
Welcome Messages. Group and channel owners can now add messages that appear when a new member joins. These messages are only visible to the person who joins the chat. August Features 1 • 2 • 3 • 4 • 5 • More
For all the details on these new features, check out our blog: https://telegram.org/blog/communities-editor-invisible-messages July Features 1 • 2 • 3 • 4 • More
350 Million GIFs. The GIF panel now contains over 350 million GIFs in 36 languages. Your Telegram GIF searches are entirely private and do not rely on any third parties. July Features 1 • 2 • 3 • 4 • More
Ephemeral Bot Messages. You can now send private commands to bots in group chats and receive replies that are only visible to you. July Features 1 • 2 • 3 • 4 • More
Telegram Communities. Several groups, channels and bots can now be linked together in a single community, where members can view and join other chats instantly. July Features 1 • 2 • 3 • 4 • More
⭐️ Rich Text Editor. You can now create articles and long posts in a visual editor that supports dozens of formatting options and allows you to generate text with privacy-conscious AI tools. July Features 1 • 2 • 3 • 4 • More
For all the features from this update, like links in poll options, support for .md files and new browser settings – check out the full blog: https://telegram.org/blog/watch-apps-and-more June Features 1 • 2 • 3 • More
Showing the 12 most recent of 430 posts we hold for @telegram. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 54 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 12,902 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 7 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 124 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
2 domains this channel’s own posts have linked to, measured by scanning the post bodies themselves — not the channel’s description, which is the separate Declared links section below when this entry has one. Appearing here is not a claim about who runs the linked site or why the channel linked to it; an advertisement, a news citation and a malicious link all leave the same kind of row.
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | No label recorded on this Wikidata item |
|---|---|
| Description | instant messaging service |
| X / Twitter | @telegram |
| Official site | https://telegram.org |
This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.
Hacker News
This handle was named 3 times in a Hacker News comment or story, via the public Algolia search API. HN comment and story text has no confirmed reuse licence, so nothing quoted from either is reproduced here — only that a mention exists, when, and by whom, with a link to read it at the source.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 27 September 2026 — this entry's latest reading, not the date you are reading this.
“Telegram News” (@telegram), 9,461,698 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/telegram.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.