Telegram RegisterThe public register of Telegram
Telegram profile photo for CashClip App

Bot

CashClip App

@CashClipBot

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

10,095monthly users

-1,531 since we began measuring on 6 August 2026

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

Register entry

Telegram ID7146413266
TypeBot
Username@CashClipBot
First recorded22 August 2026
Last confirmed live25 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/CashClipBot

Growth

10,09511,62610,860.56 August 2026 — 11,626 monthly users7 August 2026 — 11,466 monthly users8 August 2026 — 11,280 monthly users9 August 2026 — 11,079 monthly users11 August 2026 — 10,898 monthly users12 August 2026 — 10,719 monthly users13 August 2026 — 10,601 monthly users14 August 2026 — 10,480 monthly users17 August 2026 — 10,420 monthly users18 August 2026 — 10,412 monthly users19 August 2026 — 10,444 monthly users20 August 2026 — 10,454 monthly users22 August 2026 — 10,350 monthly users22 August 2026 — 10,350 monthly users24 August 2026 — 10,183 monthly users25 August 2026 — 10,095 monthly users6 August 202625 August 2026
16 measurements spanning 18 days, net -1,531. 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 9,865–11,856 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
25 Aug 2026, 05:3410,095-88
24 Aug 2026, 01:1410,183-167
22 Aug 2026, 20:0510,350no change
22 Aug 2026, 06:3610,350-104
20 Aug 2026, 18:3610,454+10
19 Aug 2026, 15:3410,444+32
18 Aug 2026, 18:5210,412-8
17 Aug 2026, 15:5810,420-60
14 Aug 2026, 18:0810,480-121
13 Aug 2026, 05:0810,601-118
12 Aug 2026, 02:2310,719-179
11 Aug 2026, 00:5810,898-181
9 Aug 2026, 23:3511,079-201
8 Aug 2026, 20:5411,280-186
7 Aug 2026, 18:4511,466-160
6 Aug 2026, 18:4611,626first 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 9 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“CashClip App” (@CashClipBot), 10,095 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/CashClipBot.

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.