Bot

LaysBot

@Laysua_bot

On this record: Growth · Engagement · Cite this entry

16,978monthly users

-41,550 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 ID	792459312
Type	Bot
Username	@Laysua_bot
First recorded	12 August 2026
Last confirmed live	26 August 2026
Measurements held	7
Confirmed unchanged	3 times, most recently 26 August 2026
On Telegram	t.me/Laysua_bot

Growth

7 measurements spanning 17 days, net -41,550. 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 10,746–64,761 and does not start at zero.

Measurement log — every monthly users count we have recorded
Measured (UTC)	Monthly users	Change
25 Aug 2026, 04:45	16,978	-2,639
22 Aug 2026, 09:39	19,617	-4,676
20 Aug 2026, 00:52	24,293	-14,576
16 Aug 2026, 16:14	38,869	-13,134
12 Aug 2026, 02:49	52,003	no change
11 Aug 2026, 14:52	52,003	-6,525
7 Aug 2026, 21:48	58,528	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.

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.

“LaysBot” (@Laysua_bot), 16,978 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/Laysua_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.