Channel
@aokigaharaqq
On this record: Topic · Growth · Engagement · Posts · Cite this entry
711subscribers
-27 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001837677783 |
|---|---|
| Type | Channel |
| Username | @aokigaharaqq |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/aokigaharaqq |
Personal blog — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 75% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 00:02 | 711 | -4 |
| 18 Sept 2026, 05:00 | 715 | -5 |
| 10 Sept 2026, 10:18 | 720 | -5 |
| 1 Sept 2026, 02:33 | 725 | -10 |
| 24 Aug 2026, 03:05 | 735 | +1 |
| 15 Aug 2026, 20:13 | 734 | -4 |
| 7 Aug 2026, 09:18 | 738 | no change |
| 7 Aug 2026, 08:53 | 738 | first reading |
15 posts held, back to 15 February 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 15 posts for this entry, the most recent from 18 July 2026. An engagement rate over an empty window would be a number about nothing.
есть еще такие же как я больные люди, которые удаляют 2 зуба сразу?) / это мне нужно испытать все это дерьмо 3 раза, потом еще брекеты) / кст, если бы я удалила зубы эти сразу, брекеты мне бы и вовсе не пришлось бы ставить, так как у меня зубы пошли похуйне из за них. я молчу про деньги которые я въебываю на все это дерьмо)
мне даже не надо багрового косплеить/моя внешность - мой характер
ty?
в 12 лет посмотреть резеро когда он только выходил и спустя большое кол/во времени ощущать те же эмоции которые ты не ощущаешь от просмотра других аниме
теперь вес не 41 выходит
Video message, posted without a caption
Video message, posted without a caption
Video, posted without a caption
Photo, posted without a caption
Photo, posted without a caption
File, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 15 posts we hold for @aokigaharaqq. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“aokigahara/idk/idc” (@aokigaharaqq), 711 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/aokigaharaqq.
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.