Channel
@luckydonaldsbots
On this record: Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
1,164subscribers
-19 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001084930802 |
|---|---|
| Type | Channel |
| Username | @luckydonaldsbots |
| Created | Between 1 September 2016 and 30 September 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 25 August 2026 |
| On Telegram | t.me/luckydonaldsbots |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Aug 2026, 12:48 | 1,164 | -3 |
| 22 Aug 2026, 12:04 | 1,167 | -2 |
| 19 Aug 2026, 03:52 | 1,169 | -6 |
| 15 Aug 2026, 19:14 | 1,175 | -2 |
| 12 Aug 2026, 06:27 | 1,177 | -3 |
| 9 Aug 2026, 17:04 | 1,180 | -3 |
| 6 Aug 2026, 08:50 | 1,183 | no change |
| 6 Aug 2026, 00:41 | 1,183 | first reading |
20 posts held, back to 5 December 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 12 November 2025. An engagement rate over an empty window would be a number about nothing.
Experienced another way how the disk can run full, deleted 100 GB of ancient pending RabbitMQ tasks and set a message TTL as well as a maximum queue length. With that the bots are back online. #JoinCaptchaBot #BanWarnBot
Signed lucky lucy
Some bots were down again, which was caused by the disk running full. Deleted 460 GB of log files and restored the services. Bots will process all pending updates normally. #JoinCaptchaBot #BanWarnBot
Signed lucky donald
I'm aware @BanWarnBot is currently not working. I'm looking into it. Edit: fixed.
Signed lucky donald
Due to an misconfiguration in networking, currently all my bots are down. I'll post an update once it's resolved. Bots should pick up what they missed afterwords. Edit: it's resolved
Signed Lucky donald
Fixed an issue where @ChatNetworkBot in some cases didn't reply when it should send an invite link after the /start via deeplinking. Thanks in helping diagnose, L.s. and C. #fixed #ChatNetworkBot
Signed Lucky Donald 💉#️⃣3️⃣
It was brought to attention that with some bots admin commands were no longer working. That was happining for the bots migrated yesterday, because of the new bot API version. This is #fixed now. Thanks for letting me know, A. A.! #BanWarnBot #RulesRulesBot #JoinCaptchaBot
Signed Lucky Donald :
There was an issue with @JoinCaptchaBot not receiving telegram updates for a few hours apparently due to an DNS issue. This is now resolved and the bot seems to have cached up and is working fine again. Apologies if that caused any kicked members because of the message not being there on join as usual.
Signed Lucky Donald :
Done :D
Signed Lucky Donald :
Migrated @RulesRulesBot just now to the new server, was offline for ~5 minutes, to preserve data integrety. Everything seems working as it should. Will now do the same with @RulesRulesBot, so it will not respond for a few minutes as well.
Signed Lucky Donald :
Quick note that DNSControl is awesome!
Signed Lucky Donald :
Also there will be a scheduled downtime for two remaining bots tomorrow, in about 16h 20h from now : - @BanWarnBot - @RulesRulesBot Those have a database, and therefore they need to be take down to not loose any changes happining while the data is moved over. #scheduled #downtime
Signed Lucky Donald :
Heck!
Signed Lucky Donald :
Showing the 12 most recent of 20 posts we hold for @luckydonaldsbots. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
@luckydonaldsbots named 6 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“Luckydonalds Bots: Development/Status” (@luckydonaldsbots), 1,164 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/luckydonaldsbots.
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.