Telegram RegisterThe public register of Telegram
Telegram profile photo for 🇮🇷 إنزوا | Enzeva

Channel

🇮🇷 إنزوا | Enzeva

@motlaghe

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

123subscribers

+3 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001127711815
TypeChannel
Username@motlaghe
CreatedBetween 1 June 2017 and 30 September 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live4 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/motlaghe

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 26 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

118123120.57 August 2026 — 120 subscribers9 August 2026 — 120 subscribers15 August 2026 — 122 subscribers23 August 2026 — 121 subscribers31 August 2026 — 118 subscribers19 September 2026 — 121 subscribers4 October 2026 — 123 subscribers7 August 20264 October 2026
7 measurements spanning 58 days, net +3. 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 117–124 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 12:16123+2
19 Sept 2026, 04:39121+3
31 Aug 2026, 21:26118-3
23 Aug 2026, 23:47121-1
15 Aug 2026, 08:03122+2
9 Aug 2026, 04:02120no change
7 Aug 2026, 17:42120first reading

Engagement

20 posts held, back to 5 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 Aug 2026, 17:17 UTC21 viewsread 9 August 2026

بسیجی شهید روضه‌خوان حمیدرضا رجب‌زاده

8 Aug 2026, 17:07 UTC20 viewsread 9 August 2026
Forwarded from @mohebinoljavad135File

🎙فـایل صـوتـی شب هشتم محرم۱۴۴۸ زمینه|#کربلایی_حمیدرضا_رجب_زاده گروه رسانه ابن الرئوف علیه السلام @mohebinoljavad135

8 Aug 2026, 17:06 UTC22 viewsread 9 August 2026

۴ متهم قتل (شهادت) حمیدرضا رجب‌زاده دستگیر شدند.

8 Aug 2026, 17:05 UTC22 viewsread 9 August 2026
Forwarded from @akhbareforiPhoto

♦️برادر شهید رجب‌زاده: پیکر برادرم هنوز پیدا نشده است مصطفی رجب‌زاده، برادر شهید حمیدرضا رجب‌زاده: 🔹از ۳ مرداد حوالی ساعت ۱۱ برادر شهیدم مفقود شدن و ما هم کربلا بودیم، به محض اینکه متوجه ماجرا شدیم به سمت تهران برگشتیم. 🔹قبل از شهادت ایشان هیچ پیام یا تماس تهدید آمیزی نه از سوی قاتلین به ما و نه ما با شهید داشتیم . 🔹فیلم‌های لحظه شهادت برادرم در یک کانال پخش شد که توسط یکی از دوستان به ما اطلاع‌رسانی شد و من اولین ن…

8 Aug 2026, 13:43 UTC26 viewsread 9 August 2026

الذین بَذَلُوا مُهَجَهُم دُونَ الحُسَینِ عَلیه‌السّلام ..

8 Aug 2026, 13:37 UTC27 viewsread 9 August 2026

ان شاء الله دروغه. خونواده و مادرش کربلا بودن.

8 Aug 2026, 10:25 UTC32 viewsread 9 August 2026

در انتظار آخرین اذان صبح‌تان هستیم.

8 Aug 2026, 00:26 UTC41 viewsread 9 August 2026

ظاهراً قرار گذاشتن در ازای هر اعدام یک نفر رو شهید کنن.

8 Aug 2026, 00:06 UTC41 viewsread 9 August 2026
Photo

بسیجی شهید حمیدرضا رجب‌زاده. www.instagram.com/ha_rajabzadeh https://t.me/hayolhosein

Showing the 12 most recent of 20 posts we hold for @motlaghe. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

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.

Mentions

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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

“🇮🇷 إنزوا | Enzeva” (@motlaghe), 123 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/motlaghe.

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.