英文 @xircusnews 🇨🇳 China @xircusOfficialChina

Channel
Xircus NFT // 🇨🇳 China频道
@VaniaUnited
On this record: Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
7subscribers
+3 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 | -1001643797998 |
|---|---|
| Type | Channel |
| Username | @VaniaUnited |
| Created | 27 October 2021 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/VaniaUnited |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 06:28 | 7 | +3 |
| 13 Aug 2026, 07:33 | 4 | no change |
| 7 Aug 2026, 01:37 | 4 | first reading |
Engagement
10 posts held, back to 27 October 2021 — 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 pageof 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 27 October 2021. An engagement rate over an empty window would be a number about nothing.
Recent posts
英文 @xircusnews 🇨🇳 China @xircusOfficialChina
英文 @xircusnews 🇨🇳 China @xircusOfficialChina
https://t.me/VaniaUnited
英文 @xircusnews 🇨🇳 China @xircusOfficialChina
英文 @xircusnews 🇨🇳 China @xircusOfficialChina
英文 @xircusnews 🇨🇳 China @xircusOfficialChina
红杉资本助力🌟Xircus NFT✨ 世界上第一个多链NFT自定义平台,打造NFT界的阿里巴巴 🚀红杉主动联系项目方,与项目方已初步达成合作 💎团队硬核 ,2017年创立locktrip,目前市值超1亿美金 💎 开发近一年,已落地项目 ,跨7大公链 🚀AXS,Shiba,mana等正在xircus平台部署自己的NFT商店 🔥受邀出席世界上最具影响力的迪拜世界区块链峰会 🚀发行总量一亿枚,无交易税,持币双挖,也可以参与铸造 🚀10月28号将在BSC链公开发售 …
Channel photo updated
Channel created
Showing the 10 most recent of 10 posts we hold for @VaniaUnited. 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.
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
@VaniaUnited 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 7 posts, 14 August 2026 – 14 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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Xircus NFT // 🇨🇳 China频道” (@VaniaUnited), 7 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/VaniaUnited.
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.