Channel
@qunz00294
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
168subscribers
-1 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003487109476 |
|---|---|
| Type | Channel |
| Username | @qunz00294 |
| Created | 6 December 2025 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/qunz00294 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 17:25 | 168 | -1 |
| 14 Aug 2026, 03:49 | 169 | first reading |
4 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 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 4 posts for this entry, the most recent from 6 December 2025. An engagement rate over an empty window would be a number about nothing.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 2 | 100.0% |
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 1 of the 4 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 6 December 2025 to 6 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
电报账号购买·一手号源群 pinned «🚀 专业社交软件账号服务 🌍 我们提供各种国外社交软件账号，满足你的多样需求，包括： 💬 Telegram 账号 实名号 888永久号 （直登号，协议号，TG老群组，老频道，TG拉群，TG数据筛选） 📘 Facebook 账号 （FB白号，FB老号，广告户，点赞，加关注，浏览量，FB数据筛选） 🌐 WhatsApp 账号 ws蓝标号 （直登号，协议号，WS拉群，WS数据筛选） 🔗 VKontakte 账号 （vk新号，vk老号+好友，vk数据筛选） 🌐 LinkedIn 账号 （领英新号，老号，领英数据筛选）…»
🚀 专业社交软件账号服务 🌍 我们提供各种国外社交软件账号，满足你的多样需求，包括： 💬 Telegram 账号 实名号 888永久号 （直登号，协议号，TG老群组，老频道，TG拉群，TG数据筛选） 📘 Facebook 账号 （FB白号，FB老号，广告户，点赞，加关注，浏览量，FB数据筛选） 🌐 WhatsApp 账号 ws蓝标号 （直登号，协议号，WS拉群，WS数据筛选） 🔗 VKontakte 账号 （vk新号，vk老号+好友，vk数据筛选） 🌐 LinkedIn 账号 （领英新号，老号，领英数据筛选） 📸 Instagram 账号 （ins新号，老号，ins数据筛选） 🔥 Tinder 账号 （火种新号，火种老号，定制号） 🐦 Twitter 账号 （推特白号，推特老号，+好友，上粉，蓝v） 📧 Google 邮箱 GV号 （谷歌邮箱，谷歌语音账号，其他邮箱） 🍏 苹果 ID （Apple I…
❤2
Channel photo updated
Channel created
Showing the 4 most recent of 4 posts we hold for @qunz00294. 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 — 1,443,425 of 1,481,217entries 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.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“电报账号购买·一手号源群” (@qunz00294), 168 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/qunz00294.
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.