
Channel
®️Bruno Lucky Jet 🚀
@Bruno_chat_lucky
On this record: Growth · Engagement · Cite this entry
5,848subscribers
-216 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 | -1002126182447 |
|---|---|
| Type | Channel |
| Username | @Bruno_chat_lucky |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 29 August 2026 |
| Last confirmed live | 31 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 31 August 2026 |
| On Telegram | t.me/Bruno_chat_lucky |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 01:56 | 5,848 | -27 |
| 29 Aug 2026, 22:17 | 5,875 | no change |
| 27 Aug 2026, 15:13 | 5,875 | -33 |
| 24 Aug 2026, 07:34 | 5,908 | -25 |
| 20 Aug 2026, 22:14 | 5,933 | -34 |
| 17 Aug 2026, 20:28 | 5,967 | -31 |
| 14 Aug 2026, 23:48 | 5,998 | -43 |
| 11 Aug 2026, 05:52 | 6,041 | -20 |
| 8 Aug 2026, 03:56 | 6,061 | -3 |
| 7 Aug 2026, 13:54 | 6,064 | 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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“®️Bruno Lucky Jet 🚀” (@Bruno_chat_lucky), 5,848 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/Bruno_chat_lucky.
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.