Telegram RegisterThe public register of Telegram
Telegram profile photo for HUSTLE TRADE 💸

Bot

HUSTLE TRADE 💸

@HUSTLE_BTC_BOT

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

22,722monthly users

+2,198 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 live26 August 2026
Measurements held17
Confirmed unchanged1 time, most recently 26 August 2026
On Telegramt.me/HUSTLE_BTC_BOT

Growth

20,52422,80421,6647 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 users22,7227 August 202626 August 2026
17 measurements spanning 19 days, net +2,198. 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 20,182–23,146 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
26 Aug 2026, 17:5622,722-82
25 Aug 2026, 17:1222,804+292
24 Aug 2026, 19:0522,512+53
23 Aug 2026, 06:3822,459-22
21 Aug 2026, 18:0622,481+259
20 Aug 2026, 14:4222,222-3
18 Aug 2026, 12:0322,225+27
17 Aug 2026, 09:4522,198+229
15 Aug 2026, 20:4721,969no change
15 Aug 2026, 19:0321,969+1,223
14 Aug 2026, 08:1620,746+128
13 Aug 2026, 02:1320,618-74
12 Aug 2026, 01:0320,692-20
11 Aug 2026, 02:3120,712+18
10 Aug 2026, 02:1220,694+150
9 Aug 2026, 03:5320,544+20
7 Aug 2026, 14:3120,524first 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 26 August 2026 — this entry's latest reading, not the date you are reading this.

“HUSTLE TRADE 💸” (@HUSTLE_BTC_BOT), 22,722 monthly users as measured 26 August 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.