Telegram RegisterThe public register of Telegram
Telegram profile photo for Threat Hunting Usecases

Channel

Threat Hunting Usecases

@threat_hunting_usecases

Has discussion group

On this record: Topic · Growth · Engagement · Cite this entry

5,629subscribers

-83 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001393568878
TypeChannel
Username@threat_hunting_usecases
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded30 August 2026
Last confirmed live27 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 27 October 2026
On Telegramt.me/threat_hunting_usecases

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 37% 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

5,6285,7125,6707 August 2026 — 5,712 subscribers8 August 2026 — 5,711 subscribers11 August 2026 — 5,705 subscribers15 August 2026 — 5,701 subscribers17 August 2026 — 5,699 subscribers24 August 2026 — 5,697 subscribers27 August 2026 — 5,690 subscribers30 August 2026 — 5,687 subscribers30 August 2026 — 5,687 subscribers2 September 2026 — 5,681 subscribers7 September 2026 — 5,672 subscribers11 September 2026 — 5,658 subscribers15 September 2026 — 5,660 subscribers27 September 2026 — 5,642 subscribers5 October 2026 — 5,641 subscribers11 October 2026 — 5,633 subscribers14 October 2026 — 5,629 subscribers18 October 2026 — 5,628 subscribers20 October 2026 — 5,633 subscribers24 October 2026 — 5,632 subscribers27 October 2026 — 5,629 subscribers5,6297 August 202627 October 2026
21 measurements spanning 81 days, net -83. 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 5,615–5,725 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
27 Oct 2026, 10:015,629-3
24 Oct 2026, 05:395,632-1
20 Oct 2026, 19:185,633+5
18 Oct 2026, 05:075,628-1
14 Oct 2026, 19:305,629-4
11 Oct 2026, 21:155,633-8
5 Oct 2026, 07:185,641-1
27 Sept 2026, 07:185,642-18
15 Sept 2026, 22:405,660+2
11 Sept 2026, 23:205,658-14
7 Sept 2026, 19:385,672-9
2 Sept 2026, 21:545,681-6
30 Aug 2026, 12:235,687no change
30 Aug 2026, 09:425,687-3
27 Aug 2026, 04:035,690-7
24 Aug 2026, 13:035,697-2
17 Aug 2026, 18:135,699-2
15 Aug 2026, 00:565,701-4
11 Aug 2026, 10:035,705-6
8 Aug 2026, 09:015,711first 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 27 October 2026 — this entry's latest reading, not the date you are reading this.

“Threat Hunting Usecases” (@threat_hunting_usecases), 5,629 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/threat_hunting_usecases.

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.