Supergroup
BugSecurityIL
@BugSecurityIL
On this record: Topic · Growth · Engagement · Cite this entry
1,206members
-11 since we began measuring on 6 August 2026
123 online right now
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001233021680 |
|---|---|
| Type | Supergroup |
| Username | @BugSecurityIL |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 4 October 2026 |
| Last confirmed live | 1 November 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 1 November 2026 |
| On Telegram | t.me/BugSecurityIL |
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 4 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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) | Members | Change |
|---|---|---|
| 1 Nov 2026, 11:48 | 1,206 | -1 |
| 29 Oct 2026, 03:31 | 1,207 | +2 |
| 23 Oct 2026, 12:00 | 1,205 | -1 |
| 20 Oct 2026, 13:40 | 1,206 | -2 |
| 10 Oct 2026, 17:15 | 1,208 | -1 |
| 4 Oct 2026, 20:59 | 1,209 | -3 |
| 4 Oct 2026, 03:26 | 1,212 | no change |
| 9 Sept 2026, 09:15 | 1,212 | -1 |
| 3 Sept 2026, 20:57 | 1,213 | -2 |
| 28 Aug 2026, 13:34 | 1,215 | +1 |
| 25 Aug 2026, 20:43 | 1,214 | -1 |
| 22 Aug 2026, 10:29 | 1,215 | -1 |
| 16 Aug 2026, 16:48 | 1,216 | -1 |
| 6 Aug 2026, 09:13 | 1,217 | first reading |
Engagement
Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 1 November 2026 — this entry's latest reading, not the date you are reading this.
“BugSecurityIL” (@BugSecurityIL), 1,206 members as measured 1 November 2026. Telegram Register, tgregister.com/channel/BugSecurityIL.
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.