Channel

𝐕𝟐𝐏𝐡𝐨𝐞𝐧𝐢𝐱

@V2_Phoenix

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

546subscribers

+211 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	-1004360104157
Type	Channel
Username	@V2_Phoenix
Created	Between 1 June 2026 and 24 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	8 August 2026
Last confirmed live	10 October 2026
Measurements held	10
Confirmed unchanged	1 time, most recently 10 October 2026
On Telegram	t.me/V2_Phoenix

Topic

Other / unclassifiable — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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

10 measurements spanning 64 days, net +211. 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 303–578 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
10 Oct 2026, 20:40	546	+23
29 Sept 2026, 16:01	523	+41
14 Sept 2026, 20:39	482	+26
7 Sept 2026, 19:21	456	+26
29 Aug 2026, 00:17	430	+19
23 Aug 2026, 01:03	411	+42
15 Aug 2026, 18:27	369	+33
8 Aug 2026, 07:04	336	no change
8 Aug 2026, 00:16	336	+1
7 Aug 2026, 16:16	335	first reading

Engagement

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

Reaction mix

5 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 60.0% of them.

Every reaction kind recorded on the sample, most used first
Reaction	Count	Share
❤	3	60.0%
👍	1	20.0%
👏	1	20.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 5 of the 20 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 5 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 24 July 2026 to 7 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

7 Aug 2026, 11:14 UTC≈2,110 views1 reactionsread 8 August 2026

❤1

7 Aug 2026, 07:14 UTC≈1,750 viewsread 8 August 2026

6 Aug 2026, 09:39 UTC≈2,760 viewsread 8 August 2026

5 Aug 2026, 10:05 UTC≈4,560 viewsread 8 August 2026

4 Aug 2026, 18:02 UTC≈2,550 viewsread 8 August 2026

3 Aug 2026, 15:59 UTC≈2,560 viewsread 8 August 2026

2 Aug 2026, 17:27 UTC≈2,990 viewsread 8 August 2026

1 Aug 2026, 17:53 UTC≈1,830 views1 reactionsread 8 August 2026

❤1

31 Jul 2026, 14:46 UTC≈2,470 viewsread 8 August 2026

30 Jul 2026, 08:41 UTC≈1,780 viewsread 8 August 2026

30 Jul 2026, 08:38 UTC≈1,630 viewsread 8 August 2026

28 Jul 2026, 17:52 UTC≈3,500 views1 reactionsread 8 August 2026

👏1

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

𝐕𝟐𝐩𝐡𝐨𝐞𝐧𝐢𝐱
@v2ray_phoenix · 16,241217 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 10 October 2026 — this entry's latest reading, not the date you are reading this.

“𝐕𝟐𝐏𝐡𝐨𝐞𝐧𝐢𝐱” (@V2_Phoenix), 546 subscribers as measured 10 October 2026. Telegram Register, tgregister.com/channel/V2_Phoenix.

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.