Telegram RegisterThe public register of Telegram
Telegram profile photo for 广州佛山黑车防爆

Channel

广州佛山黑车防爆

@heichefangbao

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

11,657subscribers

+164 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1002170965618
TypeChannel
Username@heichefangbao
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live16 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/heichefangbao

Growth

11,49311,65711,5756 August 2026 — 11,493 subscribers6 August 2026 — 11,493 subscribers7 August 2026 — 11,523 subscribers8 August 2026 — 11,531 subscribers9 August 2026 — 11,550 subscribers11 August 2026 — 11,558 subscribers12 August 2026 — 11,566 subscribers13 August 2026 — 11,573 subscribers14 August 2026 — 11,612 subscribers16 August 2026 — 11,657 subscribers6 August 202616 August 2026
10 measurements spanning 9 days, net +164. 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 11,468–11,682 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 02:2711,657+45
14 Aug 2026, 14:4711,612+39
13 Aug 2026, 01:4711,573+7
12 Aug 2026, 00:5511,566+8
11 Aug 2026, 01:0111,558+8
9 Aug 2026, 23:3311,550+19
8 Aug 2026, 20:1611,531+8
7 Aug 2026, 22:3811,523+30
6 Aug 2026, 23:1311,493no change
6 Aug 2026, 20:0411,493first reading

Engagement

6 posts held, back to 8 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 20 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
12.8%
avg views ÷ 11,657 subscribers
Avg views / post
1,490
5 posts measured
Reaction rate
0.089%
reactions ÷ views · ER floor
Posts in window
5
of 6 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 2 of 5 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 15 August 2026
Posts held6 (8 July 202615 August 2026)
Views total7,467
Reactions total6
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 15:27 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

31 reactions across 3 posts, in 5 distinct kinds. The most used accounts for 58.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤣1858.1%
619.4%
💩412.9%
👏26.45%
🤡13.23%

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

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

15 Aug 2026, 12:28 UTC101 viewsread 15 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_209174135

14 Aug 2026, 05:30 UTC297 viewsread 15 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_209174135

12 Aug 2026, 05:30 UTC319 viewsread 13 August 2026
Photo

Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_209174135

6 Aug 2026, 04:03 UTC≈3,140 views2 reactionsread 15 August 2026
Photo

【排雷报告】https://t.me/guangfoyongle2020 【所有位置】白云永泰 【老师艺名】#小伊伊 【联系方式】@muo168 【人照几成】5成 【中介代聊】否 【上课价位】500p 【服务情况】基本xcz 【雷点说明】重点还是人照差太多了,服务是基础服务。老师嘴巴有味没敢🐍,传教士的时候,一直要忍住那个味(口臭),还有狐臭 PS排雷原因:人照低于7分像,符合排雷条件,永乐群已永久下榜拉黑,排雷奖励200元已经发放,排雷奖励188永乐通宝已经到账,辛苦工兵排雷致敬🫡

2

2 Aug 2026, 04:55 UTC≈3,610 views4 reactionsread 15 August 2026
Photo

【排雷报告】https://t.me/guangfoyongle2020 【所有位置】佛山 【老师艺名】#森迪 【联系方式】@sendi070 【人照几成】9成 【中介代聊】是 【上课价位】600p 【服务情况】遥控上楼,刚进门寒暄几句后,我借着上厕所时间,喊老师找永乐兑换,当时没去看老师飞机号,等我出来时候,老师问要等多久才能付款,我说等几分钟吧,随后老师说了一句那边收到了,我心头突然一阵,我就问老师那一般你到手是多少?老师模糊说了一下,已经实锤中介代聊,后面服务陪洗,舔咪咪,深喉,课表写的69没有,胸写36b,实际只有a,人照合一。xcz嫩妹三件套。事后我与妹子闲聊,妹子说刚来这边,网上找中介代聊的。 【雷点说明】没啥雷点,就是中介代聊。 PS排雷原因:中介代聊,符合排雷条件,永乐群已永久下榜拉黑,排雷奖励200元已经发放,排雷奖励188永乐通宝已经到账,辛苦工兵排雷致敬🫡

2👏2

8 Jul 2026, 11:17 UTC≈7,660 views25 reactionsread 15 August 2026
Photo

起因狼友问老师有位置吗,这个老师回复她满了,要介绍处女姐妹给狼友,狼友找到我,我只问她什么意思,这个老师回手无缘无故骂客人小傻逼,永乐群永久下榜踢群拉黑 老师:@Ttong08 频道:https://t.me/thtongtong0812

🤣18💩42🤡1

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

Citation-graph rank

Citation-graph rank — 65,125 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“广州佛山黑车防爆” (@heichefangbao), 11,657 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/heichefangbao.

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.