Telegram RegisterThe public register of Telegram
Telegram profile photo for 求职 @qiuzhi

Channel

求职 @qiuzhi

@huazhuhui7

2 usernames

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

6,038subscribers

-91 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001822637715
TypeChannel
Usernames@huazhuhui7 @qiuzhi
Created12 December 2022measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live16 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/huazhuhui7

Growth

6,0386,1296,083.57 August 2026 — 6,129 subscribers7 August 2026 — 6,129 subscribers7 August 2026 — 6,123 subscribers10 August 2026 — 6,105 subscribers10 August 2026 — 6,102 subscribers12 August 2026 — 6,072 subscribers13 August 2026 — 6,070 subscribers16 August 2026 — 6,044 subscribers16 August 2026 — 6,038 subscribers7 August 202616 August 2026
9 measurements spanning 10 days, net -91. 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 6,024–6,143 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 22:156,038-6
16 Aug 2026, 08:486,044-26
13 Aug 2026, 06:496,070-2
12 Aug 2026, 17:536,072-30
10 Aug 2026, 13:356,102-3
10 Aug 2026, 03:516,105-18
7 Aug 2026, 19:446,123-6
7 Aug 2026, 03:346,129no change
7 Aug 2026, 02:466,129first reading

Engagement

5 posts held, back to 12 December 2022the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 10 pagesof 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 5 posts for this entry, the most recent from 2 January 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
20s
Average length
10s

Measured directly from 2 videos 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.

Reaction mix

19,924 reactions across 2 posts, in 9 distinct kinds. The most used accounts for 49.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
💩9,94049.9%
🤮9,82049.3%
👍800.402%
630.316%
👎120.06%
🌚30.015%
😁30.015%
🥰20.01%
🔥10.005%

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 2 of the 5 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 19,924reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 5 most recent posts we hold, published 12 December 2022 to 2 January 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.

Recent posts

8 Jan 2023, 19:20 UTC≈49,900 views9,988 reactionsread 12 August 2026
Video

😁🤪🤨😫 广告投放详情请点击下方链接跳转看介绍👇🏻👇🏻👇🏻 TG的全局搜索只有四个字中文才能搜索 华助会2023年全面升级为华人在外 记住拼音 @huaren✅️ 华人在外,没有意外 ⚡️. 【华人在外】109个万人聊天大群广告推送,不限内容字数。 👉🏻1800 USDT一个月 💡2小时推送一次109个群,一天12次 极具性价比 强烈推荐⭐️⭐️⭐️⭐️⭐️ 广告价格不接受任何议价,可以去了解下,现在还有谁有这么多群,并进行持续引流。 ⚡️.【华人在外】109个聊天大群+5000+个视频色群+【国人在外】101个聊天大群 2小时一次推送广告。超级无敌效果最强性价比 不限广告内容 3700 USDT/月 最强推送,效果爆棚! ⭐️⭐️⭐️⭐️⭐️ ⚡️.【国人在外】101个聊天大群推送 1200U/月。100个聊天大群12小时置顶 2300U/月⭐️⭐️⭐️⭐️⭐️ 有位置 ⚡️. 【华人在外】108个聊天大

💩4,970🤮4,90050👍48👎12🌚3😁3🥰2

8 Jan 2023, 15:06 UTC≈28,600 views9,936 reactionsread 12 August 2026
Video

【華助會】旗下品牌 因为TG全局搜索,三个字的中文无法搜索。 2023年起华助会全面升级成新的品牌名 【华人在外】 记住华人拼音 @huaren✅️ ,就能轻松找到我们。 华人在外,没有意外! 华人在外斥资百万 拿下顶级NFT 引流,安全,爆料,炒币,合约,6D, 6Y,8Y,8D,9D. 电视,链游,搞笑,广告,汉化,汉语,华人,国人,接码,开车,嫖妓,群发,搜索,中文,吃瓜,招人,招聘,做爱,国安,币coin,韭菜,代发,百科,求职,打工,韭菜,色群,QQ群,黄金,担保哥,狠人,人群,总书记,劳务派遣,甩人,中华,对不起,大鸡巴,守护,好群 给广告合作伙伴提供强大的流量支持和无敌曝光 我们每月还会投入10几万引流进我们的开车小群 每月新增500群以上,30万人次以上的新增用户. 不计成本的投入是我们的承诺和保障。 为每个合作伙伴创造价值,合作共赢。 😀 >>> 点这里切换【简体中文】<<< 😀 😀 华人在外中文

💩4,970🤮4,920👍3213🔥1

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

Citation-graph rank

Citation-graph rank — 554,174 of 1,481,243entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

Named by 7 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.

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

“求职 @qiuzhi” (@huazhuhui7), 6,038 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/huazhuhui7.

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.