برای ورود روی لینک زیر کلیک کنید👇👇 https://t.me/+uhoIqvKneh5jOWVl https://t.me/+uhoIqvKneh5jOWVl

Channel
t.me/MiZapas | @MiZapas
@MiZapas2
On this record: Growth · Engagement · What this channel posts · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Cite this entry
55,511subscribers
+1,464 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001394753960 |
|---|---|
| Type | Channel |
| Username | @MiZapas2 |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 6 September 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 6 September 2026 |
| On Telegram | t.me/MiZapas2 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Sept 2026, 22:20 | 55,511 | -5 |
| 4 Sept 2026, 11:39 | 55,516 | -42 |
| 2 Sept 2026, 23:16 | 55,558 | +7 |
| 1 Sept 2026, 20:14 | 55,551 | +52 |
| 31 Aug 2026, 20:26 | 55,499 | +32 |
| 30 Aug 2026, 17:36 | 55,467 | -67 |
| 29 Aug 2026, 20:45 | 55,534 | -172 |
| 28 Aug 2026, 17:23 | 55,706 | -95 |
| 27 Aug 2026, 20:55 | 55,801 | -54 |
| 26 Aug 2026, 22:53 | 55,855 | -3 |
| 25 Aug 2026, 22:33 | 55,858 | +91 |
| 24 Aug 2026, 21:17 | 55,767 | +148 |
| 23 Aug 2026, 07:07 | 55,619 | -98 |
| 21 Aug 2026, 19:57 | 55,717 | +165 |
| 20 Aug 2026, 14:04 | 55,552 | -6 |
| 19 Aug 2026, 13:42 | 55,558 | -5 |
| 18 Aug 2026, 12:35 | 55,563 | +172 |
| 17 Aug 2026, 14:54 | 55,391 | +104 |
| 16 Aug 2026, 04:48 | 55,287 | +118 |
| 14 Aug 2026, 16:05 | 55,169 | first reading |
Engagement
1 post held, back to 28 January 2026 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 68 pages 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 1 post for this entry, the most recent from 28 January 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 1
Lifetime counters from Telegram’s own channel header, read 9 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
Showing the 1 most recent of 1 post we hold for @MiZapas2. 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.
Posts edited after publishing
@MiZapas2 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
- First edit seen
- 9 August 2026
- Most recent edit
- 7 September 2026
Mentions
Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 1
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 0
- vacant every time we have ever looked
@MiZapas2 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
named in 7 posts, 8 August 2026 – 16 August 2026 · confirmed gone 22 August 2026 (two independent sightings — see how we confirm a dead handle)evidenced
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 6 September 2026 — this entry's latest reading, not the date you are reading this.
“t.me/MiZapas | @MiZapas” (@MiZapas2), 55,511 subscribers as measured 6 September 2026. Telegram Register, tgregister.com/channel/MiZapas2.
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.