Telegram RegisterThe public register of Telegram
Telegram profile photo for OctaPedia•HackersWorld•Cracking•Business

Channel

OctaPedia•HackersWorld•Cracking•Business

@octapedia

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

4,134subscribers

-145 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001451403601
TypeChannel
Username@octapedia
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 September 2026
Last confirmed live28 October 2026
Measurements held21
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/octapedia

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 13 September 2026 and assigned it the closest of 31 fixed categories, at 88% 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

4,1344,2794,206.56 August 2026 — 4,279 subscribers13 August 2026 — 4,275 subscribers16 August 2026 — 4,265 subscribers19 August 2026 — 4,261 subscribers22 August 2026 — 4,255 subscribers25 August 2026 — 4,245 subscribers29 August 2026 — 4,240 subscribers1 September 2026 — 4,235 subscribers4 September 2026 — 4,235 subscribers6 September 2026 — 4,225 subscribers11 September 2026 — 4,216 subscribers15 September 2026 — 4,207 subscribers19 September 2026 — 4,200 subscribers29 September 2026 — 4,180 subscribers7 October 2026 — 4,163 subscribers13 October 2026 — 4,165 subscribers16 October 2026 — 4,157 subscribers19 October 2026 — 4,149 subscribers22 October 2026 — 4,142 subscribers25 October 2026 — 4,138 subscribers28 October 2026 — 4,134 subscribers6 August 202628 October 2026
21 measurements spanning 83 days, net -145. 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 4,112–4,301 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
28 Oct 2026, 04:594,134-4
25 Oct 2026, 14:594,138-4
22 Oct 2026, 18:014,142-7
19 Oct 2026, 13:404,149-8
16 Oct 2026, 13:174,157-8
13 Oct 2026, 06:114,165+2
7 Oct 2026, 04:014,163-17
29 Sept 2026, 22:414,180-20
19 Sept 2026, 14:594,200-7
15 Sept 2026, 05:194,207-9
11 Sept 2026, 14:184,216-9
6 Sept 2026, 14:364,225-10
4 Sept 2026, 19:254,235no change
1 Sept 2026, 19:034,235-5
29 Aug 2026, 09:264,240-5
25 Aug 2026, 23:364,245-10
22 Aug 2026, 21:154,255-6
19 Aug 2026, 20:424,261-4
16 Aug 2026, 13:464,265-10
13 Aug 2026, 00:244,275first 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 28 October 2026 — this entry's latest reading, not the date you are reading this.

“OctaPedia•HackersWorld•Cracking•Business” (@octapedia), 4,134 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/octapedia.

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.