rouses.com SOLD
❤2

Channel
@webshellbr
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,523subscribers
-881 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1003512450200 |
|---|---|
| Type | Channel |
| Username | @webshellbr |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/webshellbr |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Oct 2026, 13:04 | 1,523 | -570 |
| 28 Oct 2026, 14:18 | 2,093 | -14 |
| 25 Oct 2026, 03:41 | 2,107 | -192 |
| 22 Oct 2026, 04:47 | 2,299 | -669 |
| 19 Oct 2026, 00:19 | 2,968 | +1 |
| 15 Oct 2026, 23:55 | 2,967 | -46 |
| 12 Oct 2026, 23:15 | 3,013 | -17 |
| 6 Oct 2026, 12:39 | 3,030 | -149 |
| 29 Sept 2026, 07:36 | 3,179 | +1,808 |
| 18 Sept 2026, 22:00 | 1,371 | -117 |
| 14 Sept 2026, 05:40 | 1,488 | -108 |
| 10 Sept 2026, 05:20 | 1,596 | -228 |
| 5 Sept 2026, 00:37 | 1,824 | -81 |
| 1 Sept 2026, 03:45 | 1,905 | -13 |
| 29 Aug 2026, 10:03 | 1,918 | -1 |
| 26 Aug 2026, 03:01 | 1,919 | -52 |
| 23 Aug 2026, 06:39 | 1,971 | -104 |
| 20 Aug 2026, 01:47 | 2,075 | -24 |
| 17 Aug 2026, 10:48 | 2,099 | -193 |
| 14 Aug 2026, 01:28 | 2,292 | first reading |
20 posts held, back to 22 July 2026 — 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
17 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 52.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 52.9% | |
| 👍 | 6 | 35.3% | |
| ❤🔥 | 1 | 5.88% | |
| 🥰 | 1 | 5.88% |
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 6 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 17 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 22 July 2026 to 7 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.
rouses.com SOLD
❤2
⭐100 WEBSHELLS 💲70 USD @covidcodes @webshellbr
⭐100 WEBSHELLS 💲70 USD @covidcodes
⭐100 WEBSHELLS 💲70 USD @covidcodes
이미 mindef.gov.sg에 판매되었습니다. $200 USD @covidcodess🍷 @webshellbr🍷
sell root access gov.my @covidcodes price $200 ma***.gov.my
👍2
⚡️PRICELIST cPanel Bulk⚡️ High DA/PA/DR cPanel Pricelist📌 ⭐100 CPANELS : $75 USD ⭐ 200 CPANELS : $100 USD ⭐ 300 CPANELS : $150 USD ⭐ 400 CPANELS : $200 USD ⭐ 500 CPANELS : $250 USD ⭐ 600 CPANELS : $300 USD ⭐ 700 CPANELS : $350 USD ⭐ 800 CPANELS : $400 USD ⭐ 900 CPANELS : $450 USD ⭐ 1000 CPANELS : $500 USD READ > cannot buy without pricelist,and for high quality,above DA/PA are 25+ 💲PAYMENT: BTC , USDT , ETHERUM…
🌐PRICELIST OF WEBSHELL BULK🌐 High DA/PA/DR Shells Pricelist📌 ⭐100 WEBSHELLS 💲70 USD ⭐200 WEBSHELLS 💲120 USD ⭐300 WEBSHELLS 💲170 USD ⭐400 WEBSHELLS 💲220 USD ⭐500 WEBSHELLS 💲270 USD ⭐600 WEBSHELLS 💲320 USD ⭐700 WEBSHELLS 💲370 USD ⭐800 WEBSHELLS 💲420 USD ⭐900 WEBSHELLS 💲470 USD ⭐1000 WEBSHELLS 💲520 USD All can be guaranteed. READ > cannot buy without pricelist,and for high quality,above DA/PA are 25+ 💲PAYMENT: BTC ,…
Domain : bandungbaratkab.go.id🌐 Price : $150💵 Access : webshell😀 Buy : @covidcodes🍷 Channel @webshellbr⭐️
Domain : seoul.go.kr🌐 Price : $300💵 Access : Root shell access😀 Buy : @covidcodes🍷 Channel @webshellbr⭐️
👍1
justicia.ar WEBSHELL [NO ROOT] price $100 pm for buy @covidcodes🍷 🌐channel @webshellb
❤3
rest domain,dm me for buyy
Showing the 12 most recent of 20 posts we hold for @webshellbr. 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.
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.
@webshellbr 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.
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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“Covid77 Market” (@webshellbr), 1,523 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/webshellbr.
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.