Telegram RegisterThe public register of Telegram
Telegram profile photo for 黑夜的窝

Channel

黑夜的窝

@heiyesjsh72

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

127subscribers

+6 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1004438352377
TypeChannel
Username@heiyesjsh72
DescriptionThis is our law firm's official channel. All content complies with laws and regulations, has been reviewed, and is free of violations. We reserve the right to pursue legal action against any malicious interference with our channel's operations.
Created26 July 2026measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held3
On Telegramt.me/heiyesjsh72

Previous handles

@heiyesjsh72 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@heiyesjsh72
held 9 August 20269 August 2026

Growth

1211271248 Aug 2026, 03:47 — 121 subscribers8 Aug 2026, 14:37 — 127 subscribers9 Aug 2026, 02:15 — 127 subscribers8 Aug 2026, 03:479 Aug 2026, 02:15
3 measurements taken within a single day, net +6. 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 120–128 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 02:15127no change
8 Aug 2026, 14:37127+6
8 Aug 2026, 03:47121first reading

Engagement

15 posts held, back to 26 July 2026the 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.

ERR · 30 days
86.6%
avg views ÷ 127 subscribers
Avg views / post
110
11 posts measured
Reaction rate
0.903%
reactions ÷ views · ER floor
Posts in window
15
of 15 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. It is computed over the 4 of 11 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held15 (26 July 20268 August 2026)
Views total1,210
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 02:15 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
11
Links
8

Lifetime counters from Telegram’s own channel header, read 9 August 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.

Reaction mix

4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
250.0%
👍250.0%

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 4 of the 15 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 26 July 2026 to 8 August 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

7 Aug 2026, 15:07 UTC94 views2 reactionsread 9 August 2026
Photo

🛡️🟰零作用 https://t.me/xu_o5201314 @ccyrp

👍2

7 Aug 2026, 11:58 UTC102 views1 reactionsread 9 August 2026
Photo

根据客户要求以屏蔽此频道与账户 https://t.me/+jHBPg-imKfwyNTlh @qlcnb

1

30 Jul 2026, 01:54 UTCviews —

黑夜的窝 pinned «你好, 我的工作内容包括: 1. 解除群组、账号和频道的限制 2. 封禁任何频道、群组或账号 3. 去除账号、群组和频道的诈骗标记 4. 恢复任何被封的频道、账号或群组 5. 保护频道、群组或账号不被封禁 请联系我 @heiyefh58_bot @hausywWk»

30 Jul 2026, 01:54 UTC174 viewsread 9 August 2026

你好, 我的工作内容包括: 1. 解除群组、账号和频道的限制 2. 封禁任何频道、群组或账号 3. 去除账号、群组和频道的诈骗标记 4. 恢复任何被封的频道、账号或群组 5. 保护频道、群组或账号不被封禁 请联系我 @heiyefh58_bot @hausywWk

30 Jul 2026, 00:54 UTC171 viewsread 9 August 2026
Photo

https://t.me/ZCYB886 This channel violates the terms of service of Telegram

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

“黑夜的窝” (@heiyesjsh72), 127 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/heiyesjsh72.

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.