Telegram RegisterThe public register of Telegram
Telegram profile photo for 港卡批发频道

Channel

港卡批发频道

@xddvvv

2 usernames

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

887subscribers

+579 since we began measuring on 19 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002021358439
TypeChannel
Usernames@gkpindao @xddvvv
Created19 January 2024 — measured — dated from the channel’s first post
First recorded19 August 2026
Last confirmed live28 September 2026
Measurements held9
Confirmed unchanged1 time, most recently 28 September 2026
On Telegramt.me/xddvvv

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 52% 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

308887597.519 August 2026 — 308 subscribers19 August 2026 — 308 subscribers26 August 2026 — 316 subscribers3 September 2026 — 338 subscribers10 September 2026 — 368 subscribers10 September 2026 — 368 subscribers12 September 2026 — 377 subscribers12 September 2026 — 376 subscribers28 September 2026 — 887 subscribers19 August 202628 September 2026
9 measurements spanning 39 days, net +579. 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 221–974 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Sept 2026, 05:37887+511
12 Sept 2026, 09:18376-1
12 Sept 2026, 00:21377+9
10 Sept 2026, 14:22368no change
10 Sept 2026, 13:47368+30
3 Sept 2026, 01:33338+22
26 Aug 2026, 03:52316+8
19 Aug 2026, 18:45308no change
19 Aug 2026, 18:30308first reading

Engagement

25 posts held, back to 19 January 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
22.3%
avg views ÷ 887 subscribers
Avg views / post
198
4 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
4
of 25 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 September 2026
Posts held25 (19 January 2024 – 10 September 2026)
Views total792
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Sept 2026, 14:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

12 reactions across 6 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤866.7%
😁433.3%

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

Measured over the 25 most recent posts we hold, published 19 January 2024 to 10 September 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

10 Sept 2026, 05:54 UTC72 viewsread 10 September 2026

香港,印尼,澳大利亚,英国,美国 需要接项目得来,量大管够

9 Sept 2026, 03:58 UTC134 viewsread 10 September 2026

香港实名企业微信红标主体 美国实名企业微信红标主体 港卡企微 红标 不实名 美卡企微 红标 不实名 批发各种港卡首次业务,有量有价 网站自助下单https://qiyewx.top/shop/ 发卡机器人 @qiyevxjiqi_bot

1 Sept 2026, 05:01 UTC409 viewsread 10 September 2026

香港实名企业微信子号 香港实名企业微信红标主体 美国实名企业微信红标主体 港卡企微 红标 不实名 批发各种港卡首次业务,有量有价 网站自助下单https://qiyewx.top/shop/ 发卡机器人 @qiyevxjiqi_bot

30 Aug 2026, 15:37 UTCviews —

港卡批发频道 pinned «项目名称:一手批发 港卡美卡企业微信 首次 供应内容: 港卡 企业V实名红标 少量有货 港卡企微 红标 不实名 网站自助下单https://qiyewx.top/shop/ 发卡机器人 @qiyevxjiqi_bot 批发各种港卡首次业务,有量有价 商家网站: https://yoyokaw.top/shop/atong 可网站自助下单 售后和咨询 @yoyoka1»

30 Aug 2026, 15:36 UTC442 viewsread 10 September 2026

项目名称:一手批发 港卡美卡企业微信 首次 供应内容: 港卡 企业V实名红标 少量有货 港卡企微 红标 不实名 网站自助下单https://qiyewx.top/shop/ 发卡机器人 @qiyevxjiqi_bot 批发各种港卡首次业务,有量有价 商家网站: https://yoyokaw.top/shop/atong 可网站自助下单 售后和咨询 @yoyoka1

30 Aug 2026, 15:01 UTC345 viewsread 10 September 2026

满48小时港淘-活淘活支 满年美支-双密-绑淘代付(app直登) 三无邮箱支付宝-限制-带账单 三无直登支付宝邮箱号 有i需要的滴滴

30 Aug 2026, 10:24 UTC318 viewsread 10 September 2026

香港企业V实名红标少量有货 需要的老板滴滴

22 Aug 2026, 08:48 UTC530 viewsread 10 September 2026

一手批发 港卡美卡企业微信 首次 港卡小红书首次 上新 港卡企微客服号 红标 不实名 批发各种港卡首次业务,有量有价 商家网站: https://yoyokaw.top/shop/atong 可网站自助下单 售后 @yoyokawang

13 Aug 2026, 14:46 UTC691 viewsread 10 September 2026

云机转移 港卡实名红标 有货 直登号 港卡实名红标 有货

5 Aug 2026, 15:14 UTC905 views0 reactionsread 10 September 2026

更换了店铺链接,注意注意 商家网站: https://yoyokaw.top/shop/atong 可网站自助下单

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

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.

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

“港卡批发频道” (@xddvvv), 887 subscribers as measured 28 September 2026. Telegram Register, tgregister.com/channel/xddvvv.

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.