Telegram RegisterThe public register of Telegram
Telegram profile photo for Lustory 18+

Bot

Lustory 18+

@LustoryBot

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

26,425monthly users

+206 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 ID7804816496
TypeBot
Username@LustoryBot
First recorded14 August 2026
Last confirmed live25 August 2026
Measurements held16
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/LustoryBot

Growth

26,21926,92326,5716 August 2026 — 26,219 monthly users7 August 2026 — 26,923 monthly users8 August 2026 — 26,888 monthly users9 August 2026 — 26,813 monthly users11 August 2026 — 26,756 monthly users12 August 2026 — 26,724 monthly users13 August 2026 — 26,782 monthly users14 August 2026 — 26,782 monthly users14 August 2026 — 26,759 monthly users16 August 2026 — 26,608 monthly users17 August 2026 — 26,594 monthly users18 August 2026 — 26,573 monthly users20 August 2026 — 26,624 monthly users22 August 2026 — 26,573 monthly users23 August 2026 — 26,381 monthly users25 August 2026 — 26,425 monthly users26,4256 August 202625 August 2026
16 measurements spanning 18 days, net +206. 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 26,113–27,029 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
25 Aug 2026, 00:2726,425+44
23 Aug 2026, 13:0826,381-192
22 Aug 2026, 00:0826,573-51
20 Aug 2026, 19:2226,624+51
18 Aug 2026, 19:3626,573-21
17 Aug 2026, 17:4726,594-14
16 Aug 2026, 15:5926,608-151
14 Aug 2026, 21:5426,759-23
14 Aug 2026, 19:5426,782no change
13 Aug 2026, 16:0726,782+58
12 Aug 2026, 18:1426,724-32
11 Aug 2026, 15:3126,756-57
9 Aug 2026, 16:0226,813-75
8 Aug 2026, 15:4226,888-35
7 Aug 2026, 18:4126,923+704
6 Aug 2026, 20:0226,219first 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 2 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.

“Lustory 18+” (@LustoryBot), 26,425 monthly users as measured 25 August 2026. Telegram Register, tgregister.com/channel/LustoryBot.

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.