[ 图片 ] 编号:0110(黑榜) 呢称:#乔乔 地址:#天河 与你:qiaoqiao8800 与你:As888520 备注:(骗子) 个人解释:(无)

Channel
千秋—广佛黑榜
@guangfoheibang8
On this record: Growth · Engagement · Posts · Citations · Cite this entry
45subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002553380308 |
|---|---|
| Type | Channel |
| Username | @guangfoheibang8 |
| Created | Between 1 March 2025 and 14 April 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 September 2026 |
| On Telegram | t.me/guangfoheibang8 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Sept 2026, 02:38 | 45 | -1 |
| 10 Aug 2026, 14:30 | 46 | no change |
| 7 Aug 2026, 17:02 | 46 | first reading |
Engagement
13 posts held, back to 14 April 2025 — 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 13 posts for this entry, the most recent from 3 February 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
[ 图片 ] 编号:0109(黑榜) 昵称:#瑶妹 地址:#荔湾 与你:jjj789 备注:用的假图 个人解释:(无)
编号:0108(黑榜) 昵称:#玖儿 地址:#白云 与你:mmkk228 与你:chengyi99 备注:用的网图吹做 个人解释:(无)
编号:0107(黑榜) 昵称:#雯雯自聊无中介 地址:#番禺 与你:ly1234569 备注:狼友谈好价提前一天付课费,第二天狼友去上课找她本人需在谈好的价格上加100,要不就是给狼友换老师上课,狼友不同意让退款无果。 个人解释:狼友议价啰嗦
[ 图片 ] 编号:0106(黑榜) 昵称:#阮志权 电报号: @dianbaoziy 备注:骗取个人资料 个人解释:(无)
编号:0105(黑榜) 昵称: #思思 地址: #海珠 与你号:sisi7971 电话: 17602015073 电话: 13288600884 备注: 态度很差,戴保鲜膜口 个人解释:(无)
编号:0104(黑榜) 昵称: #子怡 地址: #佛山 #禅城 与你号: aa1109666 备注: 说是自聊自做,到了男人来接人 个人解释:(无)
编号:0103(黑榜) 昵称; #小猫咪 #小兔兔 地址:#广州 与你:258hfd 与你:145cvt 备注:两个号同一个人,收订后删好友 个人解释:(无)
编号:0102(黑榜) 昵称:#暖暖 地址:#广州 与你号:zz5656 备注:骗子中介收了1000米打飞机,做完要充VIP6999 个人解释:(无)
编号:0101(黑榜) 昵称:B企鹅 与你号:15966yyds 备注:#骗子 个人解释:(无)
编号:0100(黑榜) 昵称:#wwb 地址:#广州 与你:Aaa25800 备注:#骗子、盗图、黑中介 个人解释:(无)
编号:0099(黑榜) 昵称:#莹莹 地址:#天河 TG:@thyy333 TGID:8052890388 TG频道:https://t.me/thyy3333 备注:#骗子 个人解释:(无)
Showing the 12 most recent of 13 posts we hold for @guangfoheibang8. 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
Names
Channels on the register whose handles appear in this channel's posts.
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 11 September 2026 — this entry's latest reading, not the date you are reading this.
“千秋—广佛黑榜” (@guangfoheibang8), 45 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/guangfoheibang8.
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.