Telegram RegisterThe public register of Telegram
Telegram profile photo for آقاے‌مجنون

Channel

آقاے‌مجنون

@mr_Majnon113

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

2,208subscribers

-11 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-1002614795321
TypeChannel
Username@mr_Majnon113
Descriptionبسـم‌ربّ‌عشـ‌ـق --﷽- درجستجوی یــار دل آزار کس نبود این رسم تازه را به جهان ما گذاشتیم♥️ +وقف آقا امام زمان(عج) +سیدکپی‌نہ؛فور https://t.me/SendHarfBot?start=mrmajnon
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded18 September 2026
Last confirmed live18 September 2026
Measurements held14
On Telegramt.me/mr_Majnon113

Topic

Religion — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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

2,1032,2192,1617 August 2026 — 2,219 subscribers8 August 2026 — 2,216 subscribers11 August 2026 — 2,192 subscribers13 August 2026 — 2,177 subscribers17 August 2026 — 2,152 subscribers20 August 2026 — 2,154 subscribers24 August 2026 — 2,127 subscribers27 August 2026 — 2,103 subscribers30 August 2026 — 2,112 subscribers2 September 2026 — 2,122 subscribers8 September 2026 — 2,150 subscribers12 September 2026 — 2,128 subscribers15 September 2026 — 2,208 subscribers18 September 2026 — 2,208 subscribers2,2087 August 202618 September 2026
14 measurements spanning 42 days, net -11. 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,086–2,236 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 15:282,208no change
15 Sept 2026, 17:202,208+80
12 Sept 2026, 07:572,128-22
8 Sept 2026, 00:402,150+28
2 Sept 2026, 14:352,122+10
30 Aug 2026, 15:372,112+9
27 Aug 2026, 18:472,103-24
24 Aug 2026, 08:532,127-27
20 Aug 2026, 06:052,154+2
17 Aug 2026, 11:422,152-25
13 Aug 2026, 18:152,177-15
11 Aug 2026, 03:072,192-24
8 Aug 2026, 00:042,216-3
7 Aug 2026, 16:062,219first 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

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

“آقاے‌مجنون” (@mr_Majnon113), 2,208 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/mr_Majnon113.

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.