Best bot of the week!

Channel
Massive Box Updates
@MassiveBoxUpdates
On this record: Growth · Engagement · What this channel posts · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry
71subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001171579343 |
|---|---|
| Type | Channel |
| Username | @MassiveBoxUpdates |
| Description | Development updates by MassiveBox |
| Created | Between 1 March 2018 and 20 October 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/MassiveBoxUpdates |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 23:02 | 71 | no change |
| 6 Aug 2026, 20:19 | 71 | first reading |
Engagement
20 posts held, back to 20 October 2020 — 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 28 December 2020. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 3
- Videos
- 1
- Links
- 13
Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
- Video runtime
- 50s
- Average length
- 50s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
🗂Welcome to @BotsArchive, the most powerful archive in the telegram bots history. Here we will post new useful bots almost everyday, feel free to use our bot @BotsArchiveBot to suggest new ones or search them in our database. 🌐 Website: http://www.botsarchive.com ⚙ APIs: http://www.botsarchive.com/docs.html 👤Get in touch with us: @BotsArchiveSupportbot 🏆 BEST NEW BOTS OF THE WEEK 🏆 🥇 😺 Cats Collection Bot - ⭐️⭐️⭐…
The bot is now published in BotsArchive! Leave a review here: https://t.me/BotsArchive/1685 Thank you.
And what better way to celebrate than listening to this Italian classic Christmas song? https://www.youtube.com/watch?v=uHsTX7I4RGg
🎄 Here in Italy (GMT+1) it's Christmas! Wishing everyone a happy and safe holiday. Remember to follow all the local laws and guidelines to prevent spreading the Corona Virus to your loved ones.
CatsCollection is now running under a load balancer that is spreading load across two server: one on Heroku and one on Kintohub. I've developed it myself with Go using a round robin algorithm. It uses FastHTTP for the server and reverse proxy, so the performance is not bad :D The load balancer itself is running on KintoHub. I'm having a good time with their Docker-based hosting. I will surely extend it to my other bo…
I'm in Montecampione, a small village in the italian pre-Alps. The landscape is awesome!
🤖 New bot in early release! @CatsCollectionBot is a bot I've been working on since August, but that has been put to the side for a long long time. I've decided to polish it and release it now. It's all ready except for the "bonus cat" feature, which will return an error as the bot isn't in BotsArchive yet. But as soon as I'm sure this bot won't make my server crash for no reason, it will be published on BotsArchive…
💬 New Devlog! Updates about WaTgLink development https://massivebox.eu.org/posts/2020/12/watg-devlog1/
Additional spoiler: it's not actually about trains
Spoiler 😳
#freemelee 🔗 123zc (@123zc1)
Showing the 12 most recent of 20 posts we hold for @MassiveBoxUpdates. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
WhatsApp has been stopping my connections because of suspect traffic. What should I do to keep the bot running? * = Would imply asking users for money.
- Limit the number of maximum users connected at the same time21%
- Use proxies*24%
- Make the bot pro only*8%
- Get more users to host instances on their server - Unlikely to happen3%
- Use an external, more reliable, API*18%
- Rewrite the entire bot with another message receiving system - Would take lot of time to develop19%
- Just stop the bot7%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 20 October 2020 to 28 December 2020. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@MassiveBoxUpdates named 1 handle 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 10 August 2026 – 10 August 2026
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“Massive Box Updates” (@MassiveBoxUpdates), 71 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/MassiveBoxUpdates.
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.