Channel
@Botz_Hunter
On this record: Growth · Engagement · Posts · Polls · Citations · Cite this entry
780subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001162152735 |
|---|---|
| Type | Channel |
| Username | @Botz_Hunter |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 8 August 2026 |
| On Telegram | t.me/Botz_Hunter |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 03:11 | 780 | -1 |
| 7 Aug 2026, 08:00 | 781 | no change |
| 7 Aug 2026, 07:56 | 781 | first reading |
20 posts held, back to 11 September 2022 — 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 4 April 2026. An engagement rate over an empty window would be a number about nothing.
🚀 Introducing: 5-Minute Text Share ⏳ 🌐 https://5m.rqp.workers.dev Need to quickly share text, code, logs, or even random thoughts? This tiny tool has you covered 👇 ✨ Features: • ⚡ Instant paste & share • 🔗 Generates a short link (just 2–3 chars!) • ⏱️ Auto-deletes after 5 minutes • 📋 One-click copy • 🌙 Clean dark/light UI 💡 Perfect for: • Sharing code snippets • Sending temporary notes • Debug logs • Quick privat…
✋
As I promised [ Link ] => https://t.me/unknown_leech_group [ Bot 1 ] => @Leech_code_001_iobot
🔠🔠🔠 🔠🔠 🔠🔠🔠🔠🔠🔠 ✨✨✨✨✨✨✨✨✨✨✨ ✅ Invitation is OPEN for now 💙 KINGS FEATURES - 👑 GDRIVE MIRROR ✅ ✅ 4GB Leech ✅ ❤️ Upto 150GB Mirror 😀 🔻 Multiple Bots ✅ 😎 1 AD token = Access ALL bots for 24h! 🗿 🆒 Enjoy other cool stuff too Leech like a KING 😎 ✨✨✨✨✨✨✨✨✨
Photo, posted without a caption
🗒️ https://x.juv.workers.dev 🔗 https://y.juv.workers.dev
🎅
4️⃣
+1
🕒
https://t.me/PRT_XXX
🙏 https://t.me/Botz_Hunter?boost 🙏
Showing the 12 most recent of 20 posts we hold for @Botz_Hunter. 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.
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.
Ready for paid mirror group?
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 11 September 2022 to 4 April 2026. 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.
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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Botz Hunter 😜” (@Botz_Hunter), 780 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/Botz_Hunter.
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.