Telegram RegisterThe public register of Telegram
Telegram profile photo for 🤖 Kawaii Uz • Bot 3.1v

Bot

🤖 Kawaii Uz • Bot 3.1v

@Kawaii_uz_bot

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

25,227monthly users

+1,768 since we began measuring on 12 August 2026

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

Register entry

Telegram ID7974105046
TypeBot
Username@Kawaii_uz_bot
First recorded15 August 2026
Last confirmed live29 August 2026
Measurements held15
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/Kawaii_uz_bot

Growth

22,95425,22724,090.512 August 2026 — 23,459 monthly users13 August 2026 — 22,954 monthly users14 August 2026 — 23,624 monthly users15 August 2026 — 23,624 monthly users16 August 2026 — 23,586 monthly users17 August 2026 — 23,843 monthly users18 August 2026 — 24,085 monthly users19 August 2026 — 24,135 monthly users20 August 2026 — 24,222 monthly users23 August 2026 — 23,827 monthly users24 August 2026 — 24,607 monthly users25 August 2026 — 24,778 monthly users26 August 2026 — 24,961 monthly users27 August 2026 — 25,138 monthly users29 August 2026 — 25,227 monthly users12 August 202629 August 2026
15 measurements spanning 17 days, net +1,768. 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 22,613–25,568 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
29 Aug 2026, 17:2325,227+89
27 Aug 2026, 17:3425,138+177
26 Aug 2026, 20:2324,961+183
25 Aug 2026, 23:3224,778+171
24 Aug 2026, 20:5724,607+780
23 Aug 2026, 03:5523,827-395
20 Aug 2026, 15:3324,222+87
19 Aug 2026, 12:3524,135+50
18 Aug 2026, 15:2324,085+242
17 Aug 2026, 13:4823,843+257
16 Aug 2026, 08:3623,586-38
15 Aug 2026, 18:5123,624no change
14 Aug 2026, 22:1623,624+670
13 Aug 2026, 14:2822,954-505
12 Aug 2026, 08:1723,459first 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.

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

“🤖 Kawaii Uz • Bot 3.1v” (@Kawaii_uz_bot), 25,227 monthly users as measured 29 August 2026. Telegram Register, tgregister.com/channel/Kawaii_uz_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.