Telegram RegisterThe public register of Telegram
Telegram profile photo for HUSTLE TRADE πŸ’Έ

Bot

HUSTLE TRADE πŸ’Έ

@HUSTLE_BTC_BOT

On this record: Topic Β· Growth Β· Engagement Β· Citations Β· Cite this entry

18,184monthly users

-2,340 since we began measuring on 7 August 2026

Risers and fallers across the register Β· movement among entries of 10,000–31,623.

Register entry

Telegram ID1657027321
TypeBot
Username@HUSTLE_BTC_BOT
First recorded15 August 2026
Last confirmed live29 October 2026
Measurements held48
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/HUSTLE_BTC_BOT

Topic

Marketing & affiliate β€” 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 65% 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

18,18422,95620,5707 August 2026 β€” 20,524 monthly users9 August 2026 β€” 20,544 monthly users10 August 2026 β€” 20,694 monthly users11 August 2026 β€” 20,712 monthly users12 August 2026 β€” 20,692 monthly users13 August 2026 β€” 20,618 monthly users14 August 2026 β€” 20,746 monthly users15 August 2026 β€” 21,969 monthly users15 August 2026 β€” 21,969 monthly users17 August 2026 β€” 22,198 monthly users18 August 2026 β€” 22,225 monthly users20 August 2026 β€” 22,222 monthly users21 August 2026 β€” 22,481 monthly users23 August 2026 β€” 22,459 monthly users24 August 2026 β€” 22,512 monthly users25 August 2026 β€” 22,804 monthly users26 August 2026 β€” 22,722 monthly users27 August 2026 β€” 22,628 monthly users28 August 2026 β€” 22,585 monthly users30 August 2026 β€” 22,654 monthly users31 August 2026 β€” 22,800 monthly users1 September 2026 β€” 22,857 monthly users3 September 2026 β€” 22,769 monthly users5 September 2026 β€” 22,713 monthly users8 September 2026 β€” 22,956 monthly users11 September 2026 β€” 22,697 monthly users13 September 2026 β€” 22,732 monthly users14 September 2026 β€” 22,485 monthly users16 September 2026 β€” 21,140 monthly users19 September 2026 β€” 20,702 monthly users25 September 2026 β€” 19,292 monthly users4 October 2026 β€” 19,293 monthly users9 October 2026 β€” 19,117 monthly users13 October 2026 β€” 19,360 monthly users14 October 2026 β€” 19,281 monthly users15 October 2026 β€” 19,103 monthly users16 October 2026 β€” 18,911 monthly users17 October 2026 β€” 18,914 monthly users18 October 2026 β€” 18,952 monthly users20 October 2026 β€” 18,890 monthly users21 October 2026 β€” 18,856 monthly users22 October 2026 β€” 18,733 monthly users23 October 2026 β€” 18,280 monthly users24 October 2026 β€” 18,493 monthly users26 October 2026 β€” 18,520 monthly users27 October 2026 β€” 18,478 monthly users28 October 2026 β€” 18,422 monthly users29 October 2026 β€” 18,184 monthly users7 August 202629 October 2026
48 measurements spanning 83 days, net -2,340. 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 17,468–23,672 and does not start at zero.
Measurement log β€” every monthly users count we have recorded, most recent 20 of 48
Measured (UTC)Monthly usersChange
29 Oct 2026, 06:1818,184-238
28 Oct 2026, 05:5118,422-56
27 Oct 2026, 07:1718,478-42
26 Oct 2026, 10:4818,520+27
24 Oct 2026, 10:0518,493+213
23 Oct 2026, 13:0518,280-453
22 Oct 2026, 15:0018,733-123
21 Oct 2026, 09:3718,856-34
20 Oct 2026, 10:5618,890-62
18 Oct 2026, 12:5818,952+38
17 Oct 2026, 13:5818,914+3
16 Oct 2026, 14:5818,911-192
15 Oct 2026, 14:0619,103-178
14 Oct 2026, 17:2119,281-79
13 Oct 2026, 07:1119,360+243
9 Oct 2026, 01:2219,117-176
4 Oct 2026, 11:3519,293+1
25 Sept 2026, 21:4119,292-1,410
19 Sept 2026, 06:3720,702-438
16 Sept 2026, 18:3821,140first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry β€” they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

Mentions

Named by 6 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.

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.

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 29 October 2026 β€” this entry's latest reading, not the date you are reading this.

β€œHUSTLE TRADE πŸ’Έβ€ (@HUSTLE_BTC_BOT), 18,184 monthly users as measured 29 October 2026. Telegram Register, tgregister.com/channel/HUSTLE_BTC_BOT.

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.