Telegram RegisterThe public register of Telegram
Telegram profile photo for Wockhardt Botnet

Channel

Wockhardt Botnet

@wockystress

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

153subscribers

-11 since we began measuring on 11 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002144247114
TypeChannel
Username@wockystress
CreatedBetween 1 December 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live6 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/wockystress

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 25 September 2026 and assigned it the closest of 31 fixed categories, at 92% 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

153164158.511 August 2026 — 164 subscribers11 August 2026 — 163 subscribers18 August 2026 — 161 subscribers24 August 2026 — 160 subscribers8 September 2026 — 157 subscribers15 September 2026 — 156 subscribers30 September 2026 — 157 subscribers9 October 2026 — 156 subscribers23 October 2026 — 155 subscribers30 October 2026 — 154 subscribers6 November 2026 — 153 subscribers11 August 20266 November 2026
11 measurements spanning 88 days, net -11. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 151–166 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Nov 2026, 16:17153-1
30 Oct 2026, 17:28154-1
23 Oct 2026, 02:59155-1
9 Oct 2026, 20:56156-1
30 Sept 2026, 03:58157+1
15 Sept 2026, 18:56156-1
8 Sept 2026, 16:37157-3
24 Aug 2026, 19:02160-1
18 Aug 2026, 00:11161-2
11 Aug 2026, 02:55163-1
11 Aug 2026, 00:16164first reading

Engagement

14 posts held, back to 29 November 2024 — 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 page 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 14 posts for this entry, the most recent from 31 May 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

12 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 58.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤758.3%
😨216.7%
👏18.33%
💔18.33%
🔥18.33%

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 7 of the 14 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 12 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 29 November 2024 to 31 May 2025, 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

31 May 2025, 19:47 UTC375 views0 reactionsread 11 August 2026

Last chance to join before losing contact on tele ‼️ https://signal.group/#CjQKIGV0Uv9T2OoGHRgbvCizFBNLw3ffHP3iXQ6xUOGZismMEhDqRWivEVR_E7PHm6b6zFU9

4 Mar 2025, 20:59 UTC653 views3 reactionsread 11 August 2026

wockhardt.botnet.su 25565 New CF Anycast SSH Proxy (CNC ONLY) Will be releasing API on Cloudflare Sub-domain shortly!! Best Regards, @mrbendyourbitchover

❤3

25 Feb 2025, 09:23 UTC676 views1 reactionsread 11 August 2026
Photo

Anyone needing their OWN spoof VPS to setup your OWN service? Spoofs start at €25, can get larger hardware specifications for as cheap as €35 (Note this will not increase your pps output) DM @mrbendyourbitchover, I can set you up on fresh node, 750k pps output per.

😨1

25 Feb 2025, 06:12 UTC519 viewsread 11 August 2026

Anyone using API/CNC currently please switch to our EU based proxy, and not our US, hosting is having an outage currently that we do not control. Best Regards, @mrbendyourbitchover, Thanks for understanding!

23 Feb 2025, 01:28 UTC501 viewsread 11 August 2026
Photo

⁨⁨Introducing Wockhardt's Latest Update! • Spoofed Floods Now REQUIRE a CIDR at End of IPV4 Ex. 70.70.70.70/32, 70.70.70.0/24. • Multiple Spoofed Servers Added. 3 1Gbit, 1 200Mbit, 2 HH & 1 Backup Spoof. • Logs Cleared, + Rebooted Servers For Quickest Response Times, & All Users Added 1 Day Compensation. • Slots Increased to 15 from previous 12 slots. • Some floods were replaced, removed, or updated, take a look…

11 Feb 2025, 23:38 UTCviews —

Wockhardt Botnet pinned «Wockhardt Services — Plans & Prices [ Daily Subscriptions: ] Bronze Daily: - Price: €5/day - Concurrent: 1 - Attack Time: 80 seconds - Cooldown: 100 seconds - VIP Access: False - Raw Access: False Silver Daily: - Price: €10/day - Concurrent:…»

9 Feb 2025, 03:59 UTC524 views4 reactionsread 11 August 2026

Wockhardt Services — Plans & Prices [ Daily Subscriptions: ] Bronze Daily: - Price: €5/day - Concurrent: 1 - Attack Time: 80 seconds - Cooldown: 100 seconds - VIP Access: False - Raw Access: False Silver Daily: - Price: €10/day - Concurrent: 1 - Attack Time: 120 seconds - Cooldown: 60 seconds - VIP Access: True - Raw Access: False Gold Daily: - Price: €15/day - Concurrent: 2 - Attack…

❤1👏1💔1😨1

7 Feb 2025, 08:55 UTC342 views2 reactionsread 11 August 2026

Rest of update "!udpplain" renamed to "botnet-udp" "!udpflood" renamed to "botnet-pps" "!vseflood" renamed to "botnet-vse" "!greflood" renamed to "botnet-gre" "!wraflood" renamed to "botnet-wra" "!pshflood" renamed to "botnet-psh" "!tcpflood" renamed to "botnet-tcp" "!ackflood" renamed to "botnet-ack" I sincerely hope everyone gets to enjoy the updates before the upcoming holidays, and can make quick adjustments to…

❤2

7 Feb 2025, 08:55 UTC350 views1 reactionsread 11 August 2026
Photo

Introducing Wockhardt's Latest Update. • Logs Cleared, + Rebooted Servers For Quickest Response Times. • Slots Increased to 12 from previous 6 slots. • Useless L7 floods were removed and ones kept were improved on. • New Floods Introduced! Some to name : "udp" : Custom UDP flood with valid data optimized for bypassing most of your typical targets. "pps" : Plain UDP flood optimized for high pps per concurrent, gen…

🔥1

14 Jan 2025, 07:24 UTC342 viewsread 11 August 2026

Expected Maintenance at 18:00-19:00 UTC Service may be delayed or fully interrupted during this time Updates are to be expected, not fully announced yet. A separate post will be made afterwards to inform you of any new changes. Best Regards @mrbendyourbitchover

Showing the 12 most recent of 14 posts we hold for @wockystress. 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

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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.

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 6 November 2026 — this entry's latest reading, not the date you are reading this.

“Wockhardt Botnet” (@wockystress), 153 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/wockystress.

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.