Telegram RegisterThe public register of Telegram
Telegram profile photo for leak.me | Crypto KOL Tracker

Channel

leak.me | Crypto KOL Tracker

@leakmealpha

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

3,051subscribers

+434 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002100146361
TypeChannel
Username@leakmealpha
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/leakmealpha

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

2,5993,0512,8257 August 2026 — 2,617 subscribers7 August 2026 — 2,617 subscribers11 August 2026 — 2,618 subscribers14 August 2026 — 2,617 subscribers17 August 2026 — 2,616 subscribers20 August 2026 — 2,612 subscribers24 August 2026 — 2,613 subscribers28 August 2026 — 2,601 subscribers31 August 2026 — 2,603 subscribers9 September 2026 — 2,599 subscribers12 September 2026 — 2,950 subscribers17 September 2026 — 3,051 subscribers7 August 202617 September 2026
12 measurements spanning 41 days, net +434. 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 2,531–3,119 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 04:213,051+101
12 Sept 2026, 19:012,950+351
9 Sept 2026, 03:182,599-4
31 Aug 2026, 08:432,603+2
28 Aug 2026, 04:442,601-12
24 Aug 2026, 19:062,613+1
20 Aug 2026, 18:442,612-4
17 Aug 2026, 20:532,616-1
14 Aug 2026, 19:072,617-1
11 Aug 2026, 02:342,618+1
7 Aug 2026, 11:312,617no change
7 Aug 2026, 11:182,617first reading

Engagement

20 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1100.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 1 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 1 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 5 August 2026 to 7 August 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

7 Aug 2026, 10:06 UTC42 viewsread 7 August 2026
Photo

NEW PROJECT: @bstocksfinance just surfaced as Binance's dedicated stocks account. 19 KOLs we track followed in the last 24h. The product hit $500M+ AUM tracking 1:1-backed tokenized US securities that trade 24/7 on BNB Chain. Caught early on leak.me

7 Aug 2026, 00:06 UTC68 viewsread 7 August 2026
Photo

ALPHA CALL: @clickl3ss reverse-engineered a wallet that called 25 of 25 Robinhood listings, then front-ran it into CASHCAT before the official listing dropped. 45 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 22:09 UTC71 viewsread 7 August 2026
Photo

ALPHA CALL: @clickl3ss tracked one wallet that called 25 of 25 Robinhood listings. On July 22 a $500 CASHCAT probe tipped the next one — the researchers who studied the pattern caught the trade before the listing hit. 33 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 22:07 UTC68 viewsread 7 August 2026
Photo

PRODUCT UPDATE: @deltaliquidity just shipped Pools. Anyone can now LP on spot, curve or bid-ask configs and earn WETH fees from any token pool on Robinhood Chain. 3 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 20:07 UTC62 viewsread 7 August 2026
Photo

ALPHA CALL: @clickl3ss reverse-engineered a wallet that preceded 25 of 25 Robinhood listings. When it probed CASHCAT with a ~$500 position, most trackers ignored it. He accumulated. Robinhood listed CASHCAT shortly after. 14 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 18:07 UTC77 viewsread 7 August 2026
Photo

PRE-LAUNCH: @bananiumm is running a free mint on Arc, the institutional chain with BlackRock, Visa and Mastercard as founding validators. Mainnet drops Sept 16. 2 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 17:06 UTC76 viewsread 7 August 2026
Photo

LIVE CAMPAIGN: @fuegonft mint is live now. Public minting opens 19:00 UTC at 0.045 ETH for the Lighter identity layer. 3 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 16:11 UTC75 viewsread 7 August 2026
Photo

LIVE CAMPAIGN: @kuant_exchange Season 5 Trading Competition is in its final hours. Leaderboard still moving on every trade, points tied to the airdrop. 3 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 16:09 UTC77 viewsread 7 August 2026
Photo

PRE-LAUNCH: @brc_exchange goes live August 8 at 2PM UTC. The $BRC memecoin evolves into a full Arc DEX suite: swap, LP, staking, and a P2P USDC marketplace bridging Base and Arc. 3 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 14:09 UTC73 viewsread 7 August 2026
Photo

PRODUCT UPDATE: @unclemac just confirmed StonkPit crossed 10M transactions on Robinhood Chain, roughly 1 in 8 of the chain's recent activity. Site clean-ups, a Bones overhaul and slots are next. 2 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 14:06 UTC69 viewsread 7 August 2026
Photo

NEW PROJECT: @hookrfun just went live on Robinhood Chain. Gen 3 opens writes for launching, blueprints and trading — plus the HOOKR token is now on chain. Tokens graduate into locked Uniswap v4 pools with programmable hooks baked in. 4 KOLs we track followed in the last 24h. Caught early on leak.me

6 Aug 2026, 12:08 UTC72 views1 reactionsread 7 August 2026
Photo

PRE-LAUNCH: @apex_ether ships a Uniswap v4 hook on Robinhood chain later today, token attached. He calls it gamified and experimental. 5 KOLs we track followed in the last 24h. Caught early on leak.me

1

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

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“leak.me | Crypto KOL Tracker” (@leakmealpha), 3,051 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/leakmealpha.

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.