Telegram RegisterThe public register of Telegram
Telegram profile photo for 全球服务器 🌍 @cdncloud_yibing

Channel

全球服务器 🌍 @cdncloud_yibing

@quanqiufuwuqi_yibing

On this record: Growth · Engagement · Posts · Citations · Cite this entry

2subscribers

-1 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002820263126
TypeChannel
Username@quanqiufuwuqi_yibing
Created28 July 2025 — measured — dated from the channel’s first post
First recorded13 August 2026
Last confirmed live19 September 2026
Measurements held3
Confirmed unchanged2 times, most recently 19 September 2026
On Telegramt.me/quanqiufuwuqi_yibing

Growth

232.58 August 2026 — 3 subscribers13 August 2026 — 3 subscribers10 September 2026 — 2 subscribers8 August 202610 September 2026
3 measurements spanning 33 days, net -1. 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 2–3 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 18:222-1
13 Aug 2026, 13:313no change
8 Aug 2026, 21:323first reading

Engagement

9 posts held, back to 28 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 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 9 posts for this entry, the most recent from 30 July 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Jul 2025, 02:36 UTC48 viewsread 13 August 2026

🇨🇳 国内服务器 🤔 扬州BGP 🤔 厦门电信 🤔 厦门电信大带宽 🤔 厦门BGP 🤔 宁波BGP 🤔 济南互通普通区 🤔 十堰电信 🤔 德阳 🤔 山东电信/BGP 🤔 武汉电信 🤔 成都电信 🤔 杭州BGP 🤔 宿迁BGP 🤔 镇江BGP 🤔 东莞BGP 🤔 深圳物理机 🤔 国内显卡

28 Jul 2025, 09:09 UTC69 viewsread 13 August 2026

📍 大洋洲服务器 🔘 澳大利亚VPS 🔘 澳大利亚物理机 🔘 新西兰VPS 🔘 新西兰物理机

28 Jul 2025, 09:09 UTC67 viewsread 13 August 2026

📍 南美洲服务器 🔘 巴西VPS 🔘 巴西物理机 🔘 阿根廷VPS 🔘 阿根廷物理机 🔘 哥伦比亚VPS 🔘 哥伦比亚物理机 🔘 秘鲁VPS 🔘 秘鲁物理机 🔘 智利VPS 🔘 智利物理机 🔘 委内瑞拉VPS 🔘 厄瓜多尔VPS 🔘 玻利维亚VPS 🔘 乌拉圭VPS 🔘 巴拉圭VPS

28 Jul 2025, 09:08 UTC53 viewsread 13 August 2026

📍 北美洲服务器 🤔 美国VPS 🤔 美国物理机 🤔 加拿大VPS 🤔 加拿大物理机 🤔 墨西哥VPS 🤔 墨西哥物理机 🤔 危地马拉VPS 🤔 巴拿马VPS

28 Jul 2025, 09:08 UTC45 viewsread 13 August 2026

📍 非洲服务器 🤔 南非VPS 🤔 南非物理机 🤔 埃及VPS 🤔 埃及物理机 🤔 加纳VPS 🤔 加纳物理机 🤔 肯尼亚VPS 🤔 肯尼亚物理机 🤔 尼日利亚VPS 🤔 尼日利亚物理机 🤔 阿尔及利亚VPS 🤔 摩洛哥VPS

28 Jul 2025, 09:08 UTC52 viewsread 13 August 2026

📍 欧洲服务器 🤔 俄罗斯VPS 🤔 俄罗斯物理机 🤔 德国VPS 🤔 德国物理机 🤔 英国VPS 🤔 英国物理机 🤔 法国VPS 🤔 法国物理机 🤔 荷兰VPS 🤔 荷兰物理机 🤔 保加利亚VPS 🤔 保加利亚物理机 🤔 希腊VPS 🤔 希腊物理机 🤔 意大利VPS 🤔 意大利物理机 🤔 波兰VPS 🤔 波兰物理机 🤔 西班牙VPS 🤔 西班牙物理机 🤔 匈牙利VPS 🤔 匈牙利物理机 🤔 冰岛VPS 🤔 冰岛物理机 🤔 乌克兰VPS 🤔 乌克兰物理机 🤔 瑞士VPS 🤔 瑞士物理机 🤔 瑞典V…

28 Jul 2025, 09:07 UTC51 viewsread 13 August 2026

📍 亚洲服务器 🤔 印度VPS 🤔 印度物理机 🤔 越南VPS 🤔 越南物理机 🤔 泰国VPS 🤔 泰国物理机 🤔 新加坡VPS 🤔 新加坡物理机 🤔 菲律宾VPS 🤔 菲律宾物理机 🤔 阿联酋VPS 🤔 阿联酋物理机 🤔 马来西亚VPS 🤔 马来西亚物理机 🤔 印度尼西亚VPS 🤔 印度尼西亚物理机 🤔 柬埔寨VPS 🤔 柬埔寨物理机 🤔 土耳其VPS 🤔 土耳其物理机 🤔 孟加拉国VPS 🤔 孟加拉国物理机 🤔 沙特阿拉伯VPS 🤔 沙特阿拉伯物理机 🤔 巴基斯坦VPS 🤔 巴基斯坦物理机 🤔 哈萨克斯坦VPS 🤔 哈萨克斯坦物理机 🤔 蒙古VPS 🤔 科威特VPS …

Showing the 9 most recent of 9 posts we hold for @quanqiufuwuqi_yibing. 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 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.

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

“全球服务器 🌍 @cdncloud_yibing” (@quanqiufuwuqi_yibing), 2 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/quanqiufuwuqi_yibing.

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.