Channel
M20 CHAIN ANNOUNCEMENTS
@m20chainannouncements
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,271subscribers
-166 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001901336844 |
|---|---|
| Type | Channel |
| Username | @m20chainannouncements |
| Created | Between 1 March 2023 and 31 December 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 7 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 7 November 2026 |
| On Telegram | t.me/m20chainannouncements |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Nov 2026, 10:08 | 3,271 | -2 |
| 4 Nov 2026, 00:17 | 3,273 | -4 |
| 31 Oct 2026, 21:19 | 3,277 | -9 |
| 29 Oct 2026, 06:49 | 3,286 | -5 |
| 26 Oct 2026, 10:46 | 3,291 | -2 |
| 23 Oct 2026, 13:35 | 3,293 | -8 |
| 20 Oct 2026, 16:20 | 3,301 | -6 |
| 17 Oct 2026, 22:50 | 3,307 | -6 |
| 15 Oct 2026, 05:25 | 3,313 | -8 |
| 12 Oct 2026, 09:41 | 3,321 | -19 |
| 5 Oct 2026, 14:37 | 3,340 | -14 |
| 28 Sept 2026, 03:00 | 3,354 | -22 |
| 18 Sept 2026, 16:01 | 3,376 | -6 |
| 14 Sept 2026, 00:00 | 3,382 | -11 |
| 10 Sept 2026, 01:37 | 3,393 | -12 |
| 8 Sept 2026, 22:56 | 3,405 | no change |
| 4 Sept 2026, 15:59 | 3,405 | -4 |
| 31 Aug 2026, 21:26 | 3,409 | -8 |
| 28 Aug 2026, 17:15 | 3,417 | -5 |
| 26 Aug 2026, 03:13 | 3,422 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.
Appears in Telegram’s recommendations for other channels
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.
@crypto_retro · 378,336
Telegram ranks this channel #10 of 78 here — alongside 77 others — read 10 August 2026
@THETA_GAINERS_NEHA_JAREDA · 17,445
Telegram ranks this channel #38 of 51 here — alongside 50 others — read 3 September 2026
@RamJiKiPathshala · 36,334
Telegram ranks this channel #58 of 60 here — alongside 59 others — read 3 October 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 7 November 2026 — this entry's latest reading, not the date you are reading this.
“M20 CHAIN ANNOUNCEMENTS” (@m20chainannouncements), 3,271 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/m20chainannouncements.
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.