Telegram RegisterThe public register of Telegram

Channel

飞机社群(听读)

@china567

10 usernames

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

7,236subscribers

-1,349 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001299975464
TypeChannel
Usernames@cchina @china567 @chinawang @feijishequn @gyggg @tingdu @vipchina @vipchina8 @vipchina88 @vipchina888
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 August 2026
Measurements held18
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/china567

Growth

7,2368,5857,910.57 August 2026 — 8,585 subscribers7 August 2026 — 8,573 subscribers7 August 2026 — 8,573 subscribers7 August 2026 — 8,435 subscribers7 August 2026 — 8,435 subscribers10 August 2026 — 7,802 subscribers10 August 2026 — 7,798 subscribers12 August 2026 — 7,486 subscribers12 August 2026 — 7,486 subscribers12 August 2026 — 7,484 subscribers12 August 2026 — 7,485 subscribers12 August 2026 — 7,483 subscribers12 August 2026 — 7,471 subscribers12 August 2026 — 7,438 subscribers13 August 2026 — 7,418 subscribers13 August 2026 — 7,406 subscribers13 August 2026 — 7,361 subscribers14 August 2026 — 7,236 subscribers7 August 202614 August 2026
18 measurements spanning 7 days, net -1,349. 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 7,034–8,787 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 01:097,236-125
13 Aug 2026, 08:537,361-45
13 Aug 2026, 06:057,406-12
13 Aug 2026, 05:277,418-20
12 Aug 2026, 23:367,438-33
12 Aug 2026, 22:327,471-12
12 Aug 2026, 19:247,483-2
12 Aug 2026, 16:257,485+1
12 Aug 2026, 15:437,484-2
12 Aug 2026, 09:157,486no change
12 Aug 2026, 09:047,486-312
10 Aug 2026, 16:117,798-4
10 Aug 2026, 06:507,802-633
7 Aug 2026, 16:028,435no change
7 Aug 2026, 15:518,435-138
7 Aug 2026, 02:158,573no change
7 Aug 2026, 02:058,573-12
7 Aug 2026, 00:008,585first reading

Engagement

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

ERR · 30 days
2.95%
avg views ÷ 7,236 subscribers
Avg views / post
213
21 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
21
of 21 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 August 2026
Posts held21 (28 July 202612 August 2026)
Views total4,478
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 09:45 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.

Recent posts

12 Aug 2026, 03:24 UTC95 viewsread 12 August 2026
Photo

诈骗犯 原来估计是小面包 后面改 开心果 又换一个英文名 @btc88j 这个诈骗犯 大家小心

Signed 九天狐🦊(eSIM/月会员3.8U)

11 Aug 2026, 20:38 UTC121 viewsread 12 August 2026

靓号礼物 低价出售 t.me/nft/LibertyFigure-89888 t.me/nft/PoolFloat-88988 t.me/nft/PoolFloat-38888 t.me/nft/SnowMittens-38888 t.me/nft/CandyCane-85888 t.me/nft/MousseCake-85888 t.me/nft/XmasStocking-3456 t.me/nft/LightSword-3456 t.me/nft/StarNotepad-58 t.me/nft/WinterWreath-68

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

11 Aug 2026, 16:43 UTC108 viewsread 12 August 2026
Photo

虚假平台腾博会 @tbyl 推广负责人 @grgg68 张国荣 闽粤会 @MYHQ8 爱拼才会赢 @hzw68 2个虚假群 请大家务必上当受骗 我发10U进行测试了 哈哈哈

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

9 Aug 2026, 21:59 UTC180 viewsread 12 August 2026
Photo

@shaoye 找这个人做过机器人的,或者有合作的赶紧止损。 这家伙3年nft老人,以购买地步和借钱周转为由杀熟,内部群已确认跑路了,跑了盛丰27000U 发哥4000U。 圈子里还有谁被骗了? #接龙 七天 2.7万 锦鲤 1.685万 盛丰 2.7万 发哥 0.4万 嘉宾 0.295万 揽胜 0.295万 神医 0.59万 365 0.82万 温蒂 0.59万

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

5 Aug 2026, 18:27 UTC271 viewsread 12 August 2026
Photo

https://t.me/nft/MoneyPot-17463

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

5 Aug 2026, 14:29 UTC258 viewsread 12 August 2026

🎁新的礼物🎁 准备好迎接又一次或许是70% 的优惠了吗? ps :杜拉夫已升级 编号8

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

4 Aug 2026, 08:26 UTC272 viewsread 12 August 2026
Photo

我终于知道会员只有有缘人能懂 ✅八月发发发👏全网低价月3.8U 3个月仅12U|3月仅12U|12U|12U

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

4 Aug 2026, 01:39 UTC258 viewsread 12 August 2026
Photo

· 苹果下架Telegram:今天(8月4日),Telegram已从苹果iOS应用商店下架。 · TON价格波动:受消息影响,TON(现名GARM)价格短时下跌超5%,报1.33美元,并非“腰斩”。此外,不同平台数据有差异,也有显示其价格在3.5美元或1.6美元附近。 · 消息面的直接冲击:Telegram与TON生态深度绑定,App被下架直接触发了市场的恐慌性抛售。 · 历史的重演:Telegram及其代币此前已因印度监管禁令、CEO被捕等事件多次受挫,市场信心本就很脆弱。 · 技术面的脆弱:在消息公布前,TON价格已长期处于下行通道,任何风吹草动都容易引发剧烈波动。

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

3 Aug 2026, 16:04 UTC222 viewsread 12 August 2026
Photo

知名比特币硬件钱包Coldcard被曝存在随机数生成缺陷漏洞,导致大量离线“冷钱包”生成的“助记词”可被系统性推算。分析机构数据显示,截至8月3日,攻击者已从约5000个受影响钱包中盗走超过1755枚比特币,按当时市值计算约合1.1亿美元(约合人民币7.43亿元)

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

2 Aug 2026, 18:40 UTC224 viewsread 12 August 2026
Photo

时间都去哪了➤8月3日了 Premium=会员 一直进行中

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

1 Aug 2026, 19:57 UTC244 viewsread 12 August 2026
File

File, posted without a caption

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

1 Aug 2026, 19:57 UTC229 viewsread 12 August 2026
File

File, posted without a caption

Signed 九天狐🦊飞机商店@fjsdbot (eSIM|月会员3.8U)

Showing the 12 most recent of 21 posts we hold for @china567. 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 — 225,359 of 1,336,469entries 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.

Mentions

Named by 4 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.

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

“飞机社群(听读)” (@china567), 7,236 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/china567.

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.