Telegram RegisterThe public register of Telegram

Channel

⚓️Морпехи Севастополя

@morpeh_810

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

20,251subscribers

-27 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001635843426
TypeChannel
Username@morpeh_810
DescriptionКанал посвящён морпехам Краснознамённого Черноморского флота! И прежде всего 810 ОГвБрМП. БОТ для связи; @morpeh_810_bot Регистрация в РКН: https://www.gosuslugi.ru/snet/67331f4f3438580dea7eb970
Created18 October 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/morpeh_810

Growth

20,24920,27820,263.56 August 2026 — 20,278 subscribers7 August 2026 — 20,272 subscribers7 August 2026 — 20,269 subscribers8 August 2026 — 20,265 subscribers10 August 2026 — 20,259 subscribers11 August 2026 — 20,249 subscribers12 August 2026 — 20,253 subscribers13 August 2026 — 20,251 subscribers20,2516 August 202613 August 2026
8 measurements spanning 7 days, net -27. 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 20,245–20,282 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 13:0520,251-2
12 Aug 2026, 12:0520,253+4
11 Aug 2026, 15:3820,249-10
10 Aug 2026, 18:0120,259-6
8 Aug 2026, 20:0420,265-4
7 Aug 2026, 22:0620,269-3
7 Aug 2026, 00:2620,272-6
6 Aug 2026, 02:4520,278first reading

Engagement

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

ERR · 30 days
10.5%
avg views ÷ 20,251 subscribers
Avg views / post
2,130
28 posts measured
Reaction rate
1.69%
reactions ÷ views · ER floor
Posts in window
28
of 28 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 14 August 2026
Posts held28 (29 July 202614 August 2026)
Views total59,711
Reactions total1,012
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Aug 2026, 07:45 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

Photos
6,220
Videos
2,240
Links
2,410

Lifetime counters from Telegram’s own channel header, read 14 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
3m 57s
Average length
1m 59s

Measured directly from 2 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

920 reactions across 25 posts, in 13 distinct kinds. The most used accounts for 54.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🙏50554.9%
11812.8%
👍10911.8%
🔥889.57%
🫡363.91%
💯323.48%
custom 5456235270682729174131.41%
😁90.978%
custom 545651527248565678040.435%
👎20.217%
🤔20.217%
custom 545403912505526385010.109%
👏10.109%

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

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

Telegram Stars

Stars received
11
across the posts below
Posts paid on
2
of 28 we hold a reading for · 7%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @morpeh_810. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 28 most recent posts we hold for this entry, published 29 July 2026 to 14 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

14 Aug 2026, 05:31 UTC352 views10 reactionsread 14 August 2026
Photo

⚡️Фронтовая сводка на утро 14.08.26⚡️ Сумской фронт Идут бои на прежних рубежах — в районе Могрицы, Хотени, а также в районе Вольной Слободы и Уланово. Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🙏7👍21

13 Aug 2026, 16:17 UTC969 views27 reactionsread 14 August 2026

