Telegram RegisterThe public register of Telegram
Telegram profile photo for Binance Miningpool Announcements

Channel

Binance Miningpool Announcements

@binancePool_announcements

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

8subscribers

-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-1002232100101
TypeChannel
Username@binancePool_announcements
Created19 June 2024 — measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live12 October 2026
Measurements held3
Confirmed unchanged6 times, most recently 12 October 2026
On Telegramt.me/binancePool_announcements

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 2 October 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

898.57 August 2026 — 9 subscribers12 August 2026 — 9 subscribers23 August 2026 — 8 subscribers7 August 202623 August 2026
3 measurements spanning 16 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 8–9 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 18:588-1
12 Aug 2026, 11:469no change
7 Aug 2026, 12:489first reading

Engagement

16 posts held, back to 19 June 2024 — 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 16 posts for this entry, the most recent from 21 June 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

21 Jun 2024, 06:02 UTC10 viewsread 12 August 2026

Binance Completes Integration of Tether (USDT) on Toncoin Network, Opens Deposits and Withdrawals https://www.binance.com/en/support/announcement/f6c4867f5cab47e39864130804eff106

21 Jun 2024, 03:01 UTC9 viewsread 12 August 2026

AVA Flexible Products: Complete Subscription to Enjoy Up to 6% Bonus Tiered APR! https://www.binance.com/en/support/announcement/9c67e03f0acc40aaae89227c983bc89b

21 Jun 2024, 02:02 UTC4 viewsread 12 August 2026

Binance Will Support the Metal DAO (MTL) Mainnet Swap https://www.binance.com/en/support/announcement/80da471195ef4cf393605e89342058d6

20 Jun 2024, 14:13 UTC3 viewsread 12 August 2026

Notice on New Trading Pairs & Trading Bots Services on Binance Spot - 2024-06-21 https://www.binance.com/en/support/announcement/40379d0ab5d74070b4f22a648d34b507

20 Jun 2024, 13:31 UTC3 viewsread 12 August 2026

Binance Adds LayerZero (ZRO) on Earn, Buy Crypto, Convert, Margin & Futures https://www.binance.com/en/support/announcement/09bdfa5901c94bf6a4e60ab66078a75c

20 Jun 2024, 11:54 UTC2 viewsread 12 August 2026

LayerZero (ZRO) Listing Will Be Postponed https://www.binance.com/en/support/announcement/86d3d85e975b4eba802ed65951d69dbd

20 Jun 2024, 11:48 UTC3 viewsread 12 August 2026

In case you missed it, our CTO Rohit Wad just shared his perspectives on how #BinanceBuild captures the spirit that’s powered our growth over the years – with you, our users, at the heart of it.

20 Jun 2024, 10:50 UTC3 viewsread 12 August 2026

Updated: Binance Will Support the Fetch .ai (FET), Ocean Protocol (OCEAN) and SingularityNET (AGIX) Token Merge https://www.binance.com/en/support/announcement/e485541c370240adba3929fded74f269

20 Jun 2024, 10:32 UTC2 viewsread 12 August 2026

Binance Adds Lista (LISTA) on Earn, Buy Crypto, Convert, Margin & Futures https://www.binance.com/en/support/announcement/6f7bdac5744c4a109b1042496764df91

20 Jun 2024, 09:01 UTC2 viewsread 12 August 2026

Learn & Earn: Complete Courses & Quizzes to Earn CVP Rewards! (2024-06-20) https://www.binance.com/en/support/announcement/177ec50e01034c63b1da5b0a9c5cf3b6

20 Jun 2024, 06:26 UTC2 viewsread 12 August 2026

Binance Will List LayerZero (ZRO) with Seed Tag Applied https://www.binance.com/en/support/announcement/28a21b10ed23416386b40d263b71cd99

20 Jun 2024, 03:01 UTC2 viewsread 12 August 2026

Updates on Tick Size for Spot Trading Pairs (2024-06-27) https://www.binance.com/en/support/announcement/eb8c059da7ce44ce8a30df7536045b2b

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

“Binance Miningpool Announcements” (@binancePool_announcements), 8 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/binancePool_announcements.

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.