用sogo,搜个够✨ 欢迎使用 sogo!🔍 这里可以搜索群组、频道、视频、图片等各类资源,轻松找到你想要的任何内容。你也可以随时分享或添加自己喜欢的资源。 👇点击下方按钮试试吧

Channel
西红柿节点
@xihou5
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
18subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003421799310 |
|---|---|
| Type | Channel |
| Username | @xihou5 |
| Created | 6 December 2025 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/xihou5 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 18:45 | 18 | no change |
| 7 Aug 2026, 18:13 | 18 | first reading |
Engagement
10 posts held, back to 6 December 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 1 page 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 10 posts for this entry, the most recent from 28 December 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 3
- Links
- 5
Lifetime counters from Telegram’s own channel header, read 11 August 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.
Recent posts
西红柿节点 pinned a photo
✨✨ FlyBit机场 ✨✨ 官网:https://goflybit.pages.dev/#/register?code=exQa1Ed0 🎈🎈推广获取50%佣金,满50可提U🎈🎈 🧧 八折优惠码:flybit 🧧 积分兑流量,10积分兑换1G ✈️ IEPL+中转线路,采用SS协议 ✈️ 所有节点解锁流媒体、ChatGPT ✈️ 使用设备数无限制 ✈️ 支持微信、支付宝、USDT支付 ✈️ 节点高可用 ✈️ 已有节点:🇭🇰香港、🇺🇸美国、🇹🇼台湾、🇸🇬新加坡、🇯🇵日本、🇰🇷韩国、🇷🇺俄罗斯、🇦🇺澳大利亚、🇧🇷巴西、🇮🇳印度、🇬🇧英国、🇩🇪德国、🇦🇪阿联酋
https://t.me/ytdlnis
⚔️⚔️⚔️⚔️⚔️⚔️⚔️⚔️ 直达官方:Taishan Taishan机场是个性价比很高的中转机场,23年5月份开业的,目前TG群人数9500+。海外团队运营,全节点解锁流媒体和ChatGPT,有中转和IPLC专线。 😀入门套餐现在是一个季度 ¥22/64GB,年付还能打个折,只要¥68。 💕店长推荐使用¥10/128GB的套餐,年付也只要¥84,相比低档套餐,价格只多了¥24,流量翻倍了,性价比拉满。适合轻度使用或者对价格敏感的人。 🇸🇻还有对应的高流量月付套餐比如月付18/256G和32/512G。 🇸🇻以及没有过期时间限制的纯流量套餐60元/200G和150元/600G。 ☹️🙁🙁☹️🙁🙁🙁😭 😀 • 50+节点,涵盖美国、香港,台湾,日本,新加坡,德国,英国,法国、韩国、越南、澳大利亚、印度、土尔其、俄罗斯等地区。 😀 • 中转线路1倍率,IPLC 5倍率。 😀 • 不限速、不限制同时在线设备数。 😀 …
🇲🇿🇲🇿🇲🇿🇲🇿🇲🇿 🇲🇿🇲🇿🇲🇿🇲🇿🇲🇿 🇲🇿🇲🇿🇲🇿🇲🇿🇲🇿 🎉 Fast-Fish 高速专线 | 限时优惠上新! 🚀 全平台高速 · 稳定专线 · 流媒体全解锁 一次购买,多端畅用,让你的网络真正自由顺滑! ⸻ 🐟 金枪鱼 · 入门稳定之选 💰 ¥12 / 月付 📦 128GB / 月 ⚡ 100 Mbps 👤 5 台设备 ✨ 7×24技术支持 · 流媒体解锁 · GPT不降智 ⸻ 🦈 大白鲨 · 热门高性价比 💰 ¥24 / 月付 📦 256GB / 月 ⚡ 150 Mbps 👥 10 台设备 ✨ 全平台稳定加速 · 专线支持 ⸻ 🐋 龙王鲸 · 顶级旗舰 💰 ¥36 / 月付 📦 384GB / 月 ⚡ 200 Mbps 👥 20 台设备 ✨ 专线高速 · 网页/工单客服 · 全服务解锁 ⸻ 🌐 官方入口 ☝️ http://fast-fish.vip/#/register?code=7…
西红柿节点 pinned «🚀 FQ加速|高端稳定加密机场 🌐 官网:https://fqjiasu.xyz 📢 频道:@fqjiasu 👥 群组:https://t.me/fqjiasu ⸻ 🔒 安全 · 稳定 · 高速 • ✅ 专业加密协议,全程保障数据安全 • ✅ 高质量线路,低延迟不跳线 • ✅ 新手友好,支持主流客户端 ⸻ 💳 支付方式 • 💚 微信支付 • 💙 支付宝 • 🪙 USDT(加密支付更安全) ⸻ 🎁 邀请返利 • 🔥 邀请返利 50%(首次) • 💰 支持提现,真实可拿 ⸻ 🌏…»
🚀 FQ加速|高端稳定加密机场 🌐 官网:https://fqjiasu.xyz 📢 频道:@fqjiasu 👥 群组:https://t.me/fqjiasu ⸻ 🔒 安全 · 稳定 · 高速 • ✅ 专业加密协议,全程保障数据安全 • ✅ 高质量线路,低延迟不跳线 • ✅ 新手友好,支持主流客户端 ⸻ 💳 支付方式 • 💚 微信支付 • 💙 支付宝 • 🪙 USDT(加密支付更安全) ⸻ 🎁 邀请返利 • 🔥 邀请返利 50%(首次) • 💰 支持提现,真实可拿 ⸻ 🌏 全球精品线路(持续维护) • 🇺🇸 美国|GPT 解锁 • 🇹🇼 台湾|全能解锁 • 🇭🇰 香港|Netflix 解锁 • 🇰🇷 韩国|🇰🇷 Netflix 解锁 • 🇯🇵 日本|TikTok 解锁 • 🇸🇬 新加坡|Netflix 解锁 • 🇬🇧 英国|GPT 解锁 无论是 GPT、Netflix、TikT…
Channel photo updated
Channel created
Showing the 10 most recent of 10 posts we hold for @xihou5. 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
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@xihou5 named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 2 posts, 12 August 2026 – 12 August 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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“西红柿节点” (@xihou5), 18 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/xihou5.
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.