Telegram RegisterThe public register of Telegram
Telegram profile photo for بهترین شکل ممکن

Channel

بهترین شکل ممکن

@behtarin_shekl

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

722subscribers

-9 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-1001587481734
TypeChannel
Username@behtarin_shekl
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/behtarin_shekl

Growth

722731726.57 August 2026 — 731 subscribers7 August 2026 — 731 subscribers15 August 2026 — 730 subscribers23 August 2026 — 722 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net -9. 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 721–732 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 16:33722-8
15 Aug 2026, 20:12730-1
7 Aug 2026, 06:32731no change
7 Aug 2026, 06:21731first reading

Engagement

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

Recent posts

5 Mar 2025, 14:00 UTC≈2,720 viewsread 7 August 2026

مرا که نیست دمی روح در بدن بی‌تو حرام باد دگر زندگی به من، بی‌تو... #قصاب‌کاشانی

5 Mar 2025, 07:08 UTC≈2,740 viewsread 7 August 2026

ساعت ۱۰:۳۷ و تا الان چهار بار تمرکز کردم تا بتونم آرامشمو حفظ کنم تا در جواب توهین و تخریب فحش پدر مادردار نکشم بهشون؛ بار پنجم رو تضمین نمیکنم.

5 Mar 2025, 07:07 UTC≈2,740 viewsread 7 August 2026

آقایون و خانم آ.ج هم باعث شدن به محدوده سعادت آباد حساسیت پیدا کنم.

5 Mar 2025, 07:06 UTC≈2,750 viewsread 7 August 2026

فیلم رها باعث شده به آل استار حساسیت پیدا کنم.

4 Mar 2025, 11:36 UTC≈2,760 viewsread 7 August 2026

صداهای تو شرکتو نمیشنوم؛ حالا بهتر شد.

4 Mar 2025, 08:08 UTC≈2,130 viewsread 7 August 2026

چرا وقتی اینجا پست میذارم همون لحظه گوشی این بنده خدا هم نوتیف میاد براش؟

4 Mar 2025, 08:07 UTC≈2,020 viewsread 7 August 2026

میزان شدت و حدت فروپاشی روانیم باعث شده دلم بخواد کتری شرکتو فرو کنم اندرون خواهر مدیرعامل که میشه مدیر فروش.

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

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

“بهترین شکل ممکن” (@behtarin_shekl), 722 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/behtarin_shekl.

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.