Channel
انمي Berserk
@Berserkzn
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
5,268subscribers
+644 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001725102674 |
|---|---|
| Type | Channel |
| Username | @Berserkzn |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 22 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/Berserkzn |
Topic
Gaming — 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 62% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 20:46 | 5,268 | +4 |
| 30 Oct 2026, 17:56 | 5,264 | +21 |
| 27 Oct 2026, 20:20 | 5,243 | -43 |
| 24 Oct 2026, 20:19 | 5,286 | +31 |
| 22 Oct 2026, 05:19 | 5,255 | +24 |
| 18 Oct 2026, 16:16 | 5,231 | +33 |
| 15 Oct 2026, 15:30 | 5,198 | +30 |
| 12 Oct 2026, 11:42 | 5,168 | +72 |
| 5 Oct 2026, 16:42 | 5,096 | +92 |
| 27 Sept 2026, 22:00 | 5,004 | +109 |
| 15 Sept 2026, 08:57 | 4,895 | +44 |
| 11 Sept 2026, 11:39 | 4,851 | +32 |
| 6 Sept 2026, 11:01 | 4,819 | +60 |
| 2 Sept 2026, 12:49 | 4,759 | no change |
| 1 Sept 2026, 22:36 | 4,759 | +25 |
| 29 Aug 2026, 21:15 | 4,734 | +34 |
| 26 Aug 2026, 18:03 | 4,700 | +11 |
| 24 Aug 2026, 02:13 | 4,689 | +2 |
| 20 Aug 2026, 20:13 | 4,687 | +23 |
| 17 Aug 2026, 11:34 | 4,664 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@uuBGu · 34,025
Telegram ranks this channel #4 of 8 here — alongside 7 others — read 4 September 2026
@w89999 · 114,991
Telegram ranks this channel #6 of 13 here — alongside 12 others — read 4 September 2026
@rrdzr · 38,502
Telegram ranks this channel #16 of 19 here — alongside 18 others — read 4 September 2026
@JJXJXXz · 124,345
Telegram ranks this channel #17 of 26 here — alongside 25 others — read 13 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 2 November 2026 — this entry's latest reading, not the date you are reading this.
“انمي Berserk” (@Berserkzn), 5,268 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/Berserkzn.
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.