
Channel
Brainstorming
@brainstormingchannel
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
2,327subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001669800381 |
|---|---|
| Type | Channel |
| Username | @brainstormingchannel |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 17 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/brainstormingchannel |
Topic
Personal blog — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 91% 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 |
|---|---|---|
| 2 Nov 2026, 10:15 | 2,327 | +3 |
| 30 Oct 2026, 06:55 | 2,324 | -1 |
| 26 Oct 2026, 22:16 | 2,325 | +2 |
| 24 Oct 2026, 01:17 | 2,323 | +3 |
| 20 Oct 2026, 23:36 | 2,320 | +2 |
| 18 Oct 2026, 07:28 | 2,318 | -1 |
| 14 Oct 2026, 20:48 | 2,319 | -6 |
| 11 Oct 2026, 08:58 | 2,325 | -5 |
| 5 Oct 2026, 05:17 | 2,330 | -2 |
| 26 Sept 2026, 18:37 | 2,332 | -9 |
| 17 Sept 2026, 01:27 | 2,341 | no change |
| 15 Sept 2026, 10:20 | 2,341 | +3 |
| 11 Sept 2026, 09:58 | 2,338 | +4 |
| 6 Sept 2026, 10:57 | 2,334 | +14 |
| 2 Sept 2026, 08:04 | 2,320 | -8 |
| 30 Aug 2026, 09:35 | 2,328 | +9 |
| 27 Aug 2026, 07:47 | 2,319 | +4 |
| 24 Aug 2026, 05:07 | 2,315 | +1 |
| 20 Aug 2026, 16:13 | 2,314 | -3 |
| 17 Aug 2026, 14:28 | 2,317 | 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.
@OneThousandandOnePodcast · 35,198
Telegram ranks this channel #19 of 77 here — alongside 76 others — read 6 September 2026
@science_magazine · 23,032
Telegram ranks this channel #20 of 95 here — alongside 94 others — read 21 September 2026
@doctor_zarifi · 55,231
Telegram ranks this channel #40 of 87 here — alongside 86 others — read 23 August 2026
@drminasafi59 · 26,721
Telegram ranks this channel #81 of 90 here — alongside 89 others — read 11 September 2026
This channel appears in 4 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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“Brainstorming” (@brainstormingchannel), 2,327 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/brainstormingchannel.
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.