Telegram RegisterThe public register of Telegram
Telegram profile photo for Torrent Leeching Groups List

Channel

Torrent Leeching Groups List

@TorrentLeechingGroup

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

6,275subscribers

-202 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-1001397458071
TypeChannel
Username@TorrentLeechingGroup
CreatedBetween 1 October 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded28 August 2026
Last confirmed live29 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/TorrentLeechingGroup

Topic

Software piracy — 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 54% 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

6,2756,4776,3767 August 2026 — 6,477 subscribers7 August 2026 — 6,475 subscribers10 August 2026 — 6,467 subscribers13 August 2026 — 6,456 subscribers17 August 2026 — 6,448 subscribers20 August 2026 — 6,439 subscribers24 August 2026 — 6,434 subscribers27 August 2026 — 6,427 subscribers28 August 2026 — 6,427 subscribers31 August 2026 — 6,418 subscribers3 September 2026 — 6,409 subscribers8 September 2026 — 6,403 subscribers12 September 2026 — 6,389 subscribers16 September 2026 — 6,383 subscribers2 October 2026 — 6,344 subscribers8 October 2026 — 6,327 subscribers13 October 2026 — 6,303 subscribers17 October 2026 — 6,297 subscribers20 October 2026 — 6,286 subscribers26 October 2026 — 6,277 subscribers29 October 2026 — 6,275 subscribers7 August 202629 October 2026
21 measurements spanning 84 days, net -202. 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 6,245–6,507 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
29 Oct 2026, 15:016,275-2
26 Oct 2026, 06:056,277-9
20 Oct 2026, 07:096,286-11
17 Oct 2026, 04:176,297-6
13 Oct 2026, 22:416,303-24
8 Oct 2026, 21:166,327-17
2 Oct 2026, 13:166,344-39
16 Sept 2026, 14:416,383-6
12 Sept 2026, 13:586,389-14
8 Sept 2026, 17:186,403-6
3 Sept 2026, 09:036,409-9
31 Aug 2026, 08:476,418-9
28 Aug 2026, 21:016,427no change
27 Aug 2026, 22:466,427-7
24 Aug 2026, 14:046,434-5
20 Aug 2026, 13:056,439-9
17 Aug 2026, 12:436,448-8
13 Aug 2026, 18:156,456-11
10 Aug 2026, 19:186,467-8
7 Aug 2026, 11:056,475first 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 29 October 2026 — this entry's latest reading, not the date you are reading this.

“Torrent Leeching Groups List” (@TorrentLeechingGroup), 6,275 subscribers as measured 29 October 2026. Telegram Register, tgregister.com/channel/TorrentLeechingGroup.

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.