Channel
@binance_coin_list
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
303subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001153229670 |
|---|---|
| Type | Channel |
| Username | @binance_coin_list |
| Created | Between 1 February 2019 and 30 September 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/binance_coin_list |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 17:18 | 303 | -1 |
| 27 Aug 2026, 13:43 | 304 | +1 |
| 14 Aug 2026, 16:24 | 303 | -2 |
| 7 Aug 2026, 21:42 | 305 | -1 |
| 6 Aug 2026, 23:16 | 306 | no change |
| 6 Aug 2026, 23:07 | 306 | first reading |
12 posts held, back to 16 August 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 12 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.
6 reactions across 4 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 5 | 83.3% | |
| 👎 | 1 | 16.7% |
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 6 of the 12 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 16 August 2024 to 13 July 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.
ETH SHORT CLOSED: +$9,801 FROM A 1.79% MOVE • Average entry: $1,824.67 • Average exit: $1,792 • Realized PnL: +$9,801 • Implied size: ~300 ETH WHAT happened? ETH failed to hold the $1,825 area and fell below the key $1,800 level, suggesting a resistance rejection or failed breakout. HOW was it executed? Shorted near resistance, held through the breakdown, then closed near $1,792 instead of waiting for the exact bot…
❤3
How a HYPE Short Realized +$342,264: Technical Structure, Macro Context and Exit Execution This was not simply a lucky short. The result came from three elements aligning: a weakening technical structure, a cautious macro environment, and disciplined exit execution. OBSERVED WALLET DATA • Implied average entry: ~$60.14 • Size closed: 50,302.94 HYPE • Closing notional: ~$2.68M • Weighted average exit: ~$53.34 • Exi…
❤1
Photo, posted without a caption
Bot release https://t.me/sabot_official
Profit tuần vừa rồi, vốn $4k
Profit 1 tuần, vốn $2k5
Hmmm 🤨
❤1
BTC đi hơi ghê nhưng BOT của thằng em vẫn tự đánh được, vẫn lụm 1k2 trong ngày.
Channel name was changed to «MT5 Bot Auto Trade»
1 acc bot khác, 2k vốn, 1 tuần lãi 700u. Tham gia bao lợi nhuận, có thể test trước với 100u, chạy trong 1 tuần mất xu nào tôi đền gấp đôi. Win chia sẻ lợi nhuận 3%. Setup bot theo túi tiền của ae. Nhắn tin cho tôi để được hỗ trợ. ——- Another bot account, 2k capital, 1 week profit 700u. Join the profit package, you can test first with 100u, run for 1 week, no matter how much you lose, I will double it. Win shares 3% …
👎1
Bot Trade Account balance: $50k Week profit: $3k6 —— How?
We are plaining to public this BOT so that you can REGISTER and monitor your PnL 😀
Showing the 12 most recent of 12 posts we hold for @binance_coin_list. 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“MT5 Bot Auto Trade” (@binance_coin_list), 303 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/binance_coin_list.
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.