Telegram RegisterThe public register of Telegram
Telegram profile photo for Binance Alpha Tracker

Channel

Binance Alpha Tracker

@BinanceAlphaTracker

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

67subscribers

-1 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-1002400341115
TypeChannel
Username@BinanceAlphaTracker
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live4 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 4 October 2026
On Telegramt.me/BinanceAlphaTracker

Topic

Other / unclassifiable — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 58% 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

6668677 August 2026 — 68 subscribers10 August 2026 — 68 subscribers23 August 2026 — 67 subscribers30 August 2026 — 66 subscribers4 October 2026 — 67 subscribers7 August 20264 October 2026
5 measurements spanning 58 days, net -1. 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 66–68 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Oct 2026, 06:5767+1
30 Aug 2026, 09:4366-1
23 Aug 2026, 14:3567-1
10 Aug 2026, 01:0168no change
7 Aug 2026, 16:4268first reading

Engagement

19 posts held, back to 8 April 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 19 posts for this entry, the most recent from 15 April 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

15 Apr 2025, 20:45 UTC≈2,820 viewsread 10 August 2026
Photo

https://www.binance.com/en/square/post/448033198377

15 Apr 2025, 20:44 UTC≈1,720 viewsread 10 August 2026
Photo

https://www.binance.com/en/square/post/21315386385345

15 Apr 2025, 20:44 UTC≈2,450 viewsread 10 August 2026
Photo

https://www.binance.com/en/square/post/21847041128674

15 Apr 2025, 20:44 UTC≈2,780 viewsread 10 August 2026
Photo

https://www.binance.com/en/square/post/21559306313385

15 Apr 2025, 20:44 UTC≈1,150 viewsread 10 August 2026

CZ posted: Binance Square just released a dozen new anti-spam features. Hope you like it. https://www.binance.com/en/square/post/1606330

15 Apr 2025, 20:44 UTC≈1,240 viewsread 10 August 2026

CZ posted: Keep building https://www.binance.com/en/square/post/1425381

15 Apr 2025, 20:44 UTC≈1,400 viewsread 10 August 2026

CZ posted: Bitcoin died 11 years ago. Yet, we are still here. https://www.binance.com/en/square/post/21315386385345

15 Apr 2025, 20:44 UTC831 viewsread 10 August 2026

CZ posted: He should have used a CEX. We provide password recovery. 😂 https://www.binance.com/en/square/post/1677341

15 Apr 2025, 20:44 UTC≈1,010 viewsread 10 August 2026

CZ posted: Two people both having access to one private key (or seed) is a very bad idea. It's almost impossible to tell who may have caused the "leak" when a hack happens. Should not be done like that. https://www.binance.com/en/square/post/1677646

Showing the 12 most recent of 19 posts we hold for @BinanceAlphaTracker. 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 4 October 2026 — this entry's latest reading, not the date you are reading this.

“Binance Alpha Tracker” (@BinanceAlphaTracker), 67 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/BinanceAlphaTracker.

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.