赞助商广告: 新币公群K2117 皇冠822 开群至今0纠纷 港车私户,公户接内港购汇,跨境通,港港精料快杀,外港国际电汇 (精料大区分卡接料,国内资金秒到账) 户充足,价格冰点,查帐快,回U快。 专卡免户费,价格你说了算。 客服: @XBKpay1 客服: @XBKpay2
👍3❤2🔥1

Channel
@jiufangyum
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
33,144subscribers
-6,800 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1002262689696 |
|---|---|
| Type | Channel |
| Usernames | @jiufangyum @ww_000 |
| Description | ✅代理定制✅飞机号 ✅飞机会员。定制稳定高速飞机代理(直连) ☎️双向联系: @SHDLIPbot ☎️客服联系: @SHDLIP 🛒自助机器人: @sihai818bot |
| Created | Between 1 October 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/jiufangyum |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 11:02 | 33,144 | -224 |
| 4 Sept 2026, 05:22 | 33,368 | -137 |
| 2 Sept 2026, 19:49 | 33,505 | -145 |
| 1 Sept 2026, 19:15 | 33,650 | -229 |
| 31 Aug 2026, 18:35 | 33,879 | -152 |
| 30 Aug 2026, 16:54 | 34,031 | -171 |
| 29 Aug 2026, 15:15 | 34,202 | -61 |
| 28 Aug 2026, 16:52 | 34,263 | -108 |
| 27 Aug 2026, 15:39 | 34,371 | -1,626 |
| 26 Aug 2026, 17:54 | 35,997 | -989 |
| 25 Aug 2026, 19:16 | 36,986 | -148 |
| 24 Aug 2026, 16:05 | 37,134 | -123 |
| 23 Aug 2026, 03:16 | 37,257 | -74 |
| 21 Aug 2026, 14:25 | 37,331 | -19 |
| 20 Aug 2026, 17:07 | 37,350 | -70 |
| 19 Aug 2026, 14:38 | 37,420 | -107 |
| 18 Aug 2026, 11:13 | 37,527 | -100 |
| 17 Aug 2026, 14:38 | 37,627 | -159 |
| 16 Aug 2026, 05:18 | 37,786 | -130 |
| 14 Aug 2026, 14:27 | 37,916 | first reading |
12 posts held, back to 6 July 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 50 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 September 2026 |
|---|---|
| Posts held | 12 (6 July 2025 – 6 September 2026) |
| Views total | 354 |
| Reactions total | 6 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Sept 2026, 15:15 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.
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.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
499 reactions across 12 posts, in 16 distinct kinds. The most used accounts for 65.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 325 | 65.1% | |
| 👍 | 38 | 7.62% | |
| 🔥 | 33 | 6.61% | |
| 🥰 | 27 | 5.41% | |
| 👎 | 14 | 2.81% | |
| 👏 | 11 | 2.20% | |
| 😁 | 10 | 2.00% | |
| ⚡ | 8 | 1.60% | |
| 🏆 | 7 | 1.40% | |
| 🎉 | 6 | 1.20% | |
| 👌 | 5 | 1.00% | |
| 🙊 | 5 | 1.00% | |
| 🤝 | 4 | 0.802% | |
| ❤🔥 | 3 | 0.601% | |
| 🤩 | 2 | 0.401% | |
| 😱 | 1 | 0.2% |
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 12 of the 12 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 499 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 6 July 2025 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.
赞助商广告: 新币公群K2117 皇冠822 开群至今0纠纷 港车私户,公户接内港购汇,跨境通,港港精料快杀,外港国际电汇 (精料大区分卡接料,国内资金秒到账) 户充足,价格冰点,查帐快,回U快。 专卡免户费,价格你说了算。 客服: @XBKpay1 客服: @XBKpay2
👍3❤2🔥1
😔一站式机器人商铺😔 ✅【代理定制】✅【TG号】 ✅【会员星星】 🇦🇪 24小时自助下单 🇦🇪 机器人自助售后 🇦🇪价格透明 🇦🇪无需等待人工回复 🇦🇪老客户、新客户均可使用 代理定制 模式1:高速不限流量套餐: 独享线路 中途可自助更换代理线路 模式2:企业极速流量套餐: 企业级线路2条 续费无需断网换线 🤓余额三通 可用代理-TG号-会员星星 ❗️防失联模式:可添加其他号为管理员 共享余额 也同步账单明细 :合适(团队 群组 多号)专用 😔福利模式: ✅ 您已加入频道,免费代理可用。 🎁 每日签到福利:1 天 + 1GB流量 🤝转发分享 邀请每1个好友:送 5天3G流量 🇳🇷联系客服:@SHDLIP 🤓自助机器人:@sihai818bot
❤19👍5🥰5👏2🎉1🔥1
🇦🇪用户名出售🇦🇪 @ttt111 @ooo555 @vvv777 @ggg000 @iii666 @lll555 @ccllll @ccc000 @oo2222 @cccc555 @hhhh888 @jjj1111 @ssss000 @wwww555 @zzzz777 @zzzz999 @ee_555 @ll_111 @ww_000 @zz_333 🇳🇷购买联系: @SHDLIP 🤓注: 以上为NFT永久用户名 所有权永久属于你 即使账户注销也可通过重新注册账户再次使用该用户名 能有效防止账号被强制注销和冻结 也能防止举报 有助于 业务发展 防止客户流失 😩
❤7👍3🔥2🎉1🥰1😁1
目前很多用户购买高速代理后 还是不懂会操作更换代理 机器人是具备售后功能的 其实很简单 一共就两步。 第一步:点击更换代理 第二步:选择你要换那个节点 重要提醒⚠️ 一定要选择你要更换的节点几 显示代理更换成功 才算完成,很多人点了更换代理以为换了其实还是在用旧代理 否则一人有多条代理就乱了。 🤓自助机器人:@sihai818bot
❤6👍4👏2🔥1😱1
🔥自助机器人正式上线! 做了代理两年多,一直都是人工处理订单。这次上线机器人,不是为了减少服务,而是为了让大家下单更快捷、更方便, 无需等待 。人工售后依然一直在。已购买的客户可联系客服把代理添加到你账户 😔一站式机器人商铺😔 ✅【代理定制】✅【TG号】 ✅【会员星星】 🇦🇪 24小时自助下单 🇦🇪 机器人自助售后 🇦🇪价格透明 🇦🇪无需等待人工回复 🇦🇪老客户、新客户均可使用 代理定制 模式1:高速不限流量套餐: 独享线路 中途可自助更换线路 模式2:企业极速流量套餐: 企业级线路2条 续费无需断网换线 🤓余额三通 可用代理-TG号-会员星星 ❗️防失联模式:可添加其他号为管理员 共享余额 也同步账单明细 :合适(团队 群组 多号)专用 😔福利模式: ✅ 您已加入频道,免费代理可用。 🎁 每日签到福利:1 天 + 1GB流量 🤝转发分享 邀请每1个好友:送 7天5G流量 🇳🇷联系客服:@SHDLIP 🤓自助机器人:@si
❤30🔥5👍3🥰2👏1
图1安卓 图2苹果 ❤️定制高速代理 ❤️ 🤩包月代理🤩11U约(85¥) 🙃包季代理🙃27U约(200¥) 🤪半年代理🤪50U约(360¥) 🥳包年代理🥳85U 约(600¥) 另有 团队高速定制 多人高速定制 不限设备 不限流量 不卡顿 不掉线 支持 😚支付宝 🥸微信😄USDT 🇱🇷🇲🇦🇬🇮🇨🇽🇬🇱🇯🇪🇨🇨🇧🇭 另出 飞机号 批发 会员代开 ☹️全天在线 联系:@SHDLIP ☹️双向 联系机器人 @SHDLIPbot
❤72👎14👍6⚡4🤝4👌3👏3🔥3
图1安卓 图2苹果 ❤️定制高速代理 ❤️ 🤩包月代理🤩11U约(85¥) 🙃包季代理🙃27U约(200¥) 🤪半年代理🤪50U约(360¥) 🥳包年代理🥳85U 约(600¥) 另有 团队高速定制 多人高速定制 不限设备 不限流量 不卡顿 不掉线 支持 😚支付宝 🥸微信😄USDT 🇱🇷🇲🇦🇬🇮🇨🇽🇬🇱🇯🇪🇨🇨🇧🇭 另出 飞机号 批发 会员代开 ☹️全天在线 联系:@SHDLIP ☹️双向 联系机器人 @SHDLIPbot
❤49🥰5🙊5⚡4🔥4🏆2👌2👍2
一直在做TG代理只是没空发帖,最近市场大量盗我频道延迟图以及收款图并冒充 大家小心提防。如有质疑可找我核对图的收款地址以及图的手机型号。 还有常见问题 老客户需要续费请提前一天 我也会提前一天提醒 只是提醒 不要跟我讲后天 钱包不在家 多少号发工资 服务器是会准时自动停 避免断网断连。 如使用中途 任何问题包售后 独享所谓的独享是指你自己独享一台服务器用独享一条线路 并不是只能一个设备用 并不限制设备 不限制速度 更不限制流量 可以一条用到期 如果万一中途只要你觉得不好用 包售后直到你满意为止。 人工24小时在线 信息基本秒回。 感谢大家的配合以及大力支持🙏 联系:@SHDLIP
❤12👍2👏1🔥1
❤️定制飞机代理 独享❤️ 🤩包月代理🤩11U约(85¥) 🙃包季代理🙃27U约(200¥) 🤪半年代理🤪50U约(360¥) 🥳包年代理🥳90U 约(650¥) 支持 😚支付宝 🥸微信😄USDT 团队高级定制 个人极速定制 不限设备 不限流量 不限速度 可试用满意后付款 包满意 🇱🇷🇲🇦🇬🇮🇨🇽🇬🇱🇯🇪🇨🇨🇧🇭 另出 飞机号 批发 会员代开 ☹️全天在线 联系:@SHDLIP
❤65🔥6🥰3🏆2👍2😁2
免费代理 1千多人在连接使用 避免不了卡顿甚至掉包 请珍惜使用 别拿去下载看片。 定制独享代理联系 @SHDLIP
❤24🔥4🥰4😁4🏆3👍3🎉2
https://t.me/addemoji/SHDLIP
❤9👍2👏2🔥2🥰2😁1
代理续费超多 定制也多 不好用别人也不会续费 需要定制代理的联系 注:服务器已优化更好 汇率和成本问题 为了你们的更好体验 包月微涨 半年 包年下降 老客户续费不变。感谢大家的支持与信任🤝 👍包月代理👍11U约(85¥) 👍包季代理👍27U约(200¥) 👍半年代理👍50U约(360¥) 👍包年代理👍90U 约(650¥) 支持 😚支付宝 🥸微信😄USDT 团队定制 团队定制 个人极速定制 不限设备 不限流量 不限速度 可试用满意后付款 看视频起飞 ------------------------------- 另出 飞机号 批发 会员代开 使用包满意 全天在线 售前售后 定制代理联系:@SHDLIP
❤30❤🔥3👍3🔥3🤩2🥰2🎉1
Showing the 12 most recent of 12 posts we hold for @jiufangyum. 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.
Named by 1 registered channel — 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.
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.
@jiufangyum named 10 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.
References a handle that is not a live channel — we have no record it ever was one.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“飞机代理/TG代理(直连)” (@jiufangyum), 33,144 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/jiufangyum.
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.