Telegram RegisterThe public register of Telegram
Telegram profile photo for Phoenix Calls

Channel

Phoenix Calls

@phoenix_sol_call

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

45subscribers

-1 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-1002106034736
TypeChannel
Username@phoenix_sol_call
DescriptionBorn in ashes. Forged by fire. I don’t rise. I return.
CreatedBetween 1 November 2023 and 29 January 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live27 August 2026
Measurements held3
On Telegramt.me/phoenix_sol_call

Previous handles

@phoenix_sol_call 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.

@phoenix_sol_call
held 10 August 202610 August 2026

Growth

454645.57 August 2026 — 46 subscribers8 August 2026 — 45 subscribers10 August 2026 — 45 subscribers7 August 202610 August 2026
3 measurements spanning 3 days, net -1. 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 45–46 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 15:0145no change
8 Aug 2026, 02:1845-1
7 Aug 2026, 11:5246first reading

Engagement

20 posts held, back to 29 January 2024the 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 29 February 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
14
Links
30

Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

6 reactions across 3 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
466.7%
🔥233.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 4 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 6 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 29 January 2024 to 29 February 2024, 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

29 Feb 2024, 15:00 UTC120 viewsread 10 August 2026
Photo

Update https://t.me/phoenix_sol_call/57 CAP NOW: 42kk 3x plus from called Good work @phoenix_sol_call

29 Feb 2024, 14:48 UTC98 viewsread 10 August 2026

TOKEN NAME: MSFT CONTRACT: 66y3tTwi2UkSb2H6frcqyTGzD6YtEXdz3avQjWBo3e1 CAP NOW: 12k ------------------- CHART: https://dexscreener.com/solana/ci8c3qkcnqcsc3vmfnktfw7cnznhvr9vzmt97j4vroxq ------------------ Social TG: https://t.me/MSFTBinbows97

22 Feb 2024, 15:49 UTC141 viewsread 10 August 2026
Photo

Update https://t.me/phoenix_sol_call/54 CAP NOW: 24k. ATH: 31k 2x plus from called Good work @phoenix_sol_call

22 Feb 2024, 15:14 UTC76 viewsread 10 August 2026

(SOL) TOKEN NAME: $CLIPPY CONTRACT: 6wpbagPpxGUcjd1dZwzpCiJGNoHsqDL9UwzQqzyHMyzt CAP NOW: 12k ------------------- CHART: https://dexscreener.com/solana/aakgjaqlb4dmf3nrnqsqygsfctrywzeqchcd1shxb68r ------------------ Social TG: https://t.me/ClippyOGAI

22 Feb 2024, 14:53 UTC64 viewsread 10 August 2026
Photo

Update Wii https://t.me/phoenix_sol_call/52 CAP NOW: 27k 2x plus from called Good work @phoenix_sol_call

22 Feb 2024, 14:42 UTC65 viewsread 10 August 2026

(SOL) TOKEN NAME: Wii CONTRACT: 6bhms9VXon51N4ZCxRAE6v2WQW9gTUzYefzQ8AEyZP48 CAP NOW: 10k ------------------- CHART: https://dexscreener.com/solana/cgafqwvtvthse2rguam1sdmk3m77r5yfhjfyirpexbhe ------------------ Social TG: https://t.me/nintendowiisol

16 Feb 2024, 13:11 UTC69 views1 reactionsread 10 August 2026

(SOL) TOKEN NAME: MAGA CONTRACT: 8JzwvpDxRKMPNypTRMKSi5wMNhoDDki6AGNDEE3DFPtL CAP NOW: 14k ------------------- CHART: https://dexscreener.com/solana/a5hgiqrixanda94sdweccdj4yximstisuis5rvgzyxnw ------------------ Social TG: https://t.me/Trumptroll_Sol

1

4 Feb 2024, 15:43 UTC82 viewsread 10 August 2026

(SOL) TOKEN NAME: BabyPork CONTRACT: AhxXdzfhGJqZjndy2N5zmw8Phay2cj2aDdVy6xPAeaeM CAP NOW: 10k ------------------- CHART: https://dexscreener.com/solana/2vjcwjmz2aaqzvpvzlhtnkqxwyyue5rmfpetcjwleght ------------------ Social TG: https://t.me/BabyPorkSol

4 Feb 2024, 07:14 UTC148 viewsread 10 August 2026
Photo

Update $VISION https://t.me/phoenix_sol_call/44 CAP NOW: 800k, ATH: 1M 40x plus from called Good work @phoenix_sol_call

2 Feb 2024, 17:20 UTC135 views3 reactionsread 10 August 2026
Photo

Update $VISION https://t.me/phoenix_sol_call/44 CAP NOW: 230k 10x plus from called Good work @phoenix_sol_call

3

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

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

“Phoenix Calls” (@phoenix_sol_call), 45 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/phoenix_sol_call.

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.