Telegram RegisterThe public register of Telegram
Telegram profile photo for ThePirateFiles

Channel

ThePirateFiles

@ThePirateFiles

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

1,253subscribers

+7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002586714447
TypeChannel
Username@ThePirateFiles
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded3 October 2026
Last confirmed live2 November 2026
Measurements held19
Confirmed unchanged3 times, most recently 2 November 2026
On Telegramt.me/ThePirateFiles

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 93% 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

1,2411,2531,2477 August 2026 — 1,246 subscribers8 August 2026 — 1,247 subscribers11 August 2026 — 1,246 subscribers14 August 2026 — 1,245 subscribers17 August 2026 — 1,243 subscribers21 August 2026 — 1,241 subscribers25 August 2026 — 1,244 subscribers27 August 2026 — 1,242 subscribers30 August 2026 — 1,241 subscribers2 September 2026 — 1,243 subscribers12 September 2026 — 1,246 subscribers16 September 2026 — 1,247 subscribers1 October 2026 — 1,249 subscribers3 October 2026 — 1,249 subscribers8 October 2026 — 1,252 subscribers17 October 2026 — 1,251 subscribers20 October 2026 — 1,250 subscribers24 October 2026 — 1,251 subscribers27 October 2026 — 1,253 subscribers7 August 202627 October 2026
19 measurements spanning 80 days, net +7. 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 1,239–1,255 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Oct 2026, 01:211,253+2
24 Oct 2026, 02:451,251+1
20 Oct 2026, 16:051,250-1
17 Oct 2026, 07:381,251-1
8 Oct 2026, 08:371,252+3
3 Oct 2026, 03:381,249no change
1 Oct 2026, 15:151,249+2
16 Sept 2026, 11:581,247+1
12 Sept 2026, 11:161,246+3
2 Sept 2026, 13:231,243+2
30 Aug 2026, 23:081,241-1
27 Aug 2026, 22:561,242-2
25 Aug 2026, 00:161,244+3
21 Aug 2026, 07:331,241-2
17 Aug 2026, 20:441,243-2
14 Aug 2026, 23:461,245-1
11 Aug 2026, 16:071,246-1
8 Aug 2026, 13:321,247+1
7 Aug 2026, 17:461,246first 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.

“ThePirateFiles” (@ThePirateFiles), 1,253 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/ThePirateFiles.

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.