Bot

Cloud

@apkcloudbot

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

42,668monthly users

+9,333 since we began measuring on 7 August 2026

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

Register entry

Telegram ID	8026768379
Type	Bot
Username	@apkcloudbot
First recorded	13 August 2026
Last confirmed live	2 September 2026
Measurements held	12
Confirmed unchanged	1 time, most recently 2 September 2026
On Telegram	t.me/apkcloudbot

Growth

12 measurements spanning 26 days, net +9,333. 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 31,550–47,019 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
2 Sept 2026, 07:46	42,668	-2,103
31 Aug 2026, 04:28	44,771	-463
28 Aug 2026, 03:34	45,234	+570
27 Aug 2026, 03:56	44,664	+1,585
23 Aug 2026, 10:45	43,079	+2,875
18 Aug 2026, 16:43	40,204	+2,642
16 Aug 2026, 14:04	37,562	+1,440
13 Aug 2026, 16:49	36,122	no change
12 Aug 2026, 07:45	36,122	+723
11 Aug 2026, 09:44	35,399	+644
9 Aug 2026, 09:11	34,755	+1,420
7 Aug 2026, 19:00	33,335	first 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 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.

Android Bomber
@asmsbomber · 46,38937 posts

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 2 September 2026 — this entry's latest reading, not the date you are reading this.

“Cloud” (@apkcloudbot), 42,668 monthly users as measured 2 September 2026. Telegram Register, tgregister.com/channel/apkcloudbot.

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.