Telegram RegisterThe public register of Telegram
Telegram profile photo for 『 بَعدِ آدم‌ها 』

Channel

『 بَعدِ آدم‌ها 』

@flowofmindd

On this record: Topic · Growth · Engagement · Citations · Cite this entry

3,013subscribers

+212 since we began measuring on 11 September 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1003501687577
TypeChannel
Username@flowofmindd
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 September 2026
Last confirmed live5 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/flowofmindd

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 4 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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

2,6333,5583,095.511 September 2026 — 2,801 subscribers13 September 2026 — 2,801 subscribers13 September 2026 — 2,778 subscribers16 September 2026 — 2,725 subscribers25 September 2026 — 2,633 subscribers4 October 2026 — 3,558 subscribers10 October 2026 — 3,390 subscribers14 October 2026 — 3,326 subscribers17 October 2026 — 3,260 subscribers20 October 2026 — 3,212 subscribers23 October 2026 — 3,163 subscribers26 October 2026 — 3,109 subscribers30 October 2026 — 3,070 subscribers2 November 2026 — 3,044 subscribers5 November 2026 — 3,013 subscribers3,01311 September 20265 November 2026
15 measurements spanning 55 days, net +212. 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 2,494–3,697 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 10:103,013-31
2 Nov 2026, 10:083,044-26
30 Oct 2026, 01:363,070-39
26 Oct 2026, 22:493,109-54
23 Oct 2026, 18:003,163-49
20 Oct 2026, 09:583,212-48
17 Oct 2026, 08:013,260-66
14 Oct 2026, 05:413,326-64
10 Oct 2026, 15:003,390-168
4 Oct 2026, 20:573,558+925
25 Sept 2026, 02:012,633-92
16 Sept 2026, 16:012,725-53
13 Sept 2026, 02:012,778-23
13 Sept 2026, 00:292,801no change
11 Sept 2026, 18:472,801first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“『 بَعدِ آدم‌ها 』” (@flowofmindd), 3,013 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/flowofmindd.

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.