Telegram RegisterThe public register of Telegram
Telegram profile photo for جواد شریف پور Sharif*

Channel

جواد شریف پور Sharif*

@JavadSharifpour

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

201subscribers

+2 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-1001008662200
TypeChannel
Username@JavadSharifpour
CreatedBetween 1 September 2015 and 31 December 2015— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/JavadSharifpour

Growth

1992012005 August 2026 — 199 subscribers7 August 2026 — 199 subscribers14 August 2026 — 201 subscribers5 August 202614 August 2026
3 measurements spanning 9 days, net +2. 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 199–201 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 15:38201+2
7 Aug 2026, 04:03199no change
5 Aug 2026, 22:07199first reading

Engagement

20 posts held, back to 9 August 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 12 June 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

12 Jun 2026, 16:08 UTC143 viewsread 7 August 2026
File

"چراغ کهنه" ترانه و دکلمه: جواد شریف پور

21 Mar 2025, 01:16 UTC620 viewsread 7 August 2026
Video

"گلبرگ" شعر و دکلمه؛ جواد شریف پور @javadSharifpour

4 Mar 2024, 11:48 UTC995 viewsread 7 August 2026
File

"قاصدک" خواننده: هرانوش ترانه: جواد شریف پور موسیقی: پدرام مرندیز

12 Jan 2024, 14:30 UTC≈1,120 viewsread 7 August 2026
File

ترانه: جواد شریف پور هوش مصنوعی "تردید" فیت مهستی و شادمهر

26 Oct 2023, 20:19 UTC927 viewsread 7 August 2026

آپارات - سرویس اشتراک ویدیو https://www.aparat.com/v/76w24

24 Jul 2023, 17:19 UTC905 viewsread 7 August 2026

. نظر دکتر هلاکویی در مورد مردم گیلان . #گیلان #رشت #ایران https://www.instagram.com/reel/CuzYA37vhws/?igshid=NjZiM2M3MzIxNA==

24 Jul 2023, 17:18 UTC840 viewsread 7 August 2026

. در کودکی وقتی از مادر بزرگ ها و پدربزرگ ها و افراد نسبتأ پیر فامیل می‌شنیدیم که "عمر کوتاه است"، باور نمی‌کردم، تعجب می‌کردم. برای ما، سه ماه تعطیلی تابستان خیلی زمان زیادی بود. انگار از پایان خرداد تا ابتدای مهر که دوباره به مدرسه برگردیم، یکبار پوست می‌انداختیم و آدم دیگری می‌شدیم تا به کلاس بالاتر برویم. تا ده سالگی آن‌قدر خاطره داشتم که با خود فکر می‌کردم حالا اگر این، پنج و شش و هفت برابر بشود، چه قدر طول خو

24 Jul 2023, 17:18 UTC587 viewsread 7 August 2026

. احمدرضا احمدی زلال ترین شخصیتی بودی که در عمر خود دیده ام. به معنای اخص کلمه شاعر خودت هم می دانستی که چه قدر صدایت را دوست داشتم وقتی شعر نیما را می خواندی; هنگام که گریه می‌دهد ساز این دود سرشت ابر بر پشت ... . #احمدرضااحمدی https://www.instagram.com/reel/CukaNvsuvvo/?igshid=NjZiM2M3MzIxNA==

24 Jul 2023, 17:17 UTC564 viewsread 7 August 2026

. این شعر را حدود ده سال پیش نوشته ام اما انگار امسال تعبیر شده . خطی میانِ اسفند و فروردین کشیده اند خطی که انگار از روز نخستین کشیده اند آن جا که سال و حال ما تمام می شود خطی به شکلِ فردا و نقطه چین کشیده اند یک عده پُشت این خط تا همیشه مانده اند یک عده اشکِ چشم شان را به آستین کشیده اند وقتی شراب را از هفته هامان گرفته اند این سُفره را به زیر هفت سین کشیده اند ایران و خانه و فامیل و شهر بهانه است خطی به روی هجومِ

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

“جواد شریف پور Sharif*” (@JavadSharifpour), 201 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/JavadSharifpour.

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.