Telegram RegisterThe public register of Telegram

Channel

Паньков ДА!️️ 🇷🇺

@pankov_da

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

304subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001941884537
TypeChannel
Username@pankov_da
DescriptionВместе - лучше! 🤝 📲WhatsApp приемная: https://wa.me/+79681618877 💻VKontakte: https://vk.com/dmitrypankovykt
Created27 March 2023measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/pankov_da

Growth

3047 Aug 2026, 14:31 — 304 subscribers8 Aug 2026, 07:50 — 304 subscribers7 Aug 2026, 14:318 Aug 2026, 07:50
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 303–305 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 07:50304no change
7 Aug 2026, 14:31304first reading

Engagement

7 posts held, back to 29 May 2026the 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 7 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
1,090
Videos
425
Links
263

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
1m 07s
Average length
1m 07s

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

35 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 37.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1337.1%
🔥925.7%
custom 5291744946733201983411.4%
👏411.4%
👍25.71%
😱25.71%
😢12.86%

Custom emoji. One row above is a 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 count beside it isTelegram’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 7 of the 7 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 35reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 29 May 2026 to 10 July 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

10 Jul 2026, 04:54 UTC57 views6 reactionsread 8 August 2026
Forwarded from @onf_frontVideo

"Чир! Ты меня слышишь? Тебя нужно срочно эвакуировать, пусть пацаны…" – командир продолжает отдавать команду Иннокентию Лаптеву, бойцу из Якутии. Но ЧИР ЕГО УЖЕ НЕ СЛЫШИТ. Он принял решение идти в одиночку. Плотней прижимает повязки на полученных ранах, берёт самое необходимое и потихоньку, стиснув зубы, выдвигается в эвакуацию. На полпути Чир слышит странные шорохи, вскидывает автомат… ✅ Читайте продолжение в пабл

2👍2🔥2

23 Jun 2026, 07:09 UTC≈1,490 views9 reactionsread 8 August 2026
Photo

Добились: Мархинка снова наполнена водой. В конце мая я писал, что проблема пересыхания реки вернулась - жители улицы Ярославского в Мархе снова остались без воды для полива: https://t.me/pankov_da/1777?single. Причина - закрытые шлюзы. Я, как народный депутат от "Единой России" и руководитель регионального отделения Народного фронта в Якутии, оперативно подключился и держал ситуацию на личном контроле. Итог: ✅ Шл

👏4🔥32

17 Jun 2026, 00:22 UTC89 views4 reactionsread 8 August 2026
Forwarded from @nf_yakutskPhoto

🛃🛃🛃🛃Самосвалы против дачников: из-за 40-тонных машин с песком дорога на Намцырь разбита, автобус отменён. 🌊В Народный фронт Якутии обратились владельцы участков на Намцырском тракте. Всего вдоль тракта расположено 1600 участков, более 1000 из них выданы многодетным семьям. Дорогу разбивают грузовики, возящие песок с карьера - на подъёме появились опасные разломы. Легковые машины буксуют, автобусы не ходят. ❗️Это уж

custom 529174494673320198321🔥1

9 Jun 2026, 04:07 UTC≈1,530 views4 reactionsread 8 August 2026
Photo

С Праздником Всех Святых! 🙏 7 июня 2026 года, архиепископ Якутский и Ленский Роман возглавил праздничное богослужение во Всехсвятском храме. Служба прошла при участии духовенства и прекрасного хора Госфилармонии Якутии. По традиции у входа архипастыря встречали курсанты. После Литургии состоялся крестный ход. Хочу от всего сердца поблагодарить Якутскую епархию за оказанную честь — мне была вручена архиерейская гра

4

6 Jun 2026, 03:20 UTC≈1,620 views4 reactionsread 8 August 2026
Photo

После моего обращения в Якутский комитет природохраны по поводу отсыпки озера вынутым при ремонте дороги грунтом, как народный депутат и руководитель регионального отделения Народного фронта, я получил ответ. Напомню: речь об улице Дежнёва в Якутске. Проверка подтвердила - подрядчик ООО ДРСУ "Сэттэ" разместил отвалы грунта в водоохранной зоне озера "Тёплое". Должностное лицо - производитель работ ООО ДРСУ "Сэттэ" -

🔥3custom 52917449467332019831

2 Jun 2026, 09:28 UTC≈1,440 views6 reactionsread 8 August 2026
Photo

В соцсети, в том числе и ко мне лично, поступают сигналы о некачественном ремонте дороги на улице Севастопольской. Жалобы поступают регулярно - игнорировать их нельзя. Данная дорога стоит на контроле у Народного фронта с прошлого года. Дорога сдана и оплачена, но по результату нашего выезда видим: ❌ Трещины и выбоины на новом покрытии ❌ Провалы у канализационных люков ❌ Тротуарная плитка пошла волной ❌ Застой воды в

4😱1custom 52917449467332019831

29 May 2026, 03:25 UTC≈1,420 views2 reactionsread 8 August 2026
Photo

Мархинка: В 2025 году проблему решили - в 2026 году она вернулась. Жители улицы Ярославского в Мархе снова остались без воды для полива. Только теперь причина не в дамбе. Напомню хронологию: 🔴 2023–2024 - после реконструкции дороги Можайского в реке Мархинке осталась временная дамба. Вода перекрыта, люди покупают её за 500 рублей за 200 литров. Рыба и утки исчезают. 🔴2025 - Народный фронт Якутии добивается решения

😢1😱1

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

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

“Паньков ДА!️️ 🇷🇺” (@pankov_da), 304 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/pankov_da.

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.