Posted without readable text

Channel
ANUJ BOTS
@anujbots
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
5,980subscribers
-31 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002454812372 |
|---|---|
| Type | Channel |
| Username | @anujbots |
| Created | Between 1 September 2024 and 8 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 28 October 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 28 October 2026 |
| On Telegram | t.me/anujbots |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 66% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 28 Oct 2026, 13:06 | 5,980 | +113 |
| 25 Oct 2026, 06:56 | 5,867 | +44 |
| 22 Oct 2026, 13:41 | 5,823 | +42 |
| 19 Oct 2026, 02:26 | 5,781 | +8 |
| 15 Oct 2026, 17:00 | 5,773 | +6 |
| 12 Oct 2026, 17:38 | 5,767 | +220 |
| 6 Oct 2026, 08:39 | 5,547 | -48 |
| 29 Sept 2026, 09:19 | 5,595 | -106 |
| 16 Sept 2026, 02:41 | 5,701 | -21 |
| 12 Sept 2026, 14:19 | 5,722 | -35 |
| 8 Sept 2026, 23:19 | 5,757 | -52 |
| 3 Sept 2026, 08:34 | 5,809 | -27 |
| 31 Aug 2026, 06:37 | 5,836 | -22 |
| 27 Aug 2026, 20:43 | 5,858 | -20 |
| 25 Aug 2026, 03:54 | 5,878 | -21 |
| 22 Aug 2026, 08:16 | 5,899 | -28 |
| 19 Aug 2026, 00:02 | 5,927 | -22 |
| 16 Aug 2026, 08:07 | 5,949 | -27 |
| 12 Aug 2026, 17:18 | 5,976 | -29 |
| 9 Aug 2026, 15:15 | 6,005 | first reading |
Engagement
20 posts held, back to 8 March 2025 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 6 pages of 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 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
102 reactions across 16 posts, in 3 distinct kinds. The most used accounts for 61.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 63 | 61.8% | |
| 👍 | 37 | 36.3% | |
| 👌 | 2 | 1.96% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 17 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 March 2025 to 12 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Posted without readable text
Here Are All Useful Bots 1. Camera Hack Bot - Click Here 2. Telegram Views Bot - Click Here 3. Free Recharge Bot - Click Here 4. Free Temp Number Bot - Click Here 5. Phishing Bot - Click Here 6. Twitter Downloader - Click Here 7. Free TG Members Bot - Click Here 8. Free Insta Like & View Bot - Click Here 9. Pinterest Downloader - Click Here 10. Number To Info Bot - Click Here 11. Font Changer Bot - Click Here 12. Bo…
❤4
🚀 BIG UPDATE – Referral Leaderboard Bonus ❄️ 🔥 Get ready for something BIG on 7th May! 🏆 Top Referrers will receive EXTRA BONUS POINTS 💵 📊 Leaderboard Rewards: 🥇 Top 1 → 2000 Points 🥈 Top 2 → 1500 Points 🥉 Top 3 → 1200 Points 😀 Top 4 → 1000 Points 5️⃣ Top 5 → 800 Points 6️⃣ Top 6 → 700 Points 7️⃣ Top 7 → 600 Points 8️⃣ Top 8 → 500 Points 9️⃣ Top 9 → 500 Points 🔟 Top 10 → 500 Points ━━━━━━━━━━━━━━━ 💡 Important: 👉…
❤5
OUR PHISHING BOT RE-STARTED WITH NEW TEMPLATES START BOT⬇️ ✅@INSTA_FB_PHISHINGxBOT ✅@INSTA_FB_PHISHINGxBOT ✅@INSTA_FB_PHISHINGxBOT
3 New theme added in our camera hack bot Start bot - @CameraHackv1Bot
❤5
Commond- /Diposit let upi = "anujffseller@fam" // API Call HTTP.get({ url: "https://anujbots.xyz/api/qr.php?upi=" + upi, success: "/QR" }) Commond- /QR let res = JSON.parse(content) if (res.status == "success") { let order_id = res.data.order_id let qr = res.data.qr_url let expire = res.data.expires_at_ist Api.sendPhoto({ photo: qr, caption: "💳 *Deposit Payment*\n\n" + "⏳ Expire …
❤8
👛 Free FamPay Auto Payment Verification API 💡 Stop relying only on Paytm Business — now enable automatic payment verification with FamPay too! ━━━━━━━━━━━━━━━━━━ 🔍 Features: ❌ Real-time Payment Detection ❌ FamPay / UPI Support ❌ Instant Auto Verification (Success / Failed) ❌ Fast & Reliable API ❌ Easy Integration (Telegram Bots / Websites) ━━━━━━━━━━━━━━━━━━ © API Documentation: 1️⃣ Generate QR Code: GET https:…
❤4
🟣 Introducing Free Instagram Reel Likes & Views Bot We provide an easy way to get Instagram Reel Likes and Views for free. 💵 Earn points and use them to get likes and views on your reels. 🔍 Features: Free Instagram Reel Likes Free Instagram Reel Views Referral earning system ⌛ Fast, safe, and fully automated 🔲 Start now: @FastTgSmmBot @FastTgSmmBot @FastTgSmmBot ━━━━━━━━━━━━━━━ 💎 Enjoy free engagement on your
❤3
❔ Okwin Auto Prediction Bot – Fully Automated! Want your Telegram channel to deliver automatic predictions with real win/loss tracking? Now it’s easier than ever! Get your custom AI-powered prediction bot today. 😀 Features: ❗️ Automatic Win/Loss Detection ❗️ Custom Prediction Times ❗️ Daily Win Targets – Bot stops automatically when reached ❗️ 24/7 Prediction Mode ❗️ Live Predictions – Real-time updates in your cha…
❤1
Do you have a Telegram channel? Are you already monetizing it? 🤔 Try Inside Ads — I’ve already started earning. Here’s the link: https://t.me/InsideAds_bot/open?startapp=r_5863036646
💰 Telegram Bot QR Deposit System (Bots.Business) Users can generate QR, pay using UPI and verify payment to add balance. ━━━━━━━━━━━━━━━━━━━━━━ 1️⃣ /deposit command var upi = "paytm.s1zxmoz@pty" HTTP.get({ url: "https://paytm.anujbots.xyz/qr.php?upi="+upi, success: "/qrCreated" }) ━━━━━━━━━━━━━━━━━━━━━━ 2️⃣ /qrCreated command var data = JSON.parse(content) if(data.success){ var orderid = data.order_id Us…
❤3
Showing the 12 most recent of 20 posts we hold for @anujbots. 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.
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
@anujbots 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 16 posts, 9 August 2026 – 13 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 28 October 2026 — this entry's latest reading, not the date you are reading this.
“ANUJ BOTS” (@anujbots), 5,980 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/anujbots.
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.