Telegram RegisterThe public register of Telegram
Telegram profile photo for Clutch Protocol

Channel

Clutch Protocol

@ClutchProtocol

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

137subscribers

-7 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-1003572238909
TypeChannel
Username@ClutchProtocol
CreatedBetween 1 December 2025 and 29 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/ClutchProtocol

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

137144140.57 August 2026 — 144 subscribers8 August 2026 — 144 subscribers15 August 2026 — 143 subscribers30 August 2026 — 140 subscribers9 September 2026 — 139 subscribers1 October 2026 — 138 subscribers11 October 2026 — 137 subscribers7 August 202611 October 2026
7 measurements spanning 65 days, net -7. 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 136–145 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 11:40137-1
1 Oct 2026, 09:58138-1
9 Sept 2026, 14:18139-1
30 Aug 2026, 11:56140-3
15 Aug 2026, 16:44143-1
8 Aug 2026, 21:17144no change
7 Aug 2026, 17:56144first reading

Engagement

20 posts held, back to 29 December 2025 — 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 1 January 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2100.0%

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 2 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 2 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 December 2025 to 1 January 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

1 Jan 2026, 04:14 UTC137 views0 reactionsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 203807.291536 tokens 🔗 https://solscan.io/tx/2XSb8B7jn2ttToUqH7GnNG8gjNFLE6dqjtqiemzEKa48enMvBW7Fqx7mgBxzZ7KxRLYGGC2KGSTGa4pYfNRTyBqX

31 Dec 2025, 19:57 UTC139 viewsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 90293.167531 tokens 🔗 https://solscan.io/tx/2S6kJ3Yh8JyGA6jKxdcpRuykg5bPiva4oTZATVp5yQeesF8PgATVcGR4Nt84mGiTrrtkE7y2iWv1p2teTjTXVVvG

31 Dec 2025, 19:28 UTC119 viewsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 98246.546391 tokens 🔗 https://solscan.io/tx/NBB3MmMUZWAdQJETs8TpYsLjBmCUKBWmiBiCLUVz4g4uJKwAZdpCo5HBnGQNmWbgSkVA4jYpuFo55ebMuGizDxD

31 Dec 2025, 18:20 UTC100 viewsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 99663.947542 tokens 🔗 https://solscan.io/tx/2p7Ti9YgWKQEVYuq4fVhcEHzze7cVVoHmdJtBYGKfme7KXSkYnKg8PYrXNufc9PMgfgt5WnHsiDZsKrEgNsXcYwX

31 Dec 2025, 05:44 UTC88 viewsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 101563.402027 tokens 🔗 https://solscan.io/tx/3hdysVA3ZAkxQaqDcNy9UeMG2XXWXjadgy1PivrrUKZcRBpWaLh6kt9k34xU3cjbdWFXJo8diG2GcqJroTZ38PdC

31 Dec 2025, 03:04 UTC87 viewsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 109183.625206 tokens 🔗 https://solscan.io/tx/5GFPEhcnDBb5cwk9AoJGARueGNSNtUj2Q4pKhWSmcwonvP7431tuZxhS2oR8rAnBje7Wxt89dUbRDuVqy3N3nRuL

31 Dec 2025, 02:37 UTC70 viewsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 107707.369842 tokens 🔗 https://solscan.io/tx/3MaZk66F5KrsoiQBFafRqxg9EYB9q2cnxgwBH5iKHGNQFnLLyxNDre2JzobzULDDzmvpYR2F5dHH5ScftQzzNb7i

31 Dec 2025, 02:33 UTC68 viewsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 95177.418847 tokens 🔗 https://solscan.io/tx/5D7dAYDFLz99G3aRyCDXBH3yfJ5uYz5LKw7UgVwEqpwt2rFaRRB8qE6TiAQ3WfVQJFosYHaSKdzPSjhs63wsNxmr

31 Dec 2025, 02:09 UTCviews —

Clutch Protocol pinned «https://x.com/Clutch_Protocol/status/2006184066341613608»

31 Dec 2025, 02:09 UTC66 views2 reactionsread 8 August 2026

https://x.com/Clutch_Protocol/status/2006184066341613608

❤2

31 Dec 2025, 02:09 UTC64 viewsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 87717.473750 tokens 🔗 https://solscan.io/tx/5NarQK3KeBZHkvvJZ3ny9sGNn9FcJSnfyvc4GkbhrJ6PLJPeq2YC5EWCkrxRM4cE7mDzbYEDW3TzGs28KNwDnxCA

30 Dec 2025, 04:08 UTC71 viewsread 8 August 2026

🔥 New $CLUTCH Burn! Amount: 414481.610500 tokens 🔗 https://solscan.io/tx/23HqarNKpesHmEL9PHTewhXae5zesPvdZ7fGpbMs18cLkpQjSq4tCKcHfWSmJriASroW4SECHNLA4aJpQcdysj5b

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

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

“Clutch Protocol” (@ClutchProtocol), 137 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/ClutchProtocol.

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.