Telegram RegisterThe public register of Telegram
Telegram profile photo for Trends Creator/Dev Action Alert

Channel

Trends Creator/Dev Action Alert

@trendsrewardclaim

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

113subscribers

-3 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003814102757
TypeChannel
Username@trendsrewardclaim
CreatedBetween 1 February 2026 and 3 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live18 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/trendsrewardclaim

Growth

113116114.58 August 2026 — 116 subscribers9 August 2026 — 116 subscribers16 August 2026 — 115 subscribers9 September 2026 — 114 subscribers18 September 2026 — 113 subscribers8 August 202618 September 2026
5 measurements spanning 41 days, net -3. 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 113–116 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 13:56113-1
9 Sept 2026, 07:21114-1
16 Aug 2026, 06:18115-1
9 Aug 2026, 05:31116no change
8 Aug 2026, 10:01116first reading

Engagement

20 posts held, back to 3 June 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 31 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Jul 2026, 20:41 UTC23 viewsread 9 August 2026

🔥🔥🔥 X Creator Fee Claim Alert 🪙 Token: SIGHT (Clawglasses) 🧾 CA: ByqipPbSHxzLi6ga5LNrnE229vsLuSrCfHMaDbe1TRND 💰 Market Cap: $1.51K | 📊 24H Volume: $0 🫴 Claimed: 19.849398493 SOL ⏰ Claimed At: 2026-07-31T20:41:47Z 👤 X: Oyster Republic 🦪📲🦞👓 (@oysterecosystem) | 👥 Followers: 43.59K

31 Jul 2026, 20:41 UTC23 viewsread 9 August 2026

🔥🔥🔥 X Creator Fee Claim Alert 🪙 Token: SIGHT (Clawglasses) 🧾 CA: AgpC3FAkeVyf2S4uFZzKZBMVUSJYZaMNn6hv7BUkTRND 💰 Market Cap: $1.46K | 📊 24H Volume: $0 🫴 Claimed: 3.782908555 SOL ⏰ Claimed At: 2026-07-31T20:41:44Z 👤 X: Oyster Republic 🦪📲🦞👓 (@oysterecosystem) | 👥 Followers: 43.59K

31 Jul 2026, 20:41 UTC22 viewsread 9 August 2026

🔥 X Creator Fee Claim Alert 🪙 Token: SIGHT (Clawglasses) 🧾 CA: 8WDjjcs376xv86ogxnGKJXLinWXxoDzRGkjwFRmHTRND 💰 Market Cap: $1.46K | 📊 24H Volume: $0 🫴 Claimed: 0.107246838 SOL ⏰ Claimed At: 2026-07-31T20:41:39Z 👤 X: Oyster Republic 🦪📲🦞👓 (@oysterecosystem) | 👥 Followers: 43.59K

8 Jul 2026, 03:54 UTC42 viewsread 9 August 2026

🔥 X Creator Fee Claim Alert 🪙 Token: 人生K线 (@0xsakura666) 🧾 CA: Aq2j8Rc1ipxWZdFZpmaByg5av132wZJnfQoYHvuKTRND 🧭 Migration: ✅ | 💰 Market Cap: $6.56K | 📊 24H Volume: $1.15K 🫴 Claimed: 0.183614533 SOL ⏰ Claimed At: 2026-07-08T03:54:56Z 👤 X: 0xSakura.Ai🌸 (@0xsakura666) | 👥 Followers: 20.63K

6 Jul 2026, 08:23 UTC36 viewsread 9 August 2026

Dev Fee Claim Alert 🪙 Token: YESTERDAY (@calilyliu) 🧾 CA: 6Gjr55LAFZ67Z2UWLJismusWfu58fr43aQbyN2FeTRND 🧭 Migration: ❌ | 💰 Market Cap: $1.99K | 📊 24H Volume: $0 🫴 Claimed: 0.000369257 SOL ⏰ Claimed At: 2026-07-06T08:23:33Z 👤 Dev: 8FUmdjqsbS2HAiYBg6yJwwT2BNZfAKa5P2GuHYcPFNXZ

6 Jul 2026, 08:23 UTC43 viewsread 9 August 2026

