Telegram RegisterThe public register of Telegram
Telegram profile photo for BMX Community

Channel

BMX Community

@bmxcommunity

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

5,987subscribers

-278 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002083832083
TypeChannel
Username@bmxcommunity
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live18 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/bmxcommunity

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 12 September 2026 and assigned it the closest of 31 fixed categories, at 57% 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

5,9876,2656,1267 August 2026 — 6,265 subscribers7 August 2026 — 6,264 subscribers10 August 2026 — 6,248 subscribers13 August 2026 — 6,224 subscribers17 August 2026 — 6,205 subscribers20 August 2026 — 6,180 subscribers24 August 2026 — 6,154 subscribers26 August 2026 — 6,138 subscribers29 August 2026 — 6,121 subscribers1 September 2026 — 6,092 subscribers5 September 2026 — 6,072 subscribers10 September 2026 — 6,031 subscribers14 September 2026 — 6,008 subscribers18 September 2026 — 5,987 subscribers7 August 202618 September 2026
14 measurements spanning 42 days, net -278. 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 5,945–6,307 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 18:185,987-21
14 Sept 2026, 04:566,008-23
10 Sept 2026, 08:406,031-41
5 Sept 2026, 06:206,072-20
1 Sept 2026, 21:176,092-29
29 Aug 2026, 15:036,121-17
26 Aug 2026, 20:436,138-16
24 Aug 2026, 03:586,154-26
20 Aug 2026, 20:176,180-25
17 Aug 2026, 10:086,205-19
13 Aug 2026, 23:146,224-24
10 Aug 2026, 10:206,248-16
7 Aug 2026, 14:586,264-1
7 Aug 2026, 12:476,265first reading

Engagement

20 posts held, back to 16 April 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pages 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 4 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

44 reactions across 18 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2250.0%
🔥1125.0%
1022.7%
🤔12.27%

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 18 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 44 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 16 April 2025 to 4 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Dec 2025, 08:53 UTCviews —

BMX Community pinned «https://t.me/BMXHOLDERS/6 🎉Welcome everyone to join the new group, there will be a red envelope tomorrow!»

4 Dec 2025, 08:53 UTC≈1,240 views5 reactionsread 12 August 2026

https://t.me/BMXHOLDERS/6 🎉Welcome everyone to join the new group, there will be a red envelope tomorrow!

3👍2

24 Jul 2025, 06:34 UTC≈2,360 views3 reactionsread 12 August 2026
Photo

BitMart’s new loan feature is here 📢 Stake to earn—AND borrow without selling 💡 Now supporting BMX in two powerful roles: 🔹 Stake BMX and still earn yields 🔹 Borrow BMX for extra flexibility One token, two use cases. Maximum impact. 🎁 Grab limited-time perks 👉 https://www.bitmart.com/activity/cryptoloans/zh-CN

👍3

17 Jul 2025, 10:17 UTC≈1,920 views2 reactionsread 12 August 2026
Photo

🚀 New on BitMart ShootingStar! 💎 Hold $BMX = Get tickets to win $TOPS! 🎟 Hold ≥ 0 BMX → 1 ticket 🎟 Hold ≥ 100 BMX → 2 tickets 🎟 Hold ≥ 200 BMX → 3 tickets ✅ Price protection for 3 days 🎯 1 ticket = 100.59 USDT = 39,447 TOPS Exclusively for BMX holders!

🔥2

17 Jul 2025, 10:17 UTC≈1,560 views3 reactionsread 12 August 2026
Photo

🔥 BitMart has completed the $BMX burn for Q2 2025! As per our Buy-back Mechanism, 20% of platform fee income is used for monthly buy-back & burn. 🧨 Burn continues until 500M BMX are destroyed — ensuring permanent supply reduction. 🔗 Burn record: https://etherscan.io/tx/0x0850b0aaa4c5fede32111dc738eb4af25bb5e929f57222d4c66aa1142132c945 More👉https://bitmart.zendesk.com/hc/en-us/articles/39048949474331-Announcement-o

🔥3

2 Jul 2025, 02:50 UTC≈1,410 views1 reactionsread 12 August 2026
Photo

