Channel
@huozhangbot
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
2subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003850171747 |
|---|---|
| Type | Channel |
| Usernames | @huozhang @huozhangbot |
| Description | 干将70 @vip1064 |
| Created | 1 March 2026 — measured — dated from the channel’s first post |
| First recorded | 13 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/huozhangbot |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 19:37 | 2 | no change |
| 13 Aug 2026, 16:48 | 2 | first reading |
6 posts held, back to 1 March 2026 — 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 6 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 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.
😢NFT @huozhen 货真 活真 😢NFT @huoyo 火哟🔥 😢NFT @huosen 霍森 火森 @huochen 火沉🔥 😢NFT @huozhang 火掌 😢NFT @huonuan 火暖🔥 😢NFT @nuanhuo 暖火🔥 暖和 😢NFT @huoteng 火熥🔥 😢NFT @shunhuo 顺火🔥 😢NFT @penhuo 喷火 😢NFT @benhuo 奔火 😢NFT @banghuo 邦火 😢NFT @RanHuo 燃火 😢NFT @mianhuo 绵火🔥 😢NFT @lvhuo 绿火🔥 😢NFT @shuanghuo 霜火 爽活🔥
😢NFT @huozhang 火掌
https://fragment.com/username/@huozhang 😢NFT @huozhang 火掌
NFT 官网一口价，喜欢的直接拍。🧧 更多nft用户名 @tg8tg 🇸🇰 NFT列表: 1- 2- 3- 4- 5- 6- 7- 8- 9- 10- 11- 12- 13- 14- 15- 16- 17- 18- 19- 20- usdt 购买联系 @ganjiang 干将 @NFT899 已上链用户名1000个。 😢NFT @zouyan 走烟(走私烟) @tg8tg @tgtg8 @tgtgQ @o66666 @j66666 @p66666
用户名nft出售列表(18) 😢NFT @quanshun 全顺 泉瞬 😢NFT @biaoshun 标顺 😢NFT @shunkuan 顺款 😢NFT @kuanshun 款顺 😢NFT @shunshang 顺商 😢NFT @shunhuo 顺火🔥 😢NFT @shungang 顺杠 😢NFT @shunxiao 顺销 😢NFT @shunsai 顺塞 @shunkao 顺考 @shunzhao 顺招 @shunzhuo 顺卓 @shunlang 顺狼 😢NFT @shunqiang 顺强 😢NFT @shunxiang 顺祥 @shunmian 顺面 @shunruan 顺软 @raoshun 绕顺 @guanshun 冠顺 @duishun 兑顺 @cuoshun 搓顺 @tuoshun …
Channel created
Showing the 6 most recent of 6 posts we hold for @huozhangbot. 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 20 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“火掌” (@huozhangbot), 2 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/huozhangbot.
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.