Telegram RegisterThe public register of Telegram
Telegram profile photo for BEAR-C2

Channel

BEAR-C2

@BearC2

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry

431subscribers

+1 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002086696545
TypeChannel
Username@BearC2
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/BearC2

Growth

430433431.57 August 2026 — 430 subscribers8 August 2026 — 430 subscribers15 August 2026 — 431 subscribers24 August 2026 — 433 subscribers30 August 2026 — 431 subscribers4317 August 202630 August 2026
5 measurements spanning 23 days, net +1. 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 430–433 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 15:55431-2
24 Aug 2026, 02:33433+2
15 Aug 2026, 20:48431+1
8 Aug 2026, 05:18430no change
7 Aug 2026, 13:39430first reading

Engagement

19 posts held, back to 11 January 2026the 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.

ERR · 30 days
21.7%
avg views ÷ 431 subscribers
Avg views / post
93.4
5 posts measured
Reaction rate
2.93%
reactions ÷ views · ER floor
Posts in window
5
of 19 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 3 of 5 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held19 (11 January 20267 August 2026)
Views total467
Reactions total9
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05:18 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
6m 15s
Average length
1m 15s

Measured directly from 5 videos 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.

Reaction mix

73 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 46.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3446.6%
❤‍🔥1723.3%
👾1317.8%
912.3%

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

Measured over the 19 most recent posts we hold, published 11 January 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.

Recent posts

7 Aug 2026, 10:12 UTC49 views3 reactionsread 8 August 2026
Photo

Be The Threat To Defeat It ❤️‍🔥

❤‍🔥3

6 Aug 2026, 13:14 UTC81 viewsread 8 August 2026
Video

"Just block api.telegram.org." 🤷 Problem solved... right? Then let's block Discord's API, Google Drive, and Dropbox too. Every time a legitimate platform is abused, we'll just add another domain to the blocklist. The challenge has never been the platform. The transport changes. The tradecraft doesn't. That's why this stage focuses on integrating different cloud communication channels into a complete framework rathe

4 Aug 2026, 10:41 UTC106 views3 reactionsread 8 August 2026
Video

What if an adversary didn't need a dedicated C2 server? 🤔 This simulation replaces dedicated C2 servers, fixed IPs, and domains with a Telegram Bot using the Telegram Bot API over encrypted HTTPS. Commands are sent through a private chat. Outputs over 4000 chars are split automatically.

3

2 Aug 2026, 19:08 UTC152 views3 reactionsread 8 August 2026
Photo

8 countries. 8 critical sectors. One APT 🔥🔥🔥 Everyone talks about killing two birds with one stone... 🪨🐦 Operation Olalampo proved that Charming Kitten (Iranian APT) could hit 8 birds with one stone. 🎯 Egypt, Saudi Arabia, UAE, Turkey, Hungary, Turkmenistan, Israel, and South America. 🏛 Government, Healthcare, Financial Services, Energy, Education, Telecommunications, Defense, and Industrial. GitHub Repository: h

🔥3

20 Jul 2026, 13:35 UTC233 views0 reactionsread 8 August 2026
Video

Added a new Execution Mode to improve session visibility during long running tasks. When a command is still executing the session now switches from Active to Executing so you always know why the response is taking longer. This is especially useful for OPSEC focused protocols like DoH where output is split into smaller chunks to blend with normal traffic then reassembled before being displayed to the operator. Sessi

14 Jul 2026, 13:25 UTC280 views2 reactionsread 8 August 2026
Photo

RustyWater ShellCode Dropper has emerged as a key component in recent Static Kitten (MuddyWater) operations targeting organizations in the Gulf and broader Middle East. Written in Rust and disguised as a legitimate looking reddit.exe, this implant serves as the main payload and backbone of their attacks. It uses a multi-stage dropper (CertificationKit.ini) that decrypts and deploys the payload at runtime, establishe

2

25 May 2026, 13:35 UTC469 views4 reactionsread 8 August 2026
Video

https://github.com/S3N4T0R-0X0/Malicious-PixelCode

🔥4

17 May 2026, 13:24 UTC518 views6 reactionsread 8 August 2026

The ceasefire in the Middle East never included cyber warfare. Iranian APTs are still actively targeting government, energy, healthcare, telecommunications, and private sectors across the region and behind the political silence, cyber operations never stopped. Read “Static Kitten APT Adversary Simulation“ by S3N4T0R on Medium: https://medium.com/@S3N4T0R/static-kitten-apt-adversary-simulation-8f595aa74118

🔥4❤‍🔥2

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

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

“BEAR-C2” (@BearC2), 431 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/BearC2.

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.