Telegram RegisterThe public register of Telegram
Telegram profile photo for Phanes Trending

Channel

Phanes Trending

@PhanesTrending

Not marked by Telegram, checked 4 September 2026

On this record: Growth · Engagement · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

6,055subscribers

-58 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002244051860
TypeChannel
Username@PhanesTrending
Created20 June 2024measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live7 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/PhanesTrending

Growth

6,0486,1146,0817 August 2026 — 6,113 subscribers7 August 2026 — 6,113 subscribers7 August 2026 — 6,114 subscribers10 August 2026 — 6,105 subscribers14 August 2026 — 6,103 subscribers17 August 2026 — 6,085 subscribers20 August 2026 — 6,077 subscribers24 August 2026 — 6,066 subscribers27 August 2026 — 6,061 subscribers30 August 2026 — 6,060 subscribers2 September 2026 — 6,048 subscribers7 September 2026 — 6,055 subscribers6,0557 August 20267 September 2026
12 measurements spanning 31 days, net -58. 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 6,038–6,124 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 01:206,055+7
2 Sept 2026, 10:276,048-12
30 Aug 2026, 01:526,060-1
27 Aug 2026, 08:266,061-5
24 Aug 2026, 18:356,066-11
20 Aug 2026, 23:286,077-8
17 Aug 2026, 18:246,085-18
14 Aug 2026, 12:466,103-2
10 Aug 2026, 22:186,105-9
7 Aug 2026, 11:366,114+1
7 Aug 2026, 07:006,113no change
7 Aug 2026, 06:486,113first reading

Engagement

2 posts held, back to 20 June 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 9 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 2 posts for this entry, the most recent from 20 June 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

20 Jun 2024, 15:53 UTC≈72,300 viewsread 12 August 2026
Photo

1️⃣ 🪶🌱$YARD • 4.22M 2️⃣ 🪶$STONKBROKER • 89.05M 3️⃣ 🪶👴$CASHCAT • 141.3M 4️⃣ 💊 👴$ANSEM • 195.7M 5️⃣ 🪶👴$UP • 160.2M 6️⃣ 💊 🌱$Plumber • 2.84M 7️⃣ 🪶$HMM • 17.48M 8️⃣ 💊 $TOAD • 13.77M 9️⃣ 🟣$MANLET • 3.87M 🔟 🔸$CETS • 5.14M 🔄 08.12.26, 03:30 AM UTC ⚠️ NFA. DYOR. Invest at your own risk.

Showing the 2 most recent of 2 posts we hold for @PhanesTrending. 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.

Posts edited after publishing

@PhanesTrending edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
8 August 2026
Most recent edit
12 August 2026

Mentions

Named by 19 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Meta caller
@metacaller · 43,115
Telegram ranks this channel #62 of 78 here — alongside 77 others — read 3 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Phanes Trending” (@PhanesTrending), 6,055 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/PhanesTrending.

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.