Channel
Bot Updates
@LustifyAI2
On this record: Growth · Engagement · Cite this entry
4,685subscribers
-126 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002513709699 |
|---|---|
| Type | Channel |
| Username | @LustifyAI2 |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/LustifyAI2 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 07:14 | 4,685 | -22 |
| 2 Sept 2026, 20:13 | 4,707 | no change |
| 1 Sept 2026, 22:49 | 4,707 | -22 |
| 29 Aug 2026, 17:35 | 4,729 | -7 |
| 26 Aug 2026, 17:54 | 4,736 | -9 |
| 24 Aug 2026, 03:23 | 4,745 | -13 |
| 20 Aug 2026, 19:35 | 4,758 | -9 |
| 17 Aug 2026, 22:23 | 4,767 | -16 |
| 14 Aug 2026, 12:08 | 4,783 | -15 |
| 10 Aug 2026, 21:37 | 4,798 | -10 |
| 8 Aug 2026, 07:58 | 4,808 | -3 |
| 7 Aug 2026, 15:45 | 4,811 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“Bot Updates” (@LustifyAI2), 4,685 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/LustifyAI2.
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.