Telegram RegisterThe public register of Telegram
Telegram profile photo for mohammadreza mohammadzadeh

Channel

mohammadreza mohammadzadeh

@mrezamzadeh

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

149subscribers

-1 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001009395627
TypeChannel
Username@mrezamzadeh
CreatedBetween 1 September 2015 and 31 December 2015 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 September 2026
Measurements held3
Confirmed unchanged5 times, most recently 11 September 2026
On Telegramt.me/mrezamzadeh

Growth

149150149.55 August 2026 — 150 subscribers8 August 2026 — 150 subscribers14 August 2026 — 149 subscribers5 August 202614 August 2026
3 measurements spanning 8 days, net -1. 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 149–150 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 08:39149-1
8 Aug 2026, 19:46150no change
5 Aug 2026, 22:32150first reading

Engagement

20 posts held, back to 29 November 2019the 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 6 February 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
4m 12s
Average length
2m 06s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

31 Jan 2022, 22:25 UTC765 viewsread 8 August 2026
File

@Moghtada_Asrin 🎙❤️❤️ #عشق #مقتدا_آسرین https://t.me/Moghtada_Asrin

Signed Mohammadreza

31 Jan 2022, 22:25 UTC777 viewsread 8 August 2026
Forwarded from @Moghtada_AsrinVideo

‎اجراى دلى تقديم به شما خوبان 🌺 @moghtada_asrin 👩‍❤️‍👨 . ‎در كنار دوست عزیز و قدیمی محمدرضاجان❤️🎹 @mohammadreza.mohammadzadeh . @restore.baha ❤️🔒 . @ebi.juybari.music ❤️🎛 . ‎#مقتدا_اسرین #اسرین_مقتدا #موزیک #موسیقی #موسیقی_سنتی #موسیقی_اصیل #ایرانی #عشق #زندگی #music #musician #پیانو #دوستی #عاشقانه_خاص #موزیک_جدید #موسیقی_همدان #باباطاهر #سنتی https://t.me/Moghtada_Asrin

Signed Mohammadreza

7 Apr 2021, 22:08 UTC627 viewsread 8 August 2026
Photo

#محمدرضامحمدزاده @mrezamzadeh

Signed Mohammadreza

8 Nov 2020, 15:01 UTC865 viewsread 8 August 2026
Photo

#محمدرضامحمدزاده @mrezamzadeh

Signed Mohammadreza

2 Sept 2020, 19:15 UTC794 viewsread 8 August 2026
Photo

#محمدرضامحمدزاده @mrezamzadeh

Signed Mohammadreza

8 Jul 2020, 07:08 UTC755 viewsread 8 August 2026
Photo

#محمدرضامحمدزاده @mrezamzadeh

Signed Mohammadreza

10 Jun 2020, 20:32 UTC704 viewsread 8 August 2026
Photo

#محمدرضامحمدزاده @mrezamzadeh

Signed Mohammadreza

30 May 2020, 21:40 UTC628 viewsread 8 August 2026
Photo

#محمدرضامحمدزاده @mrezamzadeh

Signed Mohammadreza

28 Apr 2020, 18:13 UTC640 viewsread 8 August 2026
Photo

#محمدرضامحمدزاده @mrezamzadeh

Signed Mohammadreza

19 Mar 2020, 22:42 UTC719 viewsread 8 August 2026
Photo

#محمدرضامحمدزاده @mrezamzadeh

Signed Mohammadreza

16 Mar 2020, 22:15 UTC601 viewsread 8 August 2026
Photo

#محمدرضامحمدزاده @mrezamzadeh

Signed Mohammadreza

Showing the 12 most recent of 20 posts we hold for @mrezamzadeh. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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

“mohammadreza mohammadzadeh” (@mrezamzadeh), 149 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/mrezamzadeh.

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.