Telegram RegisterThe public register of Telegram
Telegram profile photo for ERROR 404‌

Channel

ERROR 404‌

@ERROR13T13

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

202subscribers

-11 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002651307039
TypeChannel
Username@ERROR13T13
Descriptionhttp://t.me/HidenChat_Bot?start=6180905526 13
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded16 October 2026
Last confirmed live17 October 2026
Measurements held10
On Telegramt.me/ERROR13T13

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 16 October 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.

Growth

200213206.57 August 2026 — 213 subscribers8 August 2026 — 212 subscribers15 August 2026 — 208 subscribers23 August 2026 — 204 subscribers29 August 2026 — 200 subscribers6 September 2026 — 204 subscribers14 September 2026 — 201 subscribers29 September 2026 — 200 subscribers9 October 2026 — 202 subscribers16 October 2026 — 202 subscribers2027 August 202616 October 2026
10 measurements spanning 69 days, net -11. 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 198–215 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Oct 2026, 04:17202no change
9 Oct 2026, 14:38202+2
29 Sept 2026, 06:55200-1
14 Sept 2026, 21:37201-3
6 Sept 2026, 12:38204+4
29 Aug 2026, 20:56200-4
23 Aug 2026, 08:57204-4
15 Aug 2026, 20:15208-4
8 Aug 2026, 00:13212-1
7 Aug 2026, 19:32213first 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“ERROR 404‌” (@ERROR13T13), 202 subscribers as measured 16 October 2026. Telegram Register, tgregister.com/channel/ERROR13T13.

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.