Telegram RegisterThe public register of Telegram
Telegram profile photo for DailyCash

Bot

DailyCash

@DailyCashsbot

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

51,503monthly users

-51,673 since we began measuring on 6 August 2026

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

Register entry

Telegram ID8257290566
TypeBot
Username@DailyCashsbot
First recorded10 August 2026
Last confirmed live6 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 6 September 2026
On Telegramt.me/DailyCashsbot

Growth

51,503103,17677,339.56 August 2026 — 103,176 monthly users8 August 2026 — 100,115 monthly users10 August 2026 — 97,392 monthly users10 August 2026 — 97,392 monthly users14 August 2026 — 94,370 monthly users16 August 2026 — 92,114 monthly users17 August 2026 — 88,688 monthly users19 August 2026 — 85,036 monthly users23 August 2026 — 79,895 monthly users25 August 2026 — 75,699 monthly users26 August 2026 — 71,507 monthly users28 August 2026 — 67,088 monthly users30 August 2026 — 62,542 monthly users2 September 2026 — 56,332 monthly users6 September 2026 — 51,503 monthly users6 August 20266 September 2026
15 measurements spanning 31 days, net -51,673. 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 43,752–110,927 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
6 Sept 2026, 14:0151,503-4,829
2 Sept 2026, 23:5656,332-6,210
30 Aug 2026, 21:1662,542-4,546
28 Aug 2026, 18:1867,088-4,419
26 Aug 2026, 15:0371,507-4,192
25 Aug 2026, 14:4375,699-4,196
23 Aug 2026, 01:0479,895-5,141
19 Aug 2026, 19:1885,036-3,652
17 Aug 2026, 19:2688,688-3,426
16 Aug 2026, 15:1492,114-2,256
14 Aug 2026, 21:1394,370-3,022
10 Aug 2026, 16:2797,392no change
10 Aug 2026, 09:0597,392-2,723
8 Aug 2026, 06:44100,115-3,061
6 Aug 2026, 21:18103,176first 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 16 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 6 September 2026 — this entry's latest reading, not the date you are reading this.

“DailyCash” (@DailyCashsbot), 51,503 monthly users as measured 6 September 2026. Telegram Register, tgregister.com/channel/DailyCashsbot.

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.