Photo, posted without a caption
Signed шищик⬜️🟦⬜️

Channel
@animelolichan
On this record: Topic · Growth · Engagement · Posts · Cite this entry
1,295subscribers
-10 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001267320990 |
|---|---|
| Type | Channel |
| Username | @animelolichan |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/animelolichan |
Other / unclassifiable — 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 18 September 2026 and assigned it the closest of 31 fixed categories, at 84% 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 |
|---|---|---|
| 12 Oct 2026, 04:02 | 1,295 | -3 |
| 5 Oct 2026, 03:00 | 1,298 | +4 |
| 26 Sept 2026, 10:22 | 1,294 | +5 |
| 12 Sept 2026, 04:01 | 1,289 | +4 |
| 7 Sept 2026, 18:17 | 1,285 | +5 |
| 2 Sept 2026, 22:56 | 1,280 | -6 |
| 30 Aug 2026, 14:44 | 1,286 | -5 |
| 27 Aug 2026, 08:45 | 1,291 | +1 |
| 24 Aug 2026, 06:04 | 1,290 | -1 |
| 20 Aug 2026, 19:01 | 1,291 | -1 |
| 18 Aug 2026, 03:02 | 1,292 | -1 |
| 15 Aug 2026, 05:26 | 1,293 | -6 |
| 12 Aug 2026, 03:45 | 1,299 | -6 |
| 6 Aug 2026, 08:05 | 1,305 | no change |
| 6 Aug 2026, 05:46 | 1,305 | first reading |
20 posts held, back to 4 August 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Photo, posted without a caption
Signed шищик⬜️🟦⬜️
Showing the 12 most recent of 20 posts we hold for @animelolichan. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Ламповые тяночки” (@animelolichan), 1,295 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/animelolichan.
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.