Binance Wallet Exclusive Campaign with RealGoโs campaign

Channel
๐ฅ Binance Free Signal BD
@binancefreesignalbd
On this record: Topic ยท Growth ยท Engagement ยท Reactions ยท Posts ยท Citations ยท Telegram's recommendations ยท Cite this entry
1,126subscribers
-27 since we began measuring on 6 August 2026
Risers and fallers across the register ยท movement among entries of 1,000โ3,162.
Register entry
| Telegram ID | -1001416174103 |
|---|---|
| Type | Channel |
| Username | @binancefreesignalbd |
| Created | Between 1 April 2019 and 31 October 2021 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 23 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/binancefreesignalbd |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 10:46 | 1,126 | -4 |
| 31 Oct 2026, 10:30 | 1,130 | -6 |
| 28 Oct 2026, 08:44 | 1,136 | -3 |
| 25 Oct 2026, 01:17 | 1,139 | -7 |
| 21 Oct 2026, 17:28 | 1,146 | -4 |
| 18 Oct 2026, 17:10 | 1,150 | -5 |
| 15 Oct 2026, 09:11 | 1,155 | -2 |
| 12 Oct 2026, 15:37 | 1,157 | -6 |
| 5 Oct 2026, 13:37 | 1,163 | -8 |
| 27 Sept 2026, 12:36 | 1,171 | +201 |
| 14 Sept 2026, 09:58 | 970 | -24 |
| 7 Sept 2026, 05:54 | 994 | -10 |
| 2 Sept 2026, 03:32 | 1,004 | -6 |
| 30 Aug 2026, 04:47 | 1,010 | -13 |
| 26 Aug 2026, 21:14 | 1,023 | -60 |
| 24 Aug 2026, 03:34 | 1,083 | -12 |
| 20 Aug 2026, 03:08 | 1,095 | -9 |
| 17 Aug 2026, 10:48 | 1,104 | -11 |
| 14 Aug 2026, 04:49 | 1,115 | -13 |
| 10 Aug 2026, 19:54 | 1,128 | first reading |
Engagement
18 posts held, back to 10 July 2026 โ 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 18 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
3 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ๐ฑ | 2 | 66.7% | |
| โค | 1 | 33.3% |
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 2 of the 18 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 3 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 18 most recent posts we hold, published 10 July 2026 to 6 August 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.
Recent posts
Gate.io Instant $5 Opportunity! Check your Gate.io notifications! - Open your Gate.io notifications - Submit your Gate UID - Answer the quiz: - Answer: B, A - Submit and wait for the reward
Signed Zahidul Islam
โ Check Binance Web3 Booster AlloX Win or Not
For Safety If you've connected PayBox through ChatGPT, you may want to remove the access โข Uninstall the PayBox plugin from ChatGPT โข Remove the Passkey from your phone settings
Signed Najmul Vai
Go to HERE: https://paybox.sh/ Follow info Connect chatgpt or Claude Then connect your x Check Your Reward USDC Go to HERE Click Reveal Key import on Phantom DONE
Bitmart Shutdown๐ Withdraw Your Fund
๐ฑ2
Signed Najmul Vai
๐ New Base App Airdrop is Live! ๐ธ ๐ฐ Earn up to $35 as a new user by completing a few simple tasks. โญโโโโโโโโโโโโโโโโโโโโโฎ โ โจ Quick Steps โ โฐโโโโโโโโโโโโโโโโโโโโโฏ โฃโชผ ๐ฒ Download & install the Base App โฃโชผ ๐ Sign up with a new account โฃโชผ ๐ Enter referral code: ZBYJ3S5B โฃโชผ ๐ต Complete trades totaling $100 & $250 โฃโชผ โณ Hold your balance for 30 days โฐโโโโโโโโโโโโโโโโโโโโ ๐ Join Now: https://base.app/invite/frieโฆ
Signed Zahidul Islam
DAPPOS Opens Official Airdrop Registration! DAPPOS is preparing for the next stage of its ecosystem, and the official airdrop registration portal is now live ๐ Registration Period โข Starts: July 24, 00:00 UTC โข Ends: August 2, 00:00 UTC ๐How To Participate โข Visit the official registration HERE โข Complete all required information โข Submit your registration before the deadline
โค1
Check $ESP Distributed
SkewTrade Waitlist Guide SkewTrade has officially opened its waitlist and is quickly gaining attention within the Hyperliquid ecosystem. According to the project's claims, it is raising 500K $HYPE (approximately $33M) through Hyperion. โญโโโโโโโโโโโโโโโ โฃโชผ Visit: https://skew.trade/ โฃโชผ Submit your Email address โฃโชผ Add your X (Twitter) account โฃโชผ Submit your Telegram username โฃโชผ Complete your registration โฐโโโโโโโโโโฆ
โญโโโโโโโโโโโโโโโ โฃโชผ ORIGIN NFTs Mint is live โฃโชผ https://app.overlayer.fi/origin โฐโโโโโโโโโโโโโโโโ
Binance Wallet Exclusive Campaign with RealGoโs campaign is now live! ๐ Join to earn a share of a 15,000,000 RT token reward pool ๐ Campaign Period: July 16th 8:00 UTC โ July 30th 2026 7:59 UTC ๐ Join Now: https://binance.com/en/events/w3w-exclusive-campaigns Click the RealGo Exclusive Campaign page for more details. Binance Wallet x RealGo - Hold 10 USDT on Wallet - Check-In 7 Days ๐
Showing the 12 most recent of 18 posts we hold for @binancefreesignalbd. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
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.
Named by
Channels on the register whose posts name this channel's handle.
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.
@Trading_Signals_Futures_Binance ยท 36,969
Telegram ranks this channel #55 of 66 here โ alongside 65 others โ read 9 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list 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 3 November 2026 โ this entry's latest reading, not the date you are reading this.
โ๐ฅ Binance Free Signal BDโ (@binancefreesignalbd), 1,126 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/binancefreesignalbd.
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.