Telegram RegisterThe public register of Telegram
Telegram profile photo for Telegraph

Bot

Telegraph

@telegraph

Verified by Telegram

On this record: Topic · Growth · Engagement · Citations · Cross-platform identity · Cite this entry

68,495monthly users

-6,208 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID328179432
TypeBot
Username@telegraph
First recorded11 August 2026
Last confirmed live25 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/telegraph

Topic

Other / unclassifiable — 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 20 August 2026 and assigned it the closest of 31 fixed categories, at 89% 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.

Growth

68,49575,37571,9355 August 2026 — 74,703 monthly users7 August 2026 — 75,092 monthly users8 August 2026 — 74,915 monthly users10 August 2026 — 74,746 monthly users11 August 2026 — 74,692 monthly users11 August 2026 — 74,692 monthly users12 August 2026 — 74,330 monthly users14 August 2026 — 74,209 monthly users17 August 2026 — 73,445 monthly users18 August 2026 — 73,484 monthly users19 August 2026 — 73,675 monthly users20 August 2026 — 73,550 monthly users21 August 2026 — 73,839 monthly users23 August 2026 — 74,053 monthly users24 August 2026 — 74,469 monthly users27 August 2026 — 75,040 monthly users28 August 2026 — 75,375 monthly users29 August 2026 — 75,102 monthly users31 August 2026 — 74,981 monthly users2 September 2026 — 74,346 monthly users4 September 2026 — 73,947 monthly users6 September 2026 — 70,971 monthly users9 September 2026 — 72,000 monthly users12 September 2026 — 71,522 monthly users13 September 2026 — 70,502 monthly users17 September 2026 — 70,149 monthly users25 September 2026 — 68,495 monthly users5 August 202625 September 2026
27 measurements spanning 51 days, net -6,208. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 67,463–76,407 and does not start at zero.
Measurement log — every monthly users count we have recorded, most recent 20 of 27
Measured (UTC)Monthly usersChange
25 Sept 2026, 10:0268,495-1,654
17 Sept 2026, 10:2170,149-353
13 Sept 2026, 20:5970,502-1,020
12 Sept 2026, 03:2071,522-478
9 Sept 2026, 17:2172,000+1,029
6 Sept 2026, 12:3670,971-2,976
4 Sept 2026, 00:5773,947-399
2 Sept 2026, 18:1474,346-635
31 Aug 2026, 17:3674,981-121
29 Aug 2026, 17:1475,102-273
28 Aug 2026, 15:4275,375+335
27 Aug 2026, 17:1175,040+571
24 Aug 2026, 18:1274,469+416
23 Aug 2026, 04:0274,053+214
21 Aug 2026, 13:0373,839+289
20 Aug 2026, 11:2273,550-125
19 Aug 2026, 08:3673,675+191
18 Aug 2026, 09:5273,484+39
17 Aug 2026, 13:0973,445-764
14 Aug 2026, 09:2474,209first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Forward network

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.

Mentions

Named by 127 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 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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.

Cross-platform identity — Wikidata

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.

Q41137028 on Wikidata, read 27 September 2026
LabelTelegraph
Descriptionweb publishing platform
Official sitehttps://telegra.ph

Cite this entry

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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“Telegraph” (@telegraph), 68,495 monthly users as measured 25 September 2026. Telegram Register, tgregister.com/channel/telegraph.

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.