اینجا کانال زاپاسه حتما کانالای اصلی جوین باشید 💜

Channel
چیزبرگر | چیز برگر | Chizbeger | Chiz Berger
@CHiZBERGERiR
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,135subscribers
+967 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001169803724 |
|---|---|
| Type | Channel |
| Username | @CHiZBERGERiR |
| Created | 22 May 2021 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 16 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/CHiZBERGERiR |
Topic
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 16:21 | 2,135 | +196 |
| 5 Oct 2026, 15:20 | 1,939 | +119 |
| 28 Sept 2026, 06:57 | 1,820 | +123 |
| 15 Sept 2026, 17:40 | 1,697 | +73 |
| 12 Sept 2026, 01:59 | 1,624 | +110 |
| 7 Sept 2026, 07:36 | 1,514 | +196 |
| 2 Sept 2026, 10:09 | 1,318 | +28 |
| 30 Aug 2026, 00:03 | 1,290 | +5 |
| 27 Aug 2026, 04:04 | 1,285 | +16 |
| 23 Aug 2026, 19:58 | 1,269 | +35 |
| 20 Aug 2026, 08:38 | 1,234 | +20 |
| 17 Aug 2026, 18:17 | 1,214 | +8 |
| 14 Aug 2026, 20:56 | 1,206 | +14 |
| 11 Aug 2026, 11:22 | 1,192 | +20 |
| 8 Aug 2026, 05:15 | 1,172 | +4 |
| 7 Aug 2026, 05:46 | 1,168 | first reading |
Engagement
5 posts held, back to 22 May 2021 — 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 5 posts for this entry, the most recent from 20 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
جهت ورود به کانالامون کلیک کنید 👇 حتما همشون جوین باشید گممون نکنید 🦁
برای ورود به کانال اصلی بزن رو لینک پایین 👇🏻: https://t.me/+Ri2wqDpSQ5owZTE0 ❌ اینجا کانال زاپاس هست اگر کانال اصلی فیلتر شد اینجا فعالیت میکنیم ❌
برای ورود به کانال اصلی بزن رو لینک پایین 👇🏻: https://t.me/+Ri2wqDpSQ5owZTE0 ❌ اینجا کانال زاپاس هست اگر کانال اصلی فیلتر شد اینجا فعالیت میکنیم ❌
Channel created
Showing the 5 most recent of 5 posts we hold for @CHiZBERGERiR. 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.
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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“چیزبرگر | چیز برگر | Chizbeger | Chiz Berger” (@CHiZBERGERiR), 2,135 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/CHiZBERGERiR.
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.