Telegram RegisterThe public register of Telegram
Telegram profile photo for ЗВЕРОПОЛИС 2 СМОТРЕТЬ

Channel

ЗВЕРОПОЛИС 2 СМОТРЕТЬ

@zveropolistwo

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

10,295subscribers

+982 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003758334140
TypeChannel
Username@zveropolistwo
Created28 January 2026 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live3 November 2026
Measurements held26
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/zveropolistwo

Topic

Film & TV — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

7,44610,2958,870.57 August 2026 — 9,313 subscribers7 August 2026 — 9,313 subscribers8 August 2026 — 9,300 subscribers11 August 2026 — 9,206 subscribers15 August 2026 — 9,103 subscribers17 August 2026 — 9,020 subscribers20 August 2026 — 8,927 subscribers24 August 2026 — 8,843 subscribers27 August 2026 — 8,746 subscribers30 August 2026 — 8,664 subscribers2 September 2026 — 8,592 subscribers6 September 2026 — 8,486 subscribers11 September 2026 — 8,364 subscribers15 September 2026 — 8,278 subscribers19 September 2026 — 8,177 subscribers29 September 2026 — 7,942 subscribers6 October 2026 — 7,779 subscribers12 October 2026 — 7,644 subscribers15 October 2026 — 7,587 subscribers18 October 2026 — 7,511 subscribers22 October 2026 — 7,446 subscribers25 October 2026 — 7,930 subscribers27 October 2026 — 8,762 subscribers31 October 2026 — 9,487 subscribers2 November 2026 — 10,169 subscribers3 November 2026 — 10,295 subscribers7 August 20263 November 2026
26 measurements spanning 88 days, net +982. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 7,019–10,722 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)SubscribersChange
3 Nov 2026, 18:2610,295+126
2 Nov 2026, 19:2510,169+682
31 Oct 2026, 03:089,487+725
27 Oct 2026, 23:598,762+832
25 Oct 2026, 04:277,930+484
22 Oct 2026, 11:377,446-65
18 Oct 2026, 22:367,511-76
15 Oct 2026, 12:207,587-57
12 Oct 2026, 20:007,644-135
6 Oct 2026, 13:227,779-163
29 Sept 2026, 11:367,942-235
19 Sept 2026, 12:548,177-101
15 Sept 2026, 01:368,278-86
11 Sept 2026, 15:398,364-122
6 Sept 2026, 17:008,486-106
2 Sept 2026, 02:158,592-72
30 Aug 2026, 05:078,664-82
27 Aug 2026, 14:328,746-97
24 Aug 2026, 04:048,843-84
20 Aug 2026, 20:568,927first reading

Engagement

2 posts 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 32 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 2 posts 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

Photos
1
Links
1

Lifetime counters from Telegram’s own channel header, read 4 November 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.

Reaction mix

76 reactions across 1 post, in 3 distinct kinds. The most used accounts for 96.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7396.1%
❤22.63%
👏11.32%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 1 of the 2 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 76 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 2 most recent posts we hold, published 28 January 2026 to 28 January 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

28 Jan 2026, 14:16 UTC≈1,140 views76 reactionsread 4 November 2026
Photo

ФИЛЬМ «ЗВЕРОПОЛИС 2» Для просмотра фильма жми на 🔥 🌐 Обход всех блокировок 🤖 Полезные нейросети 🤡 Пранкбот 🕵️ Шерлок 💫 Купить звезды/подарки/нфт/премиум

🔥73❤2👏1

Showing the 2 most recent of 2 posts we hold for @zveropolistwo. 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

@zveropolistwo 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
3 November 2026
Most recent edit
3 November 2026

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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.

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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“ЗВЕРОПОЛИС 2 СМОТРЕТЬ” (@zveropolistwo), 10,295 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/zveropolistwo.

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.