Supergroup
Binance English
@binanceexchange
On this record: Topic · Growth · Engagement · Citations · Cross-platform identity · Cite this entry
338,138members
-23,555 since we began measuring on 5 August 2026
7,469 online right now
Risers and fallers across the register · movement among entries of 316,228–1,000,000.
Register entry
| Telegram ID | -1001146170349 |
|---|---|
| Type | Supergroup |
| Username | @binanceexchange |
| Created | Between 1 May 2016 and 31 December 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 26 September 2026 |
| Measurements held | 37 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/binanceexchange |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 60% 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
| Measured (UTC) | Members | Change |
|---|---|---|
| 26 Sept 2026, 10:16 | 338,138 | -2,684 |
| 19 Sept 2026, 12:55 | 340,822 | -1,066 |
| 17 Sept 2026, 03:37 | 341,888 | -776 |
| 15 Sept 2026, 00:41 | 342,664 | -602 |
| 13 Sept 2026, 12:17 | 343,266 | -701 |
| 11 Sept 2026, 17:40 | 343,967 | -1,055 |
| 9 Sept 2026, 05:40 | 345,022 | -1,579 |
| 5 Sept 2026, 21:36 | 346,601 | -1,046 |
| 3 Sept 2026, 18:58 | 347,647 | -647 |
| 2 Sept 2026, 11:27 | 348,294 | -501 |
| 1 Sept 2026, 12:44 | 348,795 | -551 |
| 31 Aug 2026, 12:27 | 349,346 | -431 |
| 30 Aug 2026, 14:53 | 349,777 | -419 |
| 29 Aug 2026, 17:24 | 350,196 | -566 |
| 28 Aug 2026, 13:46 | 350,762 | -423 |
| 27 Aug 2026, 16:07 | 351,185 | -387 |
| 26 Aug 2026, 13:27 | 351,572 | -600 |
| 25 Aug 2026, 10:46 | 352,172 | -474 |
| 24 Aug 2026, 13:25 | 352,646 | -848 |
| 22 Aug 2026, 22:09 | 353,494 | first reading |
Engagement
No public post preview. We read this entry on 7 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.
Mentions
Named by 43 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
@binance_announcements · 3,415,96612 postsBinance Canteen
@binancecanteen · 1,9368 posts-FREE-
@YTGfree · 12,6086 posts𝘾𝙧𝙮𝙥𝙩𝙤 𝘽𝙖𝙨𝙚 ⚡
@CryptoBase_Official · 10,4415 postsTeleTop中文索引官方频道
@TeleTopOrg · 34,0915 postsCrypto Bounty updates
@CryptoBountyUpdates · 984 postsBinance Moonbix Announcements
@Binance_Moonbix_Announcements · 2,732,7263 postsBinance Lens
@BinanceLens · 4,8853 postsĐecentralized Člub ANN 🔊 3.O (Global Leading Crypto Marketing Agency)
@decentralizedclub · 4,1413 postsAirdrop Updates ☘️🎊
@Airdropupdatescoins · 702 postsAirdrop Watchers
@AirdropWatchers · 26,2802 postsAMA Hunters 🏆🇧🇩
@AMA_HuntersBD · 412 postsBinance
@binank · 4,3352 postsCrypto Exchanges
@cryptoexchanges · 1312 posts非小号交易所公告🅥
@fxhnews · 352 postsEline Geerts
@hhji6 · 12 postsᴍɪᴢᴀɴ7_
@Mizan7_Official · 13,9552 postsBinance Exchange
@binance_online · 51 post电报妹官方频道🅥
@dianbaomei · 611 postEmin INC.
@eminmoney · 31 postGram of TON
@gram · 6,641,0391 postKasper Drops
@kasperdropsz · 131 postگروه مخصوص پخش ارز
@linkgapshit · 291 postKing shahzad
@sahzad11 · 11 post
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.
Cross-platform identity — Wikidata
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | Binance |
|---|---|
| Description | cryptocurrency exchange |
| X / Twitter | @binance |
| YouTube | UCfYw6dhiwGBJQY_-Jcs8ozw |
| Official site | http://www.binance.com/ |
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“Binance English” (@binanceexchange), 338,138 members as measured 26 September 2026. Telegram Register, tgregister.com/channel/binanceexchange.
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.