Telegram RegisterThe public register of Telegram

Channel

капитан ненавидит море

@knmore

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

481subscribers

+2 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001052305376
TypeChannel
Username@knmore
CreatedBetween 1 May 2016 and 31 March 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/knmore

Growth

4794814806 August 2026 — 479 subscribers6 August 2026 — 479 subscribers13 August 2026 — 481 subscribers6 August 202613 August 2026
3 measurements spanning 7 days, net +2. 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 479–481 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 08:47481+2
6 Aug 2026, 19:01479no change
6 Aug 2026, 07:22479first reading

Engagement

19 posts held, back to 14 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.

ERR · 30 days
103.4%
avg views ÷ 481 subscribers
Avg views / post
497
6 posts measured
Reaction rate
7.88%
reactions ÷ views · ER floor
Posts in window
6
of 19 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 29 July 2026
Posts held19 (14 May 202629 July 2026)
Views total2,984
Reactions total235
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 19:01 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.

Reaction mix

846 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 45.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 537323096894342021238845.9%
custom 537282626706001952911313.4%
custom 537080353073713260110312.2%
custom 53710830815684939339811.6%
custom 5371023536141902128748.75%
custom 5370598007962083530708.27%

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

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

29 Jul 2026, 18:50 UTC220 views27 reactionsread 6 August 2026
Video

коротко о ТЛЕТЬ от автора морозного дайджеста. ЧИТАЕМ И ПОДДЕРЖИВАЕМ, ТОВАРИЩИ🖤

custom 537323096894342021215custom 53708035307371326015custom 53728262670600195294custom 53705980079620835302custom 53710235361419021281

29 Jul 2026, 16:32 UTC235 views29 reactionsread 6 August 2026
Photo

ФОТО ‼️ Предпоказ иммерсивной новеллы " Ю " в объективе MOONart. Культурный центр "СЕРДЦЕ" 11 ИЮЛЯ

custom 537323096894342021216custom 53708035307371326017custom 53705980079620835303custom 53710235361419021283

25 Jul 2026, 16:25 UTC433 views43 reactionsread 6 August 2026
Photo

ПРЕМЬЕРА КЛИПА, БРАТВА! тлеть в контакте 🔥 тлеть в трубе 🔥

custom 537323096894342021227custom 537102353614190212810custom 53728262670600195295custom 53710830815684939331

25 Jul 2026, 07:39 UTC981 views46 reactionsread 6 August 2026

КЛИП ВЕЧЕРОМ🩸🔨

custom 537323096894342021224custom 53705980079620835309custom 53708035307371326019custom 53710235361419021283custom 53710830815684939331

24 Jul 2026, 07:32 UTC579 views52 reactionsread 6 August 2026
Photo

Капитан Ненавидит Море - ТЛЕТЬ СЛУШАТЬ 🏴 Еще немного пасмурного панк-индастриала. лейбл издателя PLEASE STOP ME

custom 537323096894342021233custom 53708035307371326018custom 53728262670600195294custom 53710830815684939333custom 53705980079620835302custom 53710235361419021282

20 Jul 2026, 08:40 UTC536 views38 reactionsread 6 August 2026
Photo

БРАТВА, МЫ ЗАПУСКАЕМ ЕЩЕ ОДИН ИММЕРСИВНЫЙ МУВ! За более чем 10 лет существования проекта мы дали не мало интервью, как авторитетным, так и «нишевым» источникам. И вот, во времена всеобщего музыкального само-повтора, неуклюжей штамповки конъюнктурного контента, политической и духовной импотенции в музыкальной среде, выбора удобных тем и САМОИНТЕРВЬЮИРОВАНИЯ, мы решили поговорить напрямую и ответить на все интересующи

custom 537323096894342021218custom 53708035307371326018custom 53710830815684939336custom 53710235361419021284custom 53728262670600195292

13 Jul 2026, 08:12 UTC532 views39 reactionsread 6 August 2026
Photo

ПРЕСЕЙВ 🌊 «ТЛЕТЬ» - второй сингл с предстоящего лонгплея «Ядовитые Ягоды».

custom 537108308156849393316custom 537323096894342021212custom 53705980079620835305custom 53708035307371326014custom 53710235361419021281custom 53728262670600195291

12 Jul 2026, 14:21 UTC558 views63 reactionsread 6 August 2026
Photo

Братья и сестры, не без крови и горечи, но со светом и яростью, вместе с вами, плечом к плечу, мы живы…снова. 🖤🌊

custom 537108308156849393331custom 537282626706001952911custom 53708035307371326019custom 53732309689434202128custom 53710235361419021284

11 Jul 2026, 15:10 UTC503 views29 reactionsread 6 August 2026
Video message

Video message, posted without a caption

custom 537059800796208353010custom 53710235361419021289custom 53708035307371326016custom 53728262670600195292custom 53732309689434202122

10 Jul 2026, 07:33 UTC≈1,110 views29 reactionsread 6 August 2026
Photo

ЗАВТРА ЛЕЗВИЕ ПОПРОБУЕТ КРОВИ. двери 18:00 капитан 23:00

custom 537323096894342021219custom 53708035307371326016custom 53710235361419021282custom 53728262670600195292

6 Jul 2026, 09:04 UTC639 views31 reactionsread 6 August 2026
Photo

В СЕРДЦЕ..В ЭТУ СУББОТУ. БИЛЕТЫ 🎟️

custom 537323096894342021211custom 53708035307371326018custom 53710235361419021288custom 53710830815684939334

4 Jul 2026, 07:40 UTC≈1,060 views61 reactionsread 6 August 2026
Video

СИНГЛ УЛЕТЕЛ НА МОДЕРАЦИЮ, БРАТВА🖤

custom 537323096894342021234custom 537282626706001952912custom 53705980079620835308custom 53710235361419021284custom 53708035307371326013

Showing the 12 most recent of 19 posts we hold for @knmore. 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 — 139,774 of 1,176,251entries 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 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“капитан ненавидит море” (@knmore), 481 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/knmore.

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.