Telegram RegisterThe public register of Telegram

Channel

На Поляне🥇

@napolyane2

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

1,937subscribers

+1 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001603415033
TypeChannel
Username@napolyane2
Created4 August 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/napolyane2

Growth

1,9361,9391,937.56 August 2026 — 1,936 subscribers6 August 2026 — 1,936 subscribers7 August 2026 — 1,937 subscribers10 August 2026 — 1,939 subscribers12 August 2026 — 1,937 subscribers1,9376 August 202612 August 2026
5 measurements spanning 6 days, net +1. 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 1,936–1,939 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 17:231,937-2
10 Aug 2026, 01:511,939+2
7 Aug 2026, 12:271,937+1
6 Aug 2026, 16:111,936no change
6 Aug 2026, 16:071,936first reading

Engagement

23 posts held, back to 5 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
24.5%
avg views ÷ 1,937 subscribers
Avg views / post
474
23 posts measured
Reaction rate
4.28%
reactions ÷ views · ER floor
Posts in window
23
of 23 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held23 (5 August 20267 August 2026)
Views total10,899
Reactions total466
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 18:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
12m 19s
Average length
1m 22s

Measured directly from 9 videos 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

466 reactions across 23 posts, in 9 distinct kinds. The most used accounts for 44.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
20544.0%
👍9320.0%
🔥7015.0%
custom 52919958887874066874710.1%
custom 5445284980978621387367.73%
🤬61.29%
😢40.858%
custom 542703894199797607530.644%
😁20.429%

Custom emoji. 3 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 23 of the 23 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 466reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 23 most recent posts we hold, published 5 August 2026 to 7 August 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

7 Aug 2026, 16:06 UTC304 views22 reactionsread 7 August 2026
Photo

Факел в этом сезоне создает тренды, а прошло всего 2 тура. Головка сыра разлетелась так, что в следующем туре Зенит лучшему игроку матча вручил арбуз . А видео с обидчиками, РПЛ обыграли в афиши матча. 🏆На Поляне

11👍6custom 54452849809786213873custom 52919958887874066872

7 Aug 2026, 13:34 UTC322 views19 reactionsread 7 August 2026

Друзья, открытая тренировка Факела и интервью с новичком команды Ходейфа Эль-Мхассани ВК📱 Ютуб 🔥

11custom 52919958887874066873custom 54452849809786213873👍2

7 Aug 2026, 09:20 UTC309 views14 reactionsread 7 August 2026
Forwarded from @premierligaVideo

Встречайте, главный релиз года – РПЛ 2026/27 🐻 Системные требования потянут все 😉 Кто выкупил все отсылки, отмечаетесь в комментариях ⬇️

8custom 52919958887874066873custom 54452849809786213873

7 Aug 2026, 07:48 UTC375 views24 reactionsread 7 August 2026
Video message

Video message, posted without a caption

custom 5445284980978621387138custom 52919958887874066873

7 Aug 2026, 07:23 UTC388 views21 reactionsread 7 August 2026

Ильнур Альшин после матча Факел - Динамо Москва (Расшифровка) - Ильнур, на сегодняшней игре Динамо чем-то вообще удивило или были готовы? - Ну, мы разбирали соперника. Ну, понятно, Динамо - топ-клуб, и у них, в принципе, играл уже второй состав. Ну, не второй состав, там ребята, кто в ротации, кто не играли. Поэтому, не то, что удивило, мы понимали, как они будут играть в целом. -Несколько матчей Факел играет, и к

12🔥3custom 52919958887874066873custom 54452849809786213873

6 Aug 2026, 15:54 UTC386 views8 reactionsread 7 August 2026
Forwarded from @KuryanovDenisVideo

Послематчевый комментарий Тимофея Маринкина: - Ты дебютировал при Ролане Гусеве, Динамо начало сезон с новым тренером, в чем основная разница с Сандро Шварцем? - Даже незнаю в чем основная разница, наверное в том, что один немец, другой русский. - Но кажется, что футбол стал более интенсивным и стало больше прессинга - За Динамо при первом заходе Шварца я смотрел на трибунах. Футбол отличается, больше прессинга,

6👍2

6 Aug 2026, 14:45 UTC379 views15 reactionsread 7 August 2026
Forwarded from @KuryanovDenisVideo

Новый для меня формат, как вам?) Подпишись | Денис Курьянов

👍114

6 Aug 2026, 14:11 UTC458 views11 reactionsread 7 August 2026

Антон Ковалев после матча «Факел» - «Динамо» — Антон, ты выиграл Кубок Белоруссии, какие главные отличия от Кубка России? — Мастерство. Футболисты индивидуально очень сильные, только в этом. Но не скажу, что в Белоруссии очень слабый уровень, просто чуть-чуть ниже. — «Динамо» сегодня удивило? Или были готовы? — Мы были готовы, да. Старались, но доля удачи была на стороне «Динамо». — Тебя долго не было в «Факеле»

9custom 54452849809786213872

6 Aug 2026, 06:27 UTC511 views51 reactionsread 7 August 2026
Video

Сделали небольшой подарок нашему новичку 🏆#ФакелДинамо | На Поляне

👍3111🔥9

6 Aug 2026, 06:05 UTC509 views23 reactionsread 7 August 2026

Алексей Сутормин после матча «Факел» — «Динамо» (расшифровка) — Алексей, больше всего интересно узнать про ваш гол «Краснодару». Показалось, что вы всё видели и, как говорится, «зряча в домик пробили»? — Если честно, там была доля везения, удача, так сказать. Хотел даже пробить в ближний угол, чуть туда не получилось, но мяч оказался у Стаса между ног. Хорошо, что повезло: давно мне лично не везло, и так сложилось,

14👍6custom 54452849809786213873

6 Aug 2026, 05:19 UTC474 views18 reactionsread 7 August 2026
Video

Ильнур Альшин после матча Факел - Динамо • Чем удивило Динамо • Что не хватает Факелу • Тяжелый старт, был ли готов к плохому началу сезона 🏆#ФакелДинамо | На Поляне

11custom 52919958887874066874custom 54270389419979760753

6 Aug 2026, 05:02 UTC506 views24 reactionsread 7 August 2026
Photo

Матвей Бардачев после матча Факел - Динамо - Есть понимание, как исправить ситуацию, три последних матча — три поражения? - Трудно сказать, наверное мы с каждой игрой находим себя. У нас вся игра сводится в концовку, с Махачкалой в концовке пропустили, с Краснодаром в конце два забили и сейчас в конце пропустили. Наверное надо на протяжении 90 минут держать концентрацию и все прийдет. Сезон только начинается. - Со

👍128custom 52919958887874066874

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

Citation-graph rank

Citation-graph rank — 239,794 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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.

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.

“На Поляне🥇” (@napolyane2), 1,937 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/napolyane2.

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.