Channel
@bitmusa_announcements
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
160subscribers
-4 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001802446340 |
|---|---|
| Type | Channel |
| Username | @bitmusa_announcements |
| Created | Between 1 September 2022 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 2 times, most recently 14 September 2026 |
| On Telegram | t.me/bitmusa_announcements |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 19:35 | 160 | -3 |
| 23 Aug 2026, 05:35 | 163 | -1 |
| 14 Aug 2026, 20:44 | 164 | no change |
| 14 Aug 2026, 01:34 | 164 | first reading |
20 posts held, back to 11 December 2023 — 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 20 posts for this entry, the most recent from 31 October 2024. An engagement rate over an empty window would be a number about nothing.
166 reactions across 16 posts, in 17 distinct kinds. The most used accounts for 56.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 💩 | 93 | 56.0% | |
| ❤ | 13 | 7.83% | |
| 👍 | 10 | 6.02% | |
| 🖕 | 10 | 6.02% | |
| 👌 | 8 | 4.82% | |
| 🤬 | 6 | 3.61% | |
| 👏 | 5 | 3.01% | |
| 🔥 | 5 | 3.01% | |
| 🤮 | 4 | 2.41% | |
| 👎 | 3 | 1.81% | |
| 🙏 | 2 | 1.20% | |
| 🥱 | 2 | 1.20% | |
| 🍌 | 1 | 0.602% | |
| 🎉 | 1 | 0.602% | |
| 😁 | 1 | 0.602% | |
| 🤔 | 1 | 0.602% | |
| 🥰 | 1 | 0.602% |
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 17 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 166 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 11 December 2023 to 31 October 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
📢 Important Announcement: Bitmusa Futures Exchange Joins BitOpex Options Exchange 📢 We are thrilled to announce that Bitmusa Futures Exchange has officially joined forces with BitOpex Options Exchange, marking a significant step toward expanding trading opportunities and enhancing our ecosystem. This partnership brings together Bitmusa’s robust futures trading expertise and Bitopex’s innovative options platform to …
Extension for Bitmusa Renewal Bitmusa.com Dear Bitmusa Users, We would like to inform you that the renewal period has been extended. The original renewal period: July 4, 2024, 05:00 (UTC) ~ September 3, 2024, 05:00 (UTC) has now been extended to: July 4, 2024, 05:00 (UTC) ~ October 31, 2024, 05:00 (UTC) We sincerely appreciate your understanding and continued support. Bitmusa
Bitmusa Renewal Announcement Bitmusa.com To provide you with enhanced services, we are undertaking a major renewal. This includes comprehensive system updates, the addition of new features, and preparations for upcoming special events. The renewal process will take approximately two months. Please refer to the details below. Renewal Period: July 4, 2024, 05:00 (UTC) ~ September 3, 2024, 05:00 (UTC) Services Affect…
System Maintenance: Bitmusa.com System maintenance is scheduled: March 27, 06:00 ~ 08:00 (UTC) This scheduled maintenance affected: Bitmusa - Website, Mobile, and API. We will provide updates as necessary. Bitmusa
🔥5
System Maintenance: Bitmusa.com System maintenance is scheduled: March 25, 06:00 ~ 07:00 (UTC) This scheduled maintenance affected: Bitmusa - Website, Mobile, and API. We will provide updates as necessary. Bitmusa
❤2👍2
System Maintenance: Bitmusa.com System maintenance is scheduled: March 20, 10:30 ~ 11:00 (UTC) This scheduled maintenance affected: Bitmusa - Website, Mobile, and API. We will provide updates as necessary. Bitmusa
❤1
System Maintenance: Bitmusa.com System maintenance is scheduled: March 19, 02:00 ~ 02:30 (UTC) This scheduled maintenance affected: Bitmusa - Website, Mobile, and API. We will provide updates as necessary. Bitmusa
System Maintenance: Bitmusa.com System maintenance is scheduled: March 14, 08:00 ~ 08:30 (UTC) This scheduled maintenance affected: Bitmusa - Website, Mobile, and API. We will provide updates as necessary. Bitmusa
❤2
System Maintenance: Bitmusa.com System maintenance is scheduled: March 13, 08:55 ~ 13:00 (UTC) This scheduled maintenance affected: Bitmusa - Website, Mobile, and API. We will provide updates as necessary.
❤1👍1👏1
System Maintenance: Bitmusa.com System maintenance schedule is extended: March 11, 05:40 ~ 06:40 (UTC) This scheduled maintenance affected: Bitmusa - Website, Mobile, and API. We will provide updates as necessary.
💩3🤬2👍1🖕1
System Maintenance: Bitmusa.com System maintenance is scheduled: March 11, 04:40 ~ 05:40 (UTC) This scheduled maintenance affected: Bitmusa - Website, Mobile, and API. We will provide updates as necessary.
💩3🖕2
System Maintenance: Bitmusa.com System maintenance schedule is extended: March 8, 05:00 ~ 07:00 (UTC) We will proceed with the new listing of futures trading. We appreciate the opportunity to share this information with you. -New Listing List • ETHUSDT • SOLUSDT • LTCUSDT • ARBUSDT • XLMUSDT • LINKUSDT • OPUSDT • DOGEUSDT • ETCUSDT • AVAXUSDT • MATICUSDT • BCHUSDT • ADAUSDT For a successful listing p…
👎2💩2🎉1👏1
Showing the 12 most recent of 20 posts we hold for @bitmusa_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.
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.
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Bitmusa Announcements” (@bitmusa_announcements), 160 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/bitmusa_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.