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

Supergroup

Guardian Trending

@GuardianTrending

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

1,830members

+25 since we began measuring on 7 August 2026

125 online right now

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

Register entry

Telegram ID-1002671374306
TypeSupergroup
Username@GuardianTrending
DescriptionLive Trending for ETH, SOL, BASE & BNB Powered by @guardianapp Trending Fast-Track: t.me/guardianapp?start=boost Support: @TokenScanSupport Promotions: @TokenScanPromotions Updates: @TokenScanHub
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 September 2026
Last confirmed live23 September 2026
Measurements held15
On Telegramt.me/GuardianTrending

Topic

Crypto & trading — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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

1,8051,8301,817.57 August 2026 — 1,805 members7 August 2026 — 1,806 members10 August 2026 — 1,805 members13 August 2026 — 1,807 members16 August 2026 — 1,810 members20 August 2026 — 1,808 members23 August 2026 — 1,810 members26 August 2026 — 1,807 members29 August 2026 — 1,818 members1 September 2026 — 1,815 members5 September 2026 — 1,810 members10 September 2026 — 1,808 members14 September 2026 — 1,817 members18 September 2026 — 1,830 members23 September 2026 — 1,830 members7 August 202623 September 2026
15 measurements spanning 47 days, net +25. 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 1,801–1,834 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
23 Sept 2026, 01:261,830no change
18 Sept 2026, 19:391,830+13
14 Sept 2026, 04:571,817+9
10 Sept 2026, 15:581,808-2
5 Sept 2026, 17:391,810-5
1 Sept 2026, 12:331,815-3
29 Aug 2026, 21:241,818+11
26 Aug 2026, 12:181,807-3
23 Aug 2026, 10:081,810+2
20 Aug 2026, 01:511,808-2
16 Aug 2026, 19:471,810+3
13 Aug 2026, 02:131,807+2
10 Aug 2026, 00:291,805-1
7 Aug 2026, 06:461,806+1
7 Aug 2026, 04:461,805first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

Mentions

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

“Guardian Trending” (@GuardianTrending), 1,830 members as measured 23 September 2026. Telegram Register, tgregister.com/channel/GuardianTrending.

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.