#朵儿 #惠城区 #龙丰 有地方 400p 800pp 私聊: @duoer20033 频道: https://t.me/duoer200331 双向: @Tetssifbot

Channel
惠州资源公开榜
@hzbg1
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
24,217subscribers
+713 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 | -1001675901018 |
|---|---|
| Type | Channel |
| Username | @hzbg1 |
| Description | #惠州 #惠城 惠州联邦修车群公开榜。@hztgs |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/hzbg1 |
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 84% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 16:01 | 24,217 | +48 |
| 19 Sept 2026, 02:58 | 24,169 | +9 |
| 16 Sept 2026, 18:19 | 24,160 | +31 |
| 14 Sept 2026, 18:36 | 24,129 | +35 |
| 13 Sept 2026, 08:18 | 24,094 | +10 |
| 11 Sept 2026, 09:02 | 24,084 | +38 |
| 8 Sept 2026, 16:38 | 24,046 | +51 |
| 5 Sept 2026, 09:54 | 23,995 | +18 |
| 3 Sept 2026, 11:56 | 23,977 | +28 |
| 2 Sept 2026, 02:57 | 23,949 | +10 |
| 1 Sept 2026, 06:18 | 23,939 | +6 |
| 31 Aug 2026, 05:54 | 23,933 | +19 |
| 30 Aug 2026, 07:26 | 23,914 | +24 |
| 29 Aug 2026, 10:26 | 23,890 | +16 |
| 28 Aug 2026, 09:28 | 23,874 | +13 |
| 27 Aug 2026, 07:05 | 23,861 | +11 |
| 26 Aug 2026, 05:56 | 23,850 | +12 |
| 25 Aug 2026, 04:37 | 23,838 | +10 |
| 23 Aug 2026, 23:44 | 23,828 | +28 |
| 22 Aug 2026, 05:17 | 23,800 | first reading |
Engagement
166 posts held, back to 5 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 66 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 10.5%
- avg views ÷ 24,217 subscribers
- Avg views / post
- 2,530
- 42 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 42
- of 166 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.
| Window | Rolling 30 days · latest post in window 29 September 2026 |
|---|---|
| Posts held | 166 (5 August 2026 – 29 September 2026) |
| Views total | 106,336 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 20:33 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
- 31
- Links
- 126
Lifetime counters from Telegram’s own channel header, read 29 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
- 6m 18s
- Average length
- 9s
Measured directly from 41 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
#小可 #惠城区 #江北 有地方 500p 1000pp 私聊: @xiaokeke88887 双向: https://t.me/xiaoke8888889909 双向:@xiaoke0998766_bot
#安娜 #惠城区 #河南岸 有地方 600p 1100pp 私聊: @fafa914914 频道: https://t.me/+39r_GhQoJF1kMWYx 双向: @xixi99999_bot
#泰国车厘子 #惠城区 #河南岸 有地方 全套650 1p 快餐450 1p 联系: @SWLMSS68 频道: https://t.me/TLDNHSS 双向: @SWLMSSbot
#米娜 #惠城区 #江北 有地方 500p 1000pp 私聊: @qingqing0061 频道: https://t.me/Qingqing55881 双向: @qingqingi_bot
#娜塔莎 #惠城区 #麦地 有地方 700p 1400pp 混血 私聊: @hjfwejj 频道: https://t.me/Mgtasha25 双向: @Guoguozzzbot
#林希 #惠城区 #河南岸 有地方 700p 1300pp 联系: @linxi1828 频道: https://t.me/linxi18288 双向机器人: @linxi1828bot
#玖悦 #惠城区 #河南岸 有地方 700p 1300pp 联系:@jiuyue697 频道: https://t.me/qingning2367 双向机器人: @qingning697bot
#苏宁 #惠城区 #龙丰 有地方 700p 1300pp 私聊: @suning165 频道: https://t.me/suning1658 双向: @suning165bot
#伊娃 #惠城区 #河南岸 有地方 700p1300pp 联系: @asxx5689 频道: https://t.me/SDS125 双向: @zxa1sbot
#小白 #惠城区 #江北 有地方 600p1200pp 36E冷白皮 联系: @xiaobai7788996 频道: https://t.me/xiaobai77556 双向: @xiaobai369_bot
#雪糕 #惠城区 #河南岸 有地方 700p 1300pp 联系:@hm57883 频道:https://t.me/ghj35677 双向:@hzyouyanbot
Showing the 12 most recent of 166 posts we hold for @hzbg1. 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
@hzbg1 edited 10 posts 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
- 10 August 2026
- Most recent edit
- 29 September 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
@anqi2520 · 2,6113 posts🌈🌈一字马舞蹈老师
@jiayang6988 · 7863 posts苏宁🍭的课间
@suning1658 · 1,4023 posts紫嫣~🍓(SPA红牌)🍓~麦地
@ziyan565 · 1,4603 posts伊琳生活频道
@a125588 · 1,3582 posts小曼95/98 开课河南岸一条龙抓龙筋可上门
@a135321298 · 2,5942 posts惠州君欣后院
@asd18868 · 1,8002 posts冰儿的温馨小窝
@bb52102 · 5,2622 posts🎲骰子第七面🤪嘟嘟
@dudu78899 · 1,9242 posts惠城~朵儿🌼的个人朋友圈
@duoer200331 · 92 posts惠州茉莉🌹👠🉑双 🉑🐍 95/98开课中
@huizhoumolihua · 2,3552 posts佳妮宝贝~🍇麦地开课🍇
@jiani9987 · 2,5702 posts知夏
@KKeKe688 · 2,0892 posts玲玲的小屋
@linglingdexiaowu · 2,6622 posts娜塔莎(加拿大华侨)💋💋
@Mgtasha25 · 8082 posts阿楠 💃172大长腿,纯御系
@songyike18 · 1,7282 posts惠城区南线 欣欣子(开课中)
@wain98 · 3,5722 posts婉婉~🎈舞蹈老师🎈麦地开
@wanwan6549 · 5762 posts小七笔记
@xiaoqi999995 · 1,6522 posts大咪咪的咪圈
@damimi7777 · 1,9711 post芊芊小花园
@dandan01123 · 1,7351 post兮兮
@hcxixi521 · 1,4871 post08年紧致小雯雯刚下海🌊
@jiajia0209 · 2,0541 post小番茄🍅麦地开课
@xkaofanqie6651 · 821 post
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.
Handles this channel named that no longer answer
- Dead references
- 4
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 3
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@hzbg1 named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 2 posts, 27 August 2026 – 29 August 2026 · confirmed gone 28 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 27 August 2026 – 27 August 2026 · confirmed gone 10 September 2026 (two independent sightings — see how we confirm a dead handle)evidenced
named in 1 post, 10 August 2026 – 10 August 2026 · confirmed gone 31 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 28 September 2026 – 28 September 2026
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.
“惠州资源公开榜” (@hzbg1), 24,217 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/hzbg1.
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.