Dev Fee Claim Alert 🪙 Token: 0 (0) 🧾 CA: CHZV2QCKWSs6p3v3B3hpYo4MBcqXSVXFDLbmEhBBTRND 🧭 Migration: ❌ | 💰 Market Cap: $1.99K | 📊 24H Volume: $0 🫴 Claimed: 0.000796 SOL ⏰ Claimed At: 2026-07-06T08:23:33Z 👤 Dev: 8FUmdjqsbS2HAiYBg6yJwwT2BNZfAKa5P2GuHYcPFNXZ

4 Jul 2026, 21:08 UTC32 viewsread 9 August 2026

Dev Fee Claim Alert 🪙 Token: TRUMP COINS (@realDonaldTrump) 🧾 CA: DuPhwwifzjjxJafDphEQoiJBcX6XZwDbkyrkaYnpVoj7 🧭 Migration: ❌ | 💰 Market Cap: $2.09K | 📊 24H Volume: $0 🫴 Claimed: 0.004054823 SOL ⏰ Claimed At: 2026-07-04T21:08:38Z 👤 Dev: 9w9kjr6iRgCvUam3s2nXxW6wGJRWjHRbnFwfyPdDxziP

4 Jul 2026, 21:08 UTC35 viewsread 9 August 2026

Dev Fee Claim Alert 🪙 Token: MCDONALDS (@0xMert_) 🧾 CA: 9cZJjphEF6Jz27kwWYJPNzbDgmNA83ryca9vFG6jC63Y 🧭 Migration: ❌ | 💰 Market Cap: $2.1K | 📊 24H Volume: $0 🫴 Claimed: 0.003101215 SOL ⏰ Claimed At: 2026-07-04T21:08:38Z 👤 Dev: 9w9kjr6iRgCvUam3s2nXxW6wGJRWjHRbnFwfyPdDxziP

4 Jul 2026, 21:08 UTC28 viewsread 9 August 2026

Dev Fee Claim Alert 🪙 Token: SOLAMI COIN (@0xMert_) 🧾 CA: 5KhCQuo8thEXPXJA9cfTPujN9MVpUeBPi7WRP3HFAr3i 🧭 Migration: ❌ | 💰 Market Cap: $2.09K | 📊 24H Volume: $0 🫴 Claimed: 0.005769804 SOL ⏰ Claimed At: 2026-07-04T21:08:38Z 👤 Dev: 9w9kjr6iRgCvUam3s2nXxW6wGJRWjHRbnFwfyPdDxziP

1 Jul 2026, 09:08 UTC32 viewsread 9 August 2026

🔥🔥🔥 X Creator Fee Claim Alert 🪙 Token: 索拉拉 (@easytopredict) 🧾 CA: CY1P83KnKwFYostvjQcoR2HJLyEJWRBRaVQmYyyD3cR8 🧭 Migration: ✅ | 💰 Market Cap: $400.16K | 📊 24H Volume: $9.1K 🫴 Claimed: 6.519032983 SOL ⏰ Claimed At: 2026-07-01T09:08:38Z 👤 X: Muper (@easytopredict) | 👥 Followers: 71.67K

1 Jul 2026, 06:50 UTC29 viewsread 9 August 2026

🔥 Dev Fee Claim Alert 🪙 Token: 文科生的时代 (文中自有比特币和Trends的费用) 🧾 CA: EVtyUuzJyUBGuWbomua7xYTS4H4QLDzmoPgk6KsxTRND 🧭 Migration: ❌ | 💰 Market Cap: $2.04K | 📊 24H Volume: $0 🫴 Claimed: 0.194673093 SOL ⏰ Claimed At: 2026-07-01T06:50:32Z 👤 Dev: GzBkHMfnDBf8HnrRMZz36Kp6rYvAWiXnmuif7SbQZ7Ds

8 Jun 2026, 14:50 UTC45 viewsread 9 August 2026

🔥🔥🔥 X Creator Fee Claim Alert 🪙 Token: 索拉拉 (@easytopredict) 🧾 CA: CY1P83KnKwFYostvjQcoR2HJLyEJWRBRaVQmYyyD3cR8 🧭 Migration: ✅ | 💰 Market Cap: $453.5K | 📊 24H Volume: $60.76K 🫴 Claimed: 8.176941891 SOL ⏰ Claimed At: 2026-06-08T14:50:54Z 👤 X: Muper (@easytopredict) | 👥 Followers: 71.67K

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

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.

“Trends Creator/Dev Action Alert” (@trendsrewardclaim), 113 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/trendsrewardclaim.

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.