Telegram RegisterThe public register of Telegram
Telegram profile photo for 黑料不打烊最新地址 https://cbdy30.com

Channel

黑料不打烊最新地址 https://cbdy30.com

@heiliao5

On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

26,077subscribers

+3,415 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001934345355
TypeChannel
Username@heiliao5
Created23 June 2023 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live26 October 2026
Measurements held48
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/heiliao5

Topic

Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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

22,66226,07724,369.57 August 2026 — 22,662 subscribers8 August 2026 — 22,674 subscribers9 August 2026 — 22,697 subscribers10 August 2026 — 22,721 subscribers11 August 2026 — 22,752 subscribers12 August 2026 — 22,767 subscribers13 August 2026 — 22,778 subscribers15 August 2026 — 22,813 subscribers16 August 2026 — 22,855 subscribers17 August 2026 — 22,897 subscribers18 August 2026 — 22,910 subscribers19 August 2026 — 22,927 subscribers20 August 2026 — 22,952 subscribers22 August 2026 — 22,983 subscribers24 August 2026 — 23,028 subscribers25 August 2026 — 23,076 subscribers26 August 2026 — 23,119 subscribers27 August 2026 — 23,145 subscribers28 August 2026 — 23,162 subscribers29 August 2026 — 23,165 subscribers29 August 2026 — 23,187 subscribers30 August 2026 — 23,206 subscribers31 August 2026 — 23,226 subscribers2 September 2026 — 23,230 subscribers3 September 2026 — 23,255 subscribers4 September 2026 — 23,318 subscribers7 September 2026 — 23,472 subscribers10 September 2026 — 23,583 subscribers12 September 2026 — 23,687 subscribers14 September 2026 — 23,775 subscribers16 September 2026 — 23,836 subscribers18 September 2026 — 23,896 subscribers1 October 2026 — 24,536 subscribers6 October 2026 — 24,707 subscribers10 October 2026 — 25,006 subscribers13 October 2026 — 25,240 subscribers15 October 2026 — 25,295 subscribers16 October 2026 — 25,362 subscribers17 October 2026 — 25,423 subscribers18 October 2026 — 25,486 subscribers19 October 2026 — 25,568 subscribers20 October 2026 — 25,679 subscribers21 October 2026 — 25,764 subscribers22 October 2026 — 25,857 subscribers23 October 2026 — 25,921 subscribers24 October 2026 — 25,999 subscribers25 October 2026 — 26,044 subscribers26 October 2026 — 26,077 subscribers7 August 202626 October 2026
48 measurements spanning 80 days, net +3,415. 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 22,150–26,589 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 48
Measured (UTC)SubscribersChange
26 Oct 2026, 10:1926,077+33
25 Oct 2026, 10:3826,044+45
24 Oct 2026, 14:0925,999+78
23 Oct 2026, 12:4525,921+64
22 Oct 2026, 14:0525,857+93
21 Oct 2026, 08:3625,764+85
20 Oct 2026, 05:5925,679+111
19 Oct 2026, 03:0025,568+82
18 Oct 2026, 01:2625,486+63
17 Oct 2026, 00:0025,423+61
16 Oct 2026, 01:3025,362+67
15 Oct 2026, 02:0825,295+55
13 Oct 2026, 21:1925,240+234
10 Oct 2026, 11:5525,006+299
6 Oct 2026, 10:1724,707+171
1 Oct 2026, 06:0024,536+640
18 Sept 2026, 10:1923,896+60
16 Sept 2026, 03:0123,836+61
14 Sept 2026, 11:0223,775+88
12 Sept 2026, 17:3823,687first reading

Engagement

11 posts held, back to 23 June 2023 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 115 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
—
no view readings in window
Avg views / post
—
no view readings
Reaction rate
—
this channel exposes no reaction counts
Posts in window
3
of 11 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 October 2026
Posts held11 (23 June 2023 – 24 October 2026)
Views total—
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Oct 2026, 07:18 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.

Reaction mix

834 reactions across 3 posts, in 12 distinct kinds. The most used accounts for 56.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤47156.5%
👍22426.9%
👎273.24%
😁253.00%
👏192.28%
🥰172.04%
🤣131.56%
🖕121.44%
🐳101.20%
🔥60.719%
🥴60.719%
🎃40.48%

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

Measured over the 11 most recent posts we hold, published 23 June 2023 to 24 October 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

1 Oct 2026, 03:28 UTCviews —

Channel name was changed to «黑料不打烊最新地址 https://cbdy16.com»

10 Mar 2025, 13:29 UTC≈238,000 views217 reactionsread 26 October 2026

黑料不打烊,吃瓜24小时不停 为防止家淫们吃瓜迷路,特邀请大家加入备份群! 吃瓜预览备份群:https://telegram.me/hlbdy3 吃瓜群众备份群:https://telegram.me/hlbdy3 吃瓜网址备份群:https://telegram.me/hlbdy4

❤140👍28👎16🖕12🐳10🥰9👏2

23 Jun 2023, 14:19 UTC≈298,000 views476 reactionsread 26 October 2026

<<<点击此处解除敏感群组限制>>> <<<点击此处安装中文语言包>>> 黑料不打烊最新地址(10/22更新) 免翻墙入口:https://cbdy29.com 永久入口需翻墙:https://hlbdy1.com/ 永久入口需翻墙:https://hl365.com/ App下载地址:https://h9g6.oldcvlmg.cc 官方免费Q群:https://www.zzwewtzu.cc/t/9rle73 ——————————————————- 撸友福利:https://ca27.pprqsncp.cc 官方推特:https://x.com/heiliaobdy4 官方电报(telegram)群:https://telegram.me/heiliao5 ——————————————————————- 官方tg资源频道一:https://telegram.me/hlbdy1com 官方tg活跃群组一:https:…

❤236👍155😁22👏15🤣13👎11🥰8🔥6

23 Jun 2023, 14:18 UTC≈169,000 views141 reactionsread 26 October 2026
Photo

解除敏感群组限制 步骤一:首先确认自己账号设置了 username(个人id) 【图一】 步骤二:复制以上网址到浏览器,登陆网页版TG https://web.telegram.org/ 【图二】 步骤三:验证码非短信,而是在你已经登陆的app里的数字验证码(TG官方给你发了一条验证码消息在你的TG App) 【图三】 步骤四:Settings - Privacy and security - Sensitive Content - 勾选 Disable filtering 【图四+图五+图六】 步骤五:勾选图片上的开关(勾选关闭敏感内容过滤)【 图五】 步骤六:重新打开Telegram 加群 注:有些国家的号码,没这设置,不能打开,解决办法只有换绑手机号码 例如: 印度尼西亚(印尼)+62的号码无法解此限制,没有此选项(telegram会根据当地政府要求做一些限制)

❤95👍41😁3👏2

Showing the 11 most recent of 11 posts we hold for @heiliao5. 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.

Posts edited after publishing

@heiliao5 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
24 October 2026

Mentions

Named by 2 registered channels — 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.

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

“黑料不打烊最新地址 https://cbdy30.com” (@heiliao5), 26,077 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/heiliao5.

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.