Telegram RegisterThe public register of Telegram

Channel

🥷🏻Корпус заказных убийств⚔

@berzhkap

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

34subscribers

+0 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001931882088
TypeChannel
Username@berzhkap
DescriptionШут - бог, кто не согласен - лох
CreatedBetween 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/berzhkap

Growth

349 Aug 2026, 16:02 — 34 subscribers11 Aug 2026, 00:46 — 34 subscribers9 Aug 2026, 16:0211 Aug 2026, 00:46
2 measurements spanning 1 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 33–35 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 00:4634no change
9 Aug 2026, 16:0234first reading

Engagement

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

What this channel posts

Photos
3,440
Videos
327
Links
162

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

Reaction mix

45 reactions across 11 posts, in 12 distinct kinds. The most used accounts for 20.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥920.0%
🕊613.3%
custom 5280688536977187669511.1%
custom 5368621528436973317511.1%
custom 528300324088188794848.89%
custom 531433320624006725036.67%
custom 597209800298935562636.67%
36.67%
😢36.67%
custom 524924289955977479624.44%
custom 536830326277040490112.22%
custom 536884663196792489912.22%

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

Measured over the 15 most recent posts we hold, published 11 May 2026 to 10 June 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 Jun 2026, 19:56 UTC43 views12 reactionsread 11 August 2026
Photo

Вибач, сонечко, що не зберегла тебе. Вибач, що мене не було поряд. Вибач, що не встигла приїхати вчасно. Вибач, що не закрила те трикляте вікно. Дякую, що була зі мною ці чудові 4 роки, вони були найкращими. Дякую, що була поряд, коли я тікала з дому, коли вешталась з місця на місце. Дякую, що довіряла мені, і вибач, що я не виправдала тієї довіри. Я буду пам'ятати тебе завжди

custom 52806885369771876695custom 52830032408818879484custom 53143332062400672503

Signed 𝒯𝒽ℯ ℒ𝒾𝓉𝓉𝓁ℯ ℱℴ𝓍

29 May 2026, 14:36 UTC51 views6 reactionsread 11 August 2026
Photo

Деякий час я не буду вести цей канал, не губіть. 18 квітня 2023 року я створила його для Бєржки, на її день народження, щоб викладати сюди її фото. Юз каналу це її ім'я, і нікнейм перший час також був на честь неї. Потім, поступово, цей канал став про моє життя, але вона завжди була і буде його частиною, тож основний контент був з її фото. Вчора, 28 травня 2026 року, її не стало і я поки не знаю, як це пережити. Ви б

🕊6

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

27 May 2026, 09:23 UTC51 views3 reactionsread 11 August 2026

Где ЗП сюки

1custom 52492428995597747961custom 59720980029893556261

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

26 May 2026, 19:34 UTC48 views3 reactionsread 11 August 2026
Photo

Сами вы омежки. Может я тут альфа самка, а вы меня омежкой сделать хотите

custom 53686215284369733173

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

26 May 2026, 11:10 UTC48 views1 reactionsread 11 August 2026

Все ще хочу

❤‍🔥1

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

24 May 2026, 18:01 UTC36 views5 reactionsread 11 August 2026

Тяжко жити хочу вмерти

😢3custom 52492428995597747961custom 53688466319679248991

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

21 May 2026, 15:07 UTC41 views2 reactionsread 11 August 2026

Тяжко жити шкода вмерти

1custom 59720980029893556261

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

17 May 2026, 15:46 UTC51 views4 reactionsread 11 August 2026
Photo

Кушає бусінка 🥰🥰

❤‍🔥2custom 53683032627704049011custom 59720980029893556261

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

13 May 2026, 17:38 UTC41 viewsread 11 August 2026
Forwarded from @h_saggPhoto

📲 Ежедневный гороскоп в МАХ

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

13 May 2026, 17:38 UTC30 viewsread 11 August 2026

В моих отношениях не хватает, собственно, второй половинки 🤨

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

12 May 2026, 17:17 UTC33 views5 reactionsread 11 August 2026
Photo

Мне никогда это не надоест

❤‍🔥2custom 536862152843697331721

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

12 May 2026, 09:29 UTC30 viewsread 11 August 2026

Мне кушац нечего

Signed 𝔖𝔥𝔞𝔡𝔬𝔴 𝔒𝔣 𝔄𝔫𝔲𝔟𝔦𝔰 🐾 ᵀᴮᶠ

Showing the 12 most recent of 15 posts we hold for @berzhkap. 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 — 1,060,200 of 1,169,250entries 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 2 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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“🥷🏻Корпус заказных убийств⚔” (@berzhkap), 34 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/berzhkap.

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.