Telegram RegisterThe public register of Telegram
Telegram profile photo for "چَنـد لـحظہ عــاشقــی"

Channel

"چَنـد لـحظہ عــاشقــی"

@chand_lahzeh_asheghi

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

53subscribers

-1 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001420015002
TypeChannel
Username@chand_lahzeh_asheghi
CreatedBetween 1 April 2019 and 25 December 2020 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live7 October 2026
Measurements held3
Confirmed unchanged2 times, most recently 7 October 2026
On Telegramt.me/chand_lahzeh_asheghi

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

535453.56 August 2026 — 54 subscribers10 August 2026 — 54 subscribers25 September 2026 — 53 subscribers6 August 202625 September 2026
3 measurements spanning 50 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 53–54 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 19:4153-1
10 Aug 2026, 08:3154no change
6 Aug 2026, 23:5154first reading

Engagement

18 posts held, back to 25 December 2020 — 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 18 posts for this entry, the most recent from 24 January 2021. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 45s
Average length
28s

Measured directly from 6 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

24 Jan 2021, 17:15 UTC847 viewsread 10 August 2026

••• #تلنگــر ⚠️🍃 #حجاب #چادر #باݩو •❥💚❥• بانو ❗️ ایݩ را بدان°☝️° تو که با وقار راہ میروۍ•••☺️ باد💨 که چـ∞ـادرت را پریشان میکند و تو دستـ✋ـهایت را °نذر° مرتب کردنش می کنی••• خدا آݩ باݪا 🔝قدح قدح غرور مۍ فروشد به فرشتـ👼گانش••• که این بود°✋° بنده اۍ که گفتم سجده اش ڪنید•••🙏 اشرف مخݪوقاتم را بݩگرید کہ چہ عاشقانہ برایم بݩدگۍ مۍکند•••♥️☺️ | @chand_lahzeh_asheghi |

10 Jan 2021, 03:39 UTC794 viewsread 10 August 2026

"پناھ‌برتُ‌کہ‌بۍواژھ‌مرامیشنوے...°'

10 Jan 2021, 03:37 UTC730 viewsread 10 August 2026
Photo

••• "طَمِّني يا الله،فَأنا مَملوءٌ بِالخَوف؛ خدایاآرومم‌کن؛کھ‌من‌پر‌ازترسم . . !🌱 | @chand_lahzeh_asheghi |

2 Jan 2021, 07:07 UTC644 viewsread 10 August 2026
Photo

••• 1:20 دَر‌تـاریـخ‌بنوـیسید ما‌،دَرخٰوابِ‌نـاز‌بودیـم ڪه‌او‌رفٺـ.. #حاج‌قاسم #ابومهدی | @chand_lahzeh_asheghi |

1 Jan 2021, 21:50 UTC504 viewsread 10 August 2026
Video

••• 🖤 حاج قاسم یکسال گذشت، اما ذره‌ای از داغ شهادت تو در دل ما کم نشد! 🎥 بلند شو علمدار... #انتقام_سخت #ضربه_متقابل #شمارش_معکوس 🌹أللَّھُـمَ ؏َـجِّـلْ لِوَلیِڪْ ألْفَرَج🌹 | @chand_lahzeh_asheghi |

1 Jan 2021, 11:22 UTC352 viewsread 10 August 2026
Video

••• بنویســید در تــاریــخ ڪه غــــــ💔ــــــــــــم حـــاج قاســم برایـمان تــمـام نشدنیست...🥀 #شهید_سلیمانی | @chand_lahzeh_asheghi |

1 Jan 2021, 07:36 UTC321 viewsread 10 August 2026

الشَهٍیْد ؛ ٱبُومَهْدِیْ وَ حٰاج‌ قٰاسِم‌ كانا أُمَّةً...

1 Jan 2021, 07:35 UTC297 viewsread 10 August 2026

عَلمْدَاٰر بودی ؛ أینَ عمّار عَلیَّ بودی ؛ ‏امشب‌همه‌ازهرقشری ؛ برای تُو ؛ خواهندنوشت ؛ برای تُو ؛ که همه‌را دوست‌داشتی ... #حاج‌قاسم‌ما

29 Dec 2020, 16:15 UTC325 viewsread 10 August 2026
Photo

••• " یَا فاطِمَةَ الزَّهرا سَلام‌ُ الله؛ يَا أُمَّ الْحَسَنِ وَ الْحُسَيْنِ " ‏نام #تُ را بردیم در هیاهوی دنیا ما را صدا کن در هیاهوی قیامت ...🌿'-』 | @chand_lahzeh_asheghi |

28 Dec 2020, 14:13 UTC296 viewsread 10 August 2026
Video

••• الحمدللہ ڪہ مادَرَمے...🖤🥀 #حاج‌مھدی‌رسولے #فاطمیه | @chand_lahzeh_asheghi |

Showing the 12 most recent of 18 posts we hold for @chand_lahzeh_asheghi. 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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“"چَنـد لـحظہ عــاشقــی"” (@chand_lahzeh_asheghi), 53 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/chand_lahzeh_asheghi.

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.