Telegram RegisterThe public register of Telegram
Telegram profile photo for مِهزی

Channel

مِهزی

@mehzi

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

527subscribers

-21 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-1001075102518
TypeChannel
Username@mehzi
CreatedBetween 1 September 2016 and 30 September 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 October 2026
Last confirmed live7 November 2026
Measurements held12
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/mehzi

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 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 the other topics.

Growth

527548537.57 August 2026 — 548 subscribers16 August 2026 — 545 subscribers25 August 2026 — 544 subscribers31 August 2026 — 540 subscribers9 September 2026 — 538 subscribers16 September 2026 — 539 subscribers1 October 2026 — 534 subscribers11 October 2026 — 534 subscribers12 October 2026 — 529 subscribers18 October 2026 — 527 subscribers24 October 2026 — 528 subscribers7 November 2026 — 527 subscribers7 August 20267 November 2026
12 measurements spanning 91 days, net -21. 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 524–551 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Nov 2026, 00:45527-1
24 Oct 2026, 20:27528+1
18 Oct 2026, 20:07527-2
12 Oct 2026, 11:09529-5
11 Oct 2026, 19:59534no change
1 Oct 2026, 07:42534-5
16 Sept 2026, 14:01539+1
9 Sept 2026, 18:19538-2
31 Aug 2026, 09:41540-4
25 Aug 2026, 02:48544-1
16 Aug 2026, 21:03545-3
7 Aug 2026, 13:14548first 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.

نگاران | ادبیات
@negaaraan_ac · 34,073
Telegram ranks this channel #33 of 88 here — alongside 87 others — read 4 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 7 November 2026 — this entry's latest reading, not the date you are reading this.

“مِهزی” (@mehzi), 527 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/mehzi.

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.