🔥 #BitMart Spot Trading Cup – Phase 3 is LIVE! Dual Leaderboard Showdown, Battle For The Top! 🚀 🎁Invite Friends & P2P Trading - Claim a 4,000 USDT Worth #Giveaway! 🏆 Spot Trading Leaderboard - Share a prize pool of 8,000 USDT + 8,000 BMX! 👉 Join Now: https://datasink.bitmart.site/t/gR 🗓 Event Period: 07/01/2025 12:00 PM – 07/31/2025 12:00 PM UTC #SpotTradingCup #Crypto #Rewards #BMX

👍1

27 Jun 2025, 13:21 UTC≈1,070 views3 reactionsread 12 August 2026
Photo

🔥"Flash Sale – Happy Sunday" NEWT 30% Off is Now on #BitMart Launchpad! 🎟️ Join now to grab your ticket & get your share of 27,822 NEWT. ⏳Participation Period:06/29 12:00 PM – 07/02 12:00 PM UTC 👉Join Now: https://bitmart.com/launchpad-detail/?activityId=666

3

12 Jun 2025, 02:44 UTC≈1,110 views3 reactionsread 12 August 2026
Photo

🎁 P2P Trading x Savings Fiesta: Enjoy 19.9% APY + Extra Rewards! 🎁 🥇 Event 1: New P2P User Promotion 🥈 Event 2:User Purchase Volume Competition 🥉 Event 3: Unlock Exclusive P2P Investment Product with APY up to 19.99% APY! 💫Join Now: https://www.bitmart.com/activity/P2PTrading_SavingsFiesta/en-US ⏰ 00:00, 06/10/2025 - 23:59, 06/25/2025 (UTC)

2🔥1

30 May 2025, 12:49 UTC≈1,240 views3 reactionsread 12 August 2026
Photo

🔥"Flash Sale – Happy Sunday" HUMA 30% OFF is NOW on #BitMart Launchpad! 🎟️ Join now to grab your ticket & get your share of 214,156.2 HUMA. ⏳Participation Period:06/01 12:00 PM – 06/03 12:00 PM UTC 👉Join Now:https://bitmart.com/launchpad-detail/en-US?activityId=664 #FlashSale #HUMA #Crypto

👍3

22 May 2025, 17:06 UTC≈1,180 views1 reactionsread 12 August 2026
Photo

🔥 #BitMart Pizza Day Crypto Party is LIVE! 🍕🍕🍕 🏆 Trade ≥1,000 BMX in spot to enter the leaderboard 💰 Top 50 traders share 3,000 BMX airdrop 🔒 Hold ≥200 USDT in BMX for 7 days for a shot at 1,000 extra BMX Don't miss your chance to win! 👉 https://www.bitmart.com/activity/PizzaDayCryptoParty/en-US

🔥1

22 May 2025, 06:45 UTC≈1,060 views1 reactionsread 12 August 2026
Photo

🌟Exclusive for Spot New Users🌟 💰BMX Trading Loss Protection, up to 200 USDT! 🚀New users who register within 30 days and make their first BMX trade will receive exclusive “BMX Trading Loss Protection.” On the 1st of each month, if the previous month's BMX return is negative and the price drop is ≤10%, users can claim 100% compensation once, up to 200 USDT in spot trading fee vouchers. Compensation will be issued by

🔥1

Showing the 12 most recent of 20 posts we hold for @bmxcommunity. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Letit Insider
@letit_ai · 36,444
Telegram ranks this channel #10 of 59 here — alongside 58 others — read 1 September 2026
BitMart Exchange Channel
@BitMartExchange_Channel · 60,370
Telegram ranks this channel #15 of 81 here — alongside 80 others — read 21 August 2026
PAXGold Channel
@PAXGold_Channel · 54,050
Telegram ranks this channel #33 of 85 here — alongside 84 others — read 23 August 2026
Airdrop Presents 🗽
@airdrop_Presents · 200,391
Telegram ranks this channel #62 of 82 here — alongside 81 others — read 11 August 2026
Airdrop Broadcaster
@AirdropBroadcasterCom · 49,641
Telegram ranks this channel #65 of 88 here — alongside 87 others — read 25 August 2026

This channel appears in 5 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 18 September 2026 — this entry's latest reading, not the date you are reading this.

“BMX Community” (@bmxcommunity), 5,987 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/bmxcommunity.

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.