Telegram RegisterThe public register of Telegram

Channel

Обзоры с Поли

@obzorpoli

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

9subscribers

+0 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002626668035
TypeChannel
Username@obzorpoli
Created18 July 2025measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live13 August 2026
Measurements held2
On Telegramt.me/obzorpoli

Growth

912 Aug 2026, 14:49 — 9 subscribers12 Aug 2026, 15:01 — 9 subscribers12 Aug 2026, 14:4912 Aug 2026, 15:01
2 measurements taken within a single day. 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 8–10 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 15:019no change
12 Aug 2026, 14:499first reading

Engagement

16 posts held, back to 18 July 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 16 posts for this entry, the most recent from 16 August 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
8
Videos
1
Links
3

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

Video runtime
1m 54s
Average length
1m 54s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

21 reactions across 4 posts, in 7 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5361714800118217989733.3%
🏆419.0%
custom 5264992982720860612314.3%
314.3%
💊29.52%
🍓14.76%
💘14.76%

Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 4 of the 16 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 21reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 16 most recent posts we hold, published 18 July 2025 to 16 August 2025, 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

16 Aug 2025, 12:07 UTC71 viewsread 12 August 2026

У Навии сегодня день рождения ☺☺☺

2 Aug 2025, 19:11 UTC97 viewsread 12 August 2026
Forwarded from @obzoron1Photo

🔳🌸 🔡🔡🔡🔡 – . . . 🤓🚫 🔳 🔠🔳🔳🔳¢·]lana&poli ➡️ · . . . –I'M LEAVING, sorry /;; 👀 🌸 Всем привет, любимые Лаликсы и остальные. Сегодня мы с Поли решили, что я покину сферу обзоров, и Поли продолжит деятельность одна. Могу лишь сказать, что буду помогать Поли с проверками, что возможно поможет ей проверять больше флудов. Спасибо большое людям, которые писали мне в анонку добрые слова, это очень мило и я это ценю. Из

25 Jul 2025, 14:03 UTC123 viewsread 12 August 2026

Посмотрите пожалуйста видео в тик токе, иначе там 1 просмотор 🥹

25 Jul 2025, 12:28 UTC115 viewsread 12 August 2026

Ставьте реакции и делитесь своим мнением об обзоре 😃

25 Jul 2025, 12:26 UTC226 views10 reactionsread 12 August 2026
Photo

🔠🐝🔥#️⃣🌼💛🔠💛🌼🔥 #️⃣#️⃣〰️〰️〰️〰️〰️〰️ Time — 1:54 Ссылка в тик токе — тык Спойлер: Флуд очень активный

custom 53617148001182179893💊21🍓1🏆1💘1custom 52649929827208606121

25 Jul 2025, 11:00 UTC264 views4 reactionsread 12 August 2026

8 > > > > 20 Давайте добьем, я уже обзор записываю 😃😃

🏆2custom 52649929827208606121custom 53617148001182179891

24 Jul 2025, 17:54 UTC62 viewsread 12 August 2026
Forwarded from @soyaaobzorPhoto

🩷🩷🩷🩷 🩷🩷🩷🩷 ➿➿➿➿➿➿➿➿ О Б З О Р Щ И К И Эрика🩷 Унни🩷 Рэйн🩷 Дио🩷 Камилиа🩷 Сталли🩷 Джина🩷 Вэй🩷 Энни🩷 Моррис🩷 Виликс🩷 Мэйви🩷 Милен🩷 Пин🩷 Миэн🩷 Сонён🩷 Шиён🩷 Линда🩷 Кейри🩷 Чу🩷 Долл🩷 Нэлли🩷 Кэмили🩷 Эмирэль🩷 Юни🩷 Меви🩷 Дэтти🩷 Эмми🩷 Мэйс🩷 Виллоу🩷 Аён💕 Рэми💕 Поли💕 Мисо🩷 Нали🩷 Данте🩷 Минчэ💕 Лайа🩷 Ева🩷 Юки🩷 Минори🩷 Кэйсси🩷 Наэлли🩷 Вивен🩷 ➿➿➿➿➿➿➿➿ Х Е Л П Ы Тиа🩷 Биникси💕 Каваи💕 Елизия💕 Смарт💕 Изи💕 Лимули💕 Гнарли💕

23 Jul 2025, 19:43 UTC51 views2 reactionsread 12 August 2026
Photo

Навия с какишом

custom 53617148001182179892

Showing the 12 most recent of 16 posts we hold for @obzorpoli. 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.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

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

“Обзоры с Поли” (@obzorpoli), 9 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/obzorpoli.

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.