Channel
@DiscussThis
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
64,608subscribers
-440 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001174737667 |
|---|---|
| Type | Channel |
| Username | @DiscussThis |
| Description | This channel is meant to post things that can be discussed. And demonstrate @discussbot in action. |
| Created | 29 May 2019 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/DiscussThis |
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 99% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 09:42 | 64,608 | -38 |
| 4 Sept 2026, 00:19 | 64,646 | -7 |
| 2 Sept 2026, 13:48 | 64,653 | -19 |
| 1 Sept 2026, 11:15 | 64,672 | -18 |
| 31 Aug 2026, 10:48 | 64,690 | -10 |
| 30 Aug 2026, 11:15 | 64,700 | -21 |
| 29 Aug 2026, 08:17 | 64,721 | -23 |
| 28 Aug 2026, 11:06 | 64,744 | -5 |
| 27 Aug 2026, 12:04 | 64,749 | +1 |
| 26 Aug 2026, 13:16 | 64,748 | +4 |
| 25 Aug 2026, 14:08 | 64,744 | -16 |
| 24 Aug 2026, 17:19 | 64,760 | -25 |
| 23 Aug 2026, 03:06 | 64,785 | -33 |
| 21 Aug 2026, 17:34 | 64,818 | -7 |
| 20 Aug 2026, 18:22 | 64,825 | -28 |
| 19 Aug 2026, 14:52 | 64,853 | -6 |
| 18 Aug 2026, 17:22 | 64,859 | -3 |
| 17 Aug 2026, 16:55 | 64,862 | -8 |
| 16 Aug 2026, 07:54 | 64,870 | -16 |
| 14 Aug 2026, 21:55 | 64,886 | first reading |
2 posts held, back to 29 May 2019 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 65 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 2 posts for this entry, the most recent from 31 May 2019. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 6 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.
This is a demonstration of what @discussbot can do when you add it to your channel. Tap the comment button below and tell us what you think (please use English). The bot is just an example of Telegram's new seamless authorization for websites. Anyone can now create bots that connect their existing social, gaming, productivity, dating or e-commerce services to Telegram on the fly. If you're a developer, see: https://…
Channel created
Showing the 2 most recent of 2 posts we hold for @DiscussThis. 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.
Named by 10 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.
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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Discuss That!” (@DiscussThis), 64,608 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/DiscussThis.
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.