Telegram RegisterThe public register of Telegram
Telegram profile photo for 皇小松日本cvv收货最新频道

Channel

皇小松日本cvv收货最新频道

@qqhxs888

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

389subscribers

+35 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-1003579647228
TypeChannel
Username@qqhxs888
CreatedBetween 1 December 2025 and 11 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live2 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/qqhxs888

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 62% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

3353893628 August 2026 — 354 subscribers8 August 2026 — 354 subscribers16 August 2026 — 347 subscribers23 August 2026 — 335 subscribers29 August 2026 — 339 subscribers6 September 2026 — 337 subscribers13 September 2026 — 361 subscribers2 October 2026 — 389 subscribers8 August 20262 October 2026
8 measurements spanning 55 days, net +35. 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 327–397 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 15:20389+28
13 Sept 2026, 07:59361+24
6 Sept 2026, 05:15337-2
29 Aug 2026, 14:44339+4
23 Aug 2026, 15:34335-12
16 Aug 2026, 20:03347-7
8 Aug 2026, 06:46354no change
8 Aug 2026, 06:30354first reading

Engagement

15 posts held, back to 11 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 15 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

28 reactions across 5 posts, in 6 distinct kinds. The most used accounts for 25.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍725.0%
🔥725.0%
👎517.9%
❤414.3%
💩414.3%
👏13.57%

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 6 of the 15 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 28 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 11 March 2026 to 2 August 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

2 Aug 2026, 04:42 UTC195 viewsread 8 August 2026

老客人有需要帮忙带回国的可以联系 有小弟回国 @qqhxs188888

25 Jul 2026, 03:51 UTC479 views5 reactionsread 8 August 2026
Photo

这个是谁下单的包裹速来认领,税要26000 确定一下 米有人找我直接拒收了 单号:2766-6050-9650

🔥4❤1

23 Jul 2026, 06:57 UTC433 viewsread 8 August 2026

大量收苹果 有的来 苹果店取 营业所 大量安排 人手充足 @qqhxs188888

13 Jul 2026, 08:31 UTC579 viewsread 8 August 2026
Photo

生成地址 还是有人纠结 看图片 然后现编一个就ok了啊 谷歌搜索 有真实地址就没有问题了啊 发黑猫 左川 邮局 姓名尽量男生 全可以营业所 跟 拦截 适用于任何吃地址的通道 明白了吗 各位董事长们 千万不要1-1-1-1这样写啊 一眼假啊 正常点

7 Jul 2026, 08:28 UTC619 views0 reactionsread 8 August 2026
Photo

在日本有要的吗免费赠送家具到付运费给你即可12w日元的

5 Jul 2026, 18:57 UTCviews —

The owner of this channel has been inactive for the last 1 month. If they remain inactive for the next 9 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.

4 Jul 2026, 15:09 UTC791 viewsread 8 August 2026

perplexity AI 或者 克劳德 能充的 滴滴我一下 @Minami_999

1 Jul 2026, 09:50 UTC600 views1 reactionsread 8 August 2026
Photo

苹果还在纠结不动产? 就这样给AI 生成就行了然后 去谷歌里面搜索一下 番地 〒100-0002 東京都千代田区皇居外苑1丁目 -18-3 就这样就ok 后面2个随便编 但是不要 -1-1 这种太假了哈 就这样 纯最干净的地址 还不明白 来问我

❤1

26 Jun 2026, 05:10 UTC656 viewsread 8 August 2026

本人飞机号:@qqhxs188888 是5个8 6干8的是个畜生,你们小心点不要挨骗了

20 Jun 2026, 01:27 UTC793 viewsread 8 August 2026

请求一个高价值咖啡机,自用 能出的私聊我 @qqhxs188888

17 Jun 2026, 06:15 UTC822 views1 reactionsread 8 August 2026

最近下苹果的客人有点说,我重点讲一下会地址不明的情况误区,第一点,全角提交的数字在苹果系统可能会变成没有丁目最后地址不明,需要正常的数字输入半角即可,有正确丁目的,后面只有一个房间号的地址也会地址不明需要补充建筑物大楼。 没有建筑大楼的地址 你先不要下,过来问我建筑大楼名补充,不然每天都在给你们打电话 整这种地址不明的事太多 用库料的,需要生成地址的直接让我帮你生成地址,以免出现地址错误 从其他国家下的苹果,日本名字需要完整的不可以只是名,或者只是姓,这样申报有不会通过

👍1

Showing the 12 most recent of 15 posts we hold for @qqhxs888. 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 2 October 2026 — this entry's latest reading, not the date you are reading this.

“皇小松日本cvv收货最新频道” (@qqhxs888), 389 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/qqhxs888.

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.