Telegram RegisterThe public register of Telegram
Telegram profile photo for Phoenix fx (free)

Channel

Phoenix fx (free)

@phoenixfxfree1

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

670subscribers

-39 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-1003873355084
TypeChannel
Username@phoenixfxfree1
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/phoenixfxfree1

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

Previous handles

@phoenixfxfree1 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@goldhunters1x
held 8 August 20268 August 2026

Growth

6707106907 August 2026 — 709 subscribers8 August 2026 — 709 subscribers11 August 2026 — 707 subscribers11 August 2026 — 707 subscribers11 August 2026 — 710 subscribers18 August 2026 — 700 subscribers25 August 2026 — 697 subscribers1 September 2026 — 693 subscribers10 September 2026 — 684 subscribers18 September 2026 — 670 subscribers7 August 202618 September 2026
10 measurements spanning 42 days, net -39. 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 664–716 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 20:56670-14
10 Sept 2026, 20:19684-9
1 Sept 2026, 01:43693-4
25 Aug 2026, 08:17697-3
18 Aug 2026, 06:12700-10
11 Aug 2026, 21:12710+3
11 Aug 2026, 18:00707no change
11 Aug 2026, 17:47707-2
8 Aug 2026, 02:17709no change
7 Aug 2026, 19:25709first reading

Engagement

34 posts held, back to 4 August 2026the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 34 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

103 reactions across 30 posts, in 5 distinct kinds. The most used accounts for 71.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7471.8%
❤‍🔥1514.6%
🔥54.85%
🙏54.85%
🎉43.88%

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

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

11 Aug 2026, 17:23 UTC91 views3 reactionsread 11 August 2026

We have some crazy things coming HENCE WHY WE CHANGED THE NAME 🥷 Hold tight its take over szn

3

11 Aug 2026, 15:33 UTC120 views3 reactionsread 11 August 2026
Photo

Good night Today is complete 💸💸 We go again tomorrow new day new beginnings @gh_support1

3

11 Aug 2026, 09:45 UTC142 views1 reactionsread 11 August 2026

Results from yesterday and last nights asian session across V1 & V2 @gh_support for autos

1

10 Aug 2026, 20:36 UTC163 views2 reactionsread 11 August 2026
Photo

Dxy is pumping gold should be dropping it looks like its lagging

2

10 Aug 2026, 20:36 UTC156 views4 reactionsread 11 August 2026

Entering again 4392 moving both SL to 4402 Sending chart now

3🎉1

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

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

“Phoenix fx (free)” (@phoenixfxfree1), 670 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/phoenixfxfree1.

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.