🔴全国友群🔴 🥇以下 航路友群 福利群 有免费上榜 🥇也有收费老群 武汉中转站 南京中转站 杭州中转站 西安中转站 上海中转站 珠海中转站 嘉兴中转站 南宁中转站 宁波中转站 合肥中转站 长沙中转站 苏州中转站 东莞中转站 广州中转站 义乌中转站

Channel
全球吃瓜防骗曝光榜
@bikan888
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
56,396subscribers
-1,879 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1002150738793 |
|---|---|
| Type | Channel |
| Username | @bikan888 |
| Description | 本频道承接所有骗术曝光 欢迎各大群频道主以及老师和狼友投稿曝光 投稿联系: @jiaoyou888bot |
| Created | Between 1 May 2024 and 31 October 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/bikan888 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 12:01 | 56,396 | -527 |
| 3 Sept 2026, 15:21 | 56,923 | -320 |
| 2 Sept 2026, 10:53 | 57,243 | -309 |
| 1 Sept 2026, 09:58 | 57,552 | -200 |
| 31 Aug 2026, 10:44 | 57,752 | -203 |
| 30 Aug 2026, 08:08 | 57,955 | -292 |
| 29 Aug 2026, 09:45 | 58,247 | -225 |
| 28 Aug 2026, 06:22 | 58,472 | -49 |
| 27 Aug 2026, 04:56 | 58,521 | -73 |
| 26 Aug 2026, 04:32 | 58,594 | -99 |
| 25 Aug 2026, 03:14 | 58,693 | -11 |
| 23 Aug 2026, 21:45 | 58,704 | -45 |
| 22 Aug 2026, 02:29 | 58,749 | +24 |
| 20 Aug 2026, 16:44 | 58,725 | +72 |
| 19 Aug 2026, 15:03 | 58,653 | +103 |
| 18 Aug 2026, 18:03 | 58,550 | +51 |
| 17 Aug 2026, 19:15 | 58,499 | +100 |
| 16 Aug 2026, 18:13 | 58,399 | -69 |
| 15 Aug 2026, 06:45 | 58,468 | +335 |
| 14 Aug 2026, 00:14 | 58,133 | first reading |
Engagement
121 posts held, back to 30 July 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 69 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.433%
- avg views ÷ 56,396 subscribers
- Avg views / post
- 244
- 111 posts measured
- Reaction rate
- 0.154%
- reactions ÷ views · ER floor
- Posts in window
- 111
- of 121 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 23 of 111 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 September 2026 |
|---|---|
| Posts held | 121 (30 July 2026 – 6 September 2026) |
| Views total | 27,104 |
| Reactions total | 26 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Sept 2026, 08:04 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
- 694
- Videos
- 11
- Links
- 90
Lifetime counters from Telegram’s own channel header, read 6 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.
Reaction mix
30 reactions across 20 posts, in 2 distinct kinds. The most used accounts for 70.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 21 | 70.0% | |
| 👍 | 9 | 30.0% |
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 25 of the 121 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 30 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 121 most recent posts we hold, published 30 July 2026 to 6 September 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
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6141425904
🔴全国友群🔴 🥇以下 航路友群 福利群 有免费上榜 🥇也有收费老群 武汉中转站 南京中转站 杭州中转站 西安中转站 上海中转站 珠海中转站 嘉兴中转站 南宁中转站 宁波中转站 合肥中转站 长沙中转站 苏州中转站 东莞中转站 广州中转站 义乌中转站
❤1
🔴全国友群🔴 🥇以下 航路友群 福利群 有免费上榜 🥇也有收费老群 武汉中转站 南京中转站 杭州中转站 西安中转站 上海中转站 珠海中转站 嘉兴中转站 南宁中转站 宁波中转站 合肥中转站 长沙中转站 苏州中转站 东莞中转站 广州中转站 义乌中转站
🔴全国友群🔴 🥇以下 航路友群 福利群 有免费上榜 🥇也有收费老群 武汉中转站 南京中转站 杭州中转站 西安中转站 上海中转站 珠海中转站 嘉兴中转站 南宁中转站 宁波中转站 合肥中转站 长沙中转站 苏州中转站 东莞中转站 广州中转站 义乌中转站
🔴全国友群🔴 🥇以下 航路友群 福利群 有免费上榜 🥇也有收费老群 武汉中转站 南京中转站 杭州中转站 西安中转站 上海中转站 珠海中转站 嘉兴中转站 南宁中转站 宁波中转站 合肥中转站 长沙中转站 苏州中转站 东莞中转站 广州中转站 义乌中转站
这个钰钰 之前在哪个群上过榜忘记是哪个了 自称是个人老师有教师 发位置到了之后说是让客服接 接到一个非常隐秘的地方给我发的位置是摩卡洗车行 然后电话指引,到了之后是一个会所里面都是30以上的女的 然后说先交钱才能给叫女孩 交完钱之后开始服务穿那个一次性裤头 全装服务做了能有十分钟按摩之后跟我说咱们这都是手推没有啪啪 啪啪得加钱充卡 但是这个人课表上面写的1000 60分钟 要像在这pp得个3 5千纯套路
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6141425904
🔴全国友群🔴 🥇以下 航路友群 福利群 有免费上榜 🥇也有收费老群 武汉中转站 南京中转站 杭州中转站 西安中转站 上海中转站 珠海中转站 嘉兴中转站 南宁中转站 宁波中转站 合肥中转站 长沙中转站 苏州中转站 东莞中转站 广州中转站 义乌中转站
🔴全国友群🔴 🥇以下 航路友群 福利群 有免费上榜 🥇也有收费老群 武汉中转站 南京中转站 杭州中转站 西安中转站 上海中转站 珠海中转站 嘉兴中转站 南宁中转站 宁波中转站 合肥中转站 长沙中转站 苏州中转站 东莞中转站 广州中转站 义乌中转站
Telegram必备的搜索引擎,极搜JISOU帮你精准找到,想要的群组、频道、视频、音乐 👉 t.me/jisou2?start=a_6141425904
🔴全国友群🔴 🥇以下 航路友群 福利群 有免费上榜 🥇也有收费老群 武汉中转站 南京中转站 杭州中转站 西安中转站 上海中转站 珠海中转站 嘉兴中转站 南宁中转站 宁波中转站 合肥中转站 长沙中转站 苏州中转站 东莞中转站 广州中转站 义乌中转站
Showing the 12 most recent of 121 posts we hold for @bikan888. 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
Named by 3 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.
@ajinkya · 7,34359 posts南宁中转站
@al_qunfudhah · 6,21359 posts合肥中转站
@channelington · 6,71159 posts嘉兴中转站
@dangzaiwoxinzhong · 6,42859 posts宁波中转站
@dashboardapp · 6,65759 posts杭州中转站
@dwflabz · 7,46159 posts武汉中转站
@eldor_khalliyev · 8,14959 posts苏州中转站
@g_40000 · 7,89559 posts西安中转站
@hiailand · 6,43659 posts上海中转站
@iq748 · 6,86159 posts东莞中转站
@jukedeckai · 6,82759 posts长沙中转站
@livejournall · 6,61459 posts义乌中转站
@louvrehotels · 6,29559 posts广州中转站
@opros_siki · 6,69459 posts珠海中转站
@toncoins101 · 5,94259 posts极搜🔍资源搜索@JISOU
@jisou2 · 1,652,95628 posts【黑帽子cvv联盟】全球撸美金项目 钓鱼 渗透 爆库 脱裤 POS机 ccshop商店
@hmzlm000 · 28,9801 post【福利群】【黑帽子cvv联盟】全球撸美金总部
@hmzlm888 · 22,5051 post全国大圈极品聚集总部
@hnanjingjujidi · 23,1041 post深圳罗湖巨乳口爆环保❤️不限次数
@luohu999qiqi · 11,6781 post美团查档—防失联
@mtcd11 · 16,0211 postSpam Info Bot
@SpamBot · 34,238,2571 post夜色下的希望🥇🥇🥇
@Ye_se2022 · 26,1131 post全国修车同城总部
@zltal · 80,0891 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
- 6
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 5
- vacant every time we have ever looked
@bikan888 named 6 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 3 posts, 8 August 2026 – 10 August 2026 · confirmed gone 9 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 4 posts, 15 August 2026 – 22 August 2026
named in 4 posts, 15 August 2026 – 22 August 2026
named in 3 posts, 31 August 2026 – 4 September 2026
named in 3 posts, 31 August 2026 – 4 September 2026
named in 3 posts, 31 August 2026 – 4 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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“全球吃瓜防骗曝光榜” (@bikan888), 56,396 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/bikan888.
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.