Telegram RegisterThe public register of Telegram
Telegram profile photo for حب الحسین♥️

Channel

حب الحسین♥️

@hobolhoseinn

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

267subscribers

+0 since we began measuring on 26 September 2026

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

Register entry

Telegram ID-1002243514700
TypeChannel
Username@hobolhoseinn
Descriptionعاقبت بخیر منم که دلدارم تویی حسین جان🥹❤️ به والله که هیچکس جز حسینِ زهرا ماندنی نیست🌱 به گوشِ جان: https://t.me/HarfinoBot?start=e336de3cbb396e35-236
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 September 2026
Last confirmed live27 September 2026
Measurements held2
On Telegramt.me/hobolhoseinn

Growth

26726 Sept 2026, 23:47 — 267 subscribers27 Sept 2026, 00:22 — 267 subscribers26 Sept 2026, 23:4727 Sept 2026, 00:22
2 measurements taken within a single day. 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 266–268 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Sept 2026, 00:22267no change
26 Sept 2026, 23:47267first reading

Engagement

20 posts held, back to 4 August 2026 — 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.

ERR · 30 days
61.3%
avg views ÷ 267 subscribers
Avg views / post
164
12 posts measured
Reaction rate
5.30%
reactions ÷ views · ER floor
Posts in window
12
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 24 September 2026
Posts held20 (4 August 2026 – 24 September 2026)
Views total1,964
Reactions total104
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken27 Sept 2026, 00:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
105
Videos
47
Links
5

Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
11s
Average length
11s

Measured directly from 1 video 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.

Reaction mix

175 reactions across 20 posts, in 7 distinct kinds. The most used accounts for 37.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6637.7%
👌3017.1%
👍2514.3%
😭2313.1%
💔1810.3%
😍116.29%
🎉21.14%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 175 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 4 August 2026 to 24 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

24 Sept 2026, 21:53 UTC98 views2 reactionsread 27 September 2026

توقع از خَلق غصه می آورد توقع از خالق معجزه🌱

❤1👌1

22 Sept 2026, 17:55 UTC95 views1 reactionsread 27 September 2026

ای خواهرِ سلطانِ خراسان نِگَهی کن 💔

💔1

20 Sept 2026, 18:41 UTC123 views7 reactionsread 27 September 2026

آرزو میکنم که خدا از همه غم هایی ک تیشه به ریشه مون میزنه نجاتمون بده🌱

👍4👌1💔1😭1

20 Sept 2026, 18:28 UTC79 views7 reactionsread 27 September 2026

یا صاحب الزمان ما فقیر بن فقیر بن فقیریم💔

👍3❤1👌1💔1😭1

19 Sept 2026, 20:57 UTC98 views7 reactionsread 27 September 2026
Photo

آقا امیرالمؤمنین علیه السلام:

👍3👌2❤1😭1

17 Sept 2026, 21:55 UTC95 views8 reactionsread 27 September 2026

ولی زندگی و کسایی بردن که الان نشستن وسط بین الحرمین.....

❤3👌2👍1😍1😭1

10 Sept 2026, 20:20 UTC146 views12 reactionsread 27 September 2026

من را گوشه ای از شارع العباس دفن کنید و بر سنگ قبرم بنویسید؛ او به غیر از قمر منیر بنی هاشم کسی را نداشت💔

😭5👍2💔2❤1👌1😍1

9 Sept 2026, 19:52 UTC128 views12 reactionsread 27 September 2026

بارالها روزی اشکِ شوقی را هم میهمانِ چشمانِ ما کن🌱

❤4👌2💔2😭2👍1😍1

5 Sept 2026, 08:58 UTC388 views12 reactionsread 27 September 2026

اللهم عجل الولیک الفرج🌸

❤5💔2😭2👌1👍1😍1

5 Sept 2026, 08:58 UTC390 views11 reactionsread 27 September 2026

ولی نسل ما که همه چی و دید کاش حداقل ظهور امامش و هم ببینه.....

👌5👍2💔2❤1😍1

5 Sept 2026, 08:53 UTC178 views11 reactionsread 27 September 2026
Video

و مرا دوا کن نه از درد تن از تمام غم هایی که آرام آرام روحم را خسته کرده اند .

❤5👌2👍2💔1😍1

29 Aug 2026, 21:46 UTC146 views14 reactionsread 27 September 2026

و رحمت بر تو به ازای تمام دخترانی که از گور رهانیدی :)

❤8🎉2😍2👌1👍1

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

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“حب الحسین♥️” (@hobolhoseinn), 267 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/hobolhoseinn.

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.