@bileihn 最新活动 只要提交审核通过即可奖励20元京东E卡 不管是提交避雷/黑榜/差评/新闻,只要审核通过都可获得E卡奖励 😒避雷:那些年一些踩过的雷,投稿让大家尽量避避 🤬黑榜:骗钱/欺诈/无套/有病...等等的一些情节较为严重的可以投稿黑榜 😡差评:老师/中介服务不好,可以写差评以示警戒 🤪新闻:近期咱们海南修车圈有什么趣闻趣事都可以投稿,也可以转载
❤59👍52👏1🔥1

Channel
@bileihn
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
11,817subscribers
-715 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003818157605 |
|---|---|
| Type | Channel |
| Username | @bileihn |
| Created | 27 February 2026 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 18 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/bileihn |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 11:53 | 11,817 | -295 |
| 1 Sept 2026, 12:44 | 12,112 | -324 |
| 31 Aug 2026, 14:24 | 12,436 | -405 |
| 30 Aug 2026, 13:06 | 12,841 | -295 |
| 29 Aug 2026, 10:13 | 13,136 | +32 |
| 28 Aug 2026, 08:44 | 13,104 | +82 |
| 27 Aug 2026, 07:04 | 13,022 | +69 |
| 26 Aug 2026, 08:37 | 12,953 | -67 |
| 25 Aug 2026, 05:07 | 13,020 | +81 |
| 24 Aug 2026, 04:39 | 12,939 | +89 |
| 22 Aug 2026, 10:47 | 12,850 | +76 |
| 21 Aug 2026, 01:03 | 12,774 | +83 |
| 19 Aug 2026, 21:41 | 12,691 | +65 |
| 18 Aug 2026, 19:48 | 12,626 | +22 |
| 17 Aug 2026, 19:46 | 12,604 | -7 |
| 16 Aug 2026, 20:14 | 12,611 | +83 |
| 15 Aug 2026, 12:43 | 12,528 | -4 |
| 14 Aug 2026, 23:01 | 12,532 | first reading |
6 posts held, back to 27 February 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 30 pages 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 6 posts for this entry, the most recent from 29 July 2026. An engagement rate over an empty window would be a number about nothing.
235 reactions across 2 posts, in 5 distinct kinds. The most used accounts for 49.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 117 | 49.8% | |
| 👍 | 114 | 48.5% | |
| 🔥 | 2 | 0.851% | |
| 👏 | 1 | 0.426% | |
| 🥰 | 1 | 0.426% |
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 2 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 235 reactions 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 27 February 2026 to 29 July 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.
@bileihn 最新活动 只要提交审核通过即可奖励20元京东E卡 不管是提交避雷/黑榜/差评/新闻,只要审核通过都可获得E卡奖励 😒避雷:那些年一些踩过的雷,投稿让大家尽量避避 🤬黑榜:骗钱/欺诈/无套/有病...等等的一些情节较为严重的可以投稿黑榜 😡差评:老师/中介服务不好,可以写差评以示警戒 🤪新闻:近期咱们海南修车圈有什么趣闻趣事都可以投稿,也可以转载
❤59👍52👏1🔥1
以下举证格式可以点击一键复制 【榜单链接】: 【举证人员】: 【举证内容】:
以下投稿格式可以点击一键复制 【投稿类型】:#避雷 #黑榜 #差评 #新闻(可选) 【投稿留名】:(可匿名) 【投稿日期】: 【上榜人员】: 【上榜账号】: 【事件总结】:
海南全岛第三方记事频道 @bileihn 本频道完全公平 公正 自由开放,谁都可以进行投稿发布, 目前本频道收录:避雷/黑榜/差评/新闻趣事发布。 投稿联系 @hnjsbbot 左下角开始使用进行投稿 上榜人员如果对榜上事实有异可以联系管理员 @hnjsbbot 进行举证,举证有效即可删除榜单信息。 榜单投稿格式要求: 【投稿类型】:#避雷 #黑榜 #差评 #新闻(可选) 【投稿留名】:(可匿名) 【投稿日期】: 【上榜人员】: 【上榜账号】: 【事件总结】: 上榜人员如需进行举行请联系 @hnjsbbot 填写模板进行举证 榜单举证格式: 【榜单链接】: 【举证人员】: 【举证内容】: ⋙⋙⋙⋙⋙⋙⋙⋙⋙ 【避雷/黑榜/差评/新闻均由撰写人提供,本频道只做收录记载,如遇情况不属实可联系管理人员进行举证】 👍海南修车群 @yjiaen1
👍62❤58🔥1🥰1
海南记事本 投稿专员 @hnjsbbot
Channel created
Showing the 6 most recent of 6 posts we hold for @bileihn. 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.
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.
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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“避雷黑榜差评新闻记事本|海南三亚海口” (@bileihn), 11,817 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/bileihn.
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.