Channel
MillionPlans
@millionplans
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,271subscribers
-136 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001782512072 |
|---|---|
| Type | Channel |
| Username | @millionplans |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 23 October 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 23 October 2026 |
| On Telegram | t.me/millionplans |
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 13 September 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 22:36 | 5,271 | -4 |
| 20 Oct 2026, 23:05 | 5,275 | -6 |
| 17 Oct 2026, 23:46 | 5,281 | -9 |
| 15 Oct 2026, 02:54 | 5,290 | -5 |
| 12 Oct 2026, 06:17 | 5,295 | -16 |
| 5 Oct 2026, 10:17 | 5,311 | -12 |
| 27 Sept 2026, 11:41 | 5,323 | -16 |
| 15 Sept 2026, 20:37 | 5,339 | -7 |
| 12 Sept 2026, 12:55 | 5,346 | -9 |
| 8 Sept 2026, 15:01 | 5,355 | -14 |
| 3 Sept 2026, 00:57 | 5,369 | -1 |
| 31 Aug 2026, 12:37 | 5,370 | no change |
| 31 Aug 2026, 01:56 | 5,370 | -10 |
| 28 Aug 2026, 10:28 | 5,380 | -4 |
| 25 Aug 2026, 08:51 | 5,384 | -11 |
| 22 Aug 2026, 13:37 | 5,395 | -4 |
| 19 Aug 2026, 11:16 | 5,399 | -4 |
| 16 Aug 2026, 08:29 | 5,403 | -4 |
| 14 Aug 2026, 21:45 | 5,407 | 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.
@snap_66 · 63,313
Telegram ranks this channel #23 of 69 here — alongside 68 others — read 21 August 2026
@LearnENG_now · 22,779
Telegram ranks this channel #30 of 53 here — alongside 52 others — read 18 September 2026
@Teamnassar · 25,256
Telegram ranks this channel #44 of 74 here — alongside 73 others — read 13 September 2026
@cognitive_ability · 108,076
Telegram ranks this channel #64 of 87 here — alongside 86 others — read 14 August 2026
@matagrcom · 24,212
Telegram ranks this channel #68 of 71 here — alongside 70 others — read 15 September 2026
This channel appears in 5 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“MillionPlans” (@millionplans), 5,271 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/millionplans.
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.