Telegram RegisterThe public register of Telegram
Telegram profile photo for 烽火cvv-通道pos

Channel

烽火cvv-通道pos

@fenghuo999

On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry

79subscribers

-3 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002396351012
TypeChannel
Username@fenghuo999
CreatedBetween 1 September 2024 and 20 January 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live3 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/fenghuo999

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 27 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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

798280.57 August 2026 — 82 subscribers9 August 2026 — 82 subscribers16 August 2026 — 81 subscribers24 August 2026 — 80 subscribers3 October 2026 — 79 subscribers7 August 20263 October 2026
5 measurements spanning 56 days, net -3. 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 79–82 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 05:4079-1
24 Aug 2026, 18:4480-1
16 Aug 2026, 07:2481-1
9 Aug 2026, 18:1682no change
7 Aug 2026, 19:3682first reading

Engagement

13 posts held, back to 20 January 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 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 13 posts for this entry, the most recent from 6 October 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤150.0%
👍150.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 2 of the 13 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 20 January 2025 to 6 October 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.

Recent posts

6 Oct 2025, 10:23 UTC438 viewsread 9 August 2026

各位兄弟姊妹中秋节快乐.祝大家中秋之后都日入万u.Happy Mid-Autumn Festival, brothers and sisters. I wish you all a daily income after the Mid-Autumn Festival.

23 Feb 2025, 02:28 UTC≈1,040 viewsread 9 August 2026

https://viettelstore.vn/dien-thoai/iphone-16-pro-max-pid339630.html 可以下单的联系我出地址,嘎嘎丝滑

11 Feb 2025, 04:53 UTC868 viewsread 9 August 2026

https://int.bahn.de/en/booking-information/gutscheine/geschenkgutscheine 可2d/苹果pay/PP,一个链接可以无限打,卡密核销 @XYE6668888

10 Feb 2025, 09:09 UTC720 viewsread 9 August 2026

https://int.bahn.de/en/booking-information/gutscheine/geschenkgutscheine 可2d/苹果pay/PP,一个链接可以无限打,卡密核销 @XYE6668888

21 Jan 2025, 08:03 UTC686 viewsread 9 August 2026

UK ZETTLE超级四标户开工中,英国,智利好进,只要打的猛的,不是链接,需要有外设 @XYE6668888

20 Jan 2025, 22:23 UTC687 viewsread 9 August 2026

西班牙赌场机,来欧洲各国料,南美料 @XYE6668888

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

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

“烽火cvv-通道pos” (@fenghuo999), 79 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/fenghuo999.

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.