Telegram RegisterThe public register of Telegram
Telegram profile photo for CODEX REPACKS

Channel

CODEX REPACKS

@CODEX_REPACKS

Has discussion group

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

8,326subscribers

+216 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-1001577213385
TypeChannel
Username@CODEX_REPACKS
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded25 August 2026
Last confirmed live26 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 26 October 2026
On Telegramt.me/CODEX_REPACKS

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

8,1108,3268,2187 August 2026 — 8,110 subscribers8 August 2026 — 8,116 subscribers11 August 2026 — 8,133 subscribers14 August 2026 — 8,149 subscribers18 August 2026 — 8,153 subscribers21 August 2026 — 8,174 subscribers24 August 2026 — 8,180 subscribers25 August 2026 — 8,180 subscribers28 August 2026 — 8,208 subscribers4 September 2026 — 8,181 subscribers9 September 2026 — 8,194 subscribers13 September 2026 — 8,193 subscribers16 September 2026 — 8,203 subscribers25 September 2026 — 8,245 subscribers4 October 2026 — 8,299 subscribers10 October 2026 — 8,301 subscribers14 October 2026 — 8,306 subscribers17 October 2026 — 8,308 subscribers20 October 2026 — 8,294 subscribers23 October 2026 — 8,302 subscribers26 October 2026 — 8,326 subscribers7 August 202626 October 2026
21 measurements spanning 80 days, net +216. 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 8,078–8,358 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
26 Oct 2026, 13:168,326+24
23 Oct 2026, 03:208,302+8
20 Oct 2026, 09:368,294-14
17 Oct 2026, 04:578,308+2
14 Oct 2026, 10:068,306+5
10 Oct 2026, 18:168,301+2
4 Oct 2026, 21:168,299+54
25 Sept 2026, 14:008,245+42
16 Sept 2026, 16:578,203+10
13 Sept 2026, 03:158,193-1
9 Sept 2026, 11:558,194+13
4 Sept 2026, 07:548,181-27
28 Aug 2026, 03:258,208+28
25 Aug 2026, 11:258,180no change
24 Aug 2026, 20:238,180+6
21 Aug 2026, 12:078,174+21
18 Aug 2026, 07:228,153+4
14 Aug 2026, 20:488,149+16
11 Aug 2026, 12:188,133+17
8 Aug 2026, 08:518,116first reading

Engagement

No public post preview. We read this entry on 25 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

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

“CODEX REPACKS” (@CODEX_REPACKS), 8,326 subscribers as measured 26 October 2026. Telegram Register, tgregister.com/channel/CODEX_REPACKS.

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.