Дорогие подписчики. К нам обратились наши Крымские морпехи с запросами о гуманитарной помощи подразделениям. Набор инструментов (головки, рожковые ключи). Сварочный аппарат (Ресанта 200). Кувалда (10–20 кг). Болгарка 150 (125) + диски (0,8 мм). Электроды (АНО‑21) — 10–15 кг. Автономный отопитель (дизель). Набор отвёрток. Зубило (2 шт.), молоток (0,500 кг) — 2 шт. Свёрла по металлу (разные). Клепальник + клёпки (разм

🙏165👍2😁2💯1🫡1

13 Aug 2026, 06:03 UTC≈1,220 views21 reactionsread 14 August 2026
Photo

⚡️Фронтовая сводка на утро 13.08.26⚡️ Сумской фронт Не прекращаются боестолкновения в районе посёлка Хотень, в Писаревке, Храповщине, Марьино, а также в лесных массивах к югу от Иволжанского. Идут бои в районе Уланово и Вольной Слободы. Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🙏153👍2🤔1

12 Aug 2026, 06:02 UTC≈1,510 views21 reactionsread 14 August 2026
Photo

⚡️Фронтовая сводка на утро 12.08.26⚡️ Сумской фронт ВСУ продолжают контратаковать в районе Могрицы. Продолжаются бои в районе Уланово, Вольной Слободы, а также на участке в районе Хотени. Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🙏183

11 Aug 2026, 09:19 UTC≈1,730 views35 reactionsread 14 August 2026
Photo

ВСУ потеряли до 240 боевиков в зоне действий "Севера" за сутки МО РФ: войска "Севера" нанесли поражение ВСУ в Сумской, Харьковской областях и городе Харьков, противник за сутки потерял до 240 военных Источник Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🔥28🫡7

11 Aug 2026, 09:18 UTC≈1,660 views25 reactionsread 14 August 2026

11 авг - РИА Новости. Курганская область отправила 130 дронов, собранных в регионе, в зону специальной военной операции, сообщила пресс-служба правительства области. "Курганская область отправила очередную партию дронов, сборка которых осуществляется студентами СПО (среднего профессионального образования - ред.) Курганской области по инициативе губернатора Вадима Шумкова", - говорится в сообщении. По словам главы р

👍222👎1

11 Aug 2026, 05:53 UTC≈1,590 views21 reactionsread 14 August 2026
Photo

⚡️Фронтовая сводка на утро 11.08.26⚡️ Сумской фронт ВС РФ отражают контратаки противника в районе Могрицы. Продолжаются боестолкновения в районе Уланово и Вольной Слободы. Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🙏17👍4

10 Aug 2026, 05:29 UTC≈1,860 views26 reactionsread 14 August 2026
Photo

⚡️Фронтовая сводка на утро 10.08.26⚡️ Сумской фронт В Глуховском и Сумском районах продолжаются бои на прежних рубежах. Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🙏26

9 Aug 2026, 07:35 UTC≈2,100 views33 reactionsread 14 August 2026
Photo

⚡️Фронтовая сводка на утро 09.08.26⚡️ Сумской фронт Продолжаются бои в районе Уланово и Вольной Слободы, а также в Писаревке, Марьино и Хотени. Об изменениях в ЛБС не сообщается. Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🙏28🫡41

8 Aug 2026, 08:41 UTC≈2,400 views30 reactionsread 14 August 2026
Photo

⚡️Фронтовая сводка на утро 08.08.26⚡️ Сумской фронт Идут бои в районе Писаревки и Хотени. В Глуховском районе продолжаются бои в Уланово, а также на подступах к Вольной Слободе. Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🙏291

7 Aug 2026, 05:53 UTC≈2,460 views30 reactionsread 14 August 2026
Photo

⚡️Фронтовая сводка на утро 07.08.26⚡️ Сумской фронт ВС РФ расширяют контроль территорий в районе Рыжевки. Сообщается о продвижении ВС РФ у деревни Горки севернее Тёткино. Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🙏282

6 Aug 2026, 06:19 UTC≈2,450 views37 reactionsread 14 August 2026
Photo

⚡️Фронтовая сводка на утро 06.08.26⚡️ Сумской фронт На центральном участке не стихают бои в районах Могрицы, Писаревки, Марьино и Хотени. МО РФ сообщило об освобождении Рыжевки, расположенной на границе с Глушковским районом Курской области в километре к юго-западу от Тёткино. ВС РФ формируют плацдарм, который станет частью буферной зоны в приграничье. Мы ВКонтакте💙 Мы в МАХ 📲 @morpeh_810🤩

🙏352

Showing the 12 most recent of 28 posts we hold for @morpeh_810. 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 — 244,112 of 1,339,933entries 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

Republishes

Channels on the register whose posts this channel has forwarded.

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

“⚓️Морпехи Севастополя” (@morpeh_810), 20,251 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/morpeh_810.

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.