Telegram RegisterThe public register of Telegram

Channel

ЗАКРЫТ. |@ :; 𝑩𝑼𝑹𝑰𝑲 ⌗𝑷𝑹𝑻𝑭. . .

@PortfBurik

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

14subscribers

+0 since we began measuring on 12 August 2026

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

Register entry

Telegram ID-1002481813194
TypeChannel
Username@PortfBurik
DescriptionЗдᴩᴀʙᴄᴛʙуйᴛᴇ!! Я - Буᴩиᴋ, нᴀчинᴀющий диɜᴀйнᴇᴩ бᴀннᴇᴩᴏʙ. Эᴛᴏ ʍᴏᴇ ᴨᴏᴩᴛɸᴏᴧиᴏ!! Дᴧя ɜᴀᴋᴀɜᴀ ᴨиᴄᴀᴛь - @BurikPRbot 𝗦𝗧𝗔𝗥𝗧: 09.10.24
CreatedBetween 1 September 2024 and 17 November 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded12 August 2026
Last confirmed live12 August 2026
Measurements held2
On Telegramt.me/PortfBurik

Growth

1412 Aug 2026, 14:49 — 14 subscribers12 Aug 2026, 15:01 — 14 subscribers12 Aug 2026, 14:4912 Aug 2026, 15:01
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 13–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 15:0114no change
12 Aug 2026, 14:4914first reading

Engagement

17 posts held, back to 17 November 2024the 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 17 posts for this entry, the most recent from 4 December 2024. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
132
Links
48

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

192 reactions across 15 posts, in 22 distinct kinds. The most used accounts for 16.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52696513128400302203216.7%
🕊2110.9%
❤‍🔥168.33%
custom 5233325759350713577157.81%
custom 5235463622271970666157.81%
custom 5269766456618262840147.29%
custom 5266961684060184497105.21%
💋105.21%
custom 523597412208477235994.69%
custom 584804211177711661594.69%
🍓94.69%
custom 523581041511131796373.65%
custom 530309796693070093463.13%
💯63.13%
custom 530319286423310429852.60%
custom 526952447816081390621.04%
custom 523369120093806219710.521%
custom 523586211363267204910.521%
custom 535296488658436799710.521%
🍌10.521%
2 further kinds21.04%

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

Measured over the 17 most recent posts we hold, published 17 November 2024 to 4 December 2024, 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
5
across the posts below
Posts paid on
1
of 15 we hold a reading for · 7%
Most on one post
5
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @PortfBurik. 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 17 most recent posts we hold for this entry, published 17 November 2024 to 4 December 2024. 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

4 Dec 2024, 12:15 UTC399 views2 reactionsread 12 August 2026

А чо вы тут делаете

💋2

Signed ⌯𝑩𝑼𝑹𝑰𝑲 |✧| ⌗𝙀𝙉𝙁𝙋 ⌗𝗛𝗘𝗬

23 Nov 2024, 06:31 UTC≈1,130 views41 reactionsread 12 August 2026

Всем здорова народ, всему когда-то да наступает конец? Я выгорел к этому делу, возможно вы даже могли заметить на количество актива на канале с моей стороны. Мне очень жаль, ребята. Отныне этот канал закрывается, хотелось бы выразить благодарность админам, подписчикам, заказчикам и союзам. Спасибо, что были с нами, простите. Союзы разрываю.😠

🕊13custom 523332575935071357711custom 52354636222719706669custom 52359741220847723595custom 52697664566182628402💘1

Signed ⌯𝑩𝑼𝑹𝑰𝑲 |✧| ⌗𝙀𝙉𝙁𝙋 ⌗𝗛𝗘𝗬

23 Nov 2024, 06:31 UTCviews —

Channel name was changed to «ЗАКРЫТ. |@ :; 𝑩𝑼𝑹𝑰𝑲 ⌗𝑷𝑹𝑻𝑭. . .»

22 Nov 2024, 18:19 UTC523 views17 reactionsread 12 August 2026
Photo

дрынь дрынь раи не умрерла, и дала вам работку из коллаба🍰🍰 #RAI #BANNERS

🍓6💯6🕊3custom 52696513128400302202

Signed 𓂃꩜раичка!¡(˶˃ ᵕ ˂˶)

20 Nov 2024, 13:15 UTC425 views15 reactionsread 12 August 2026
Photo

ЯИКТО

💋5custom 52669616840601844974❤‍🔥3custom 52359741220847723593

Signed ⌯𝑩𝑼𝑹𝑰𝑲 |✧| ⌗𝙀𝙉𝙁𝙋 ⌗𝗛𝗘𝗬

20 Nov 2024, 05:08 UTC317 views1 reactionsread 12 August 2026

разрыв с @HEARTLESS_port , @PortfBurik причина: не отметились на чистке.

❤‍🔥1

Signed ⌯𝑩𝑼𝑹𝑰𝑲 |✧| ⌗𝙀𝙉𝙁𝙋 ⌗𝗛𝗘𝗬

19 Nov 2024, 13:38 UTC286 views8 reactionsread 12 August 2026

4>>>>50 #репост

🕊2custom 52696513128400302202custom 52354636222719706661custom 52697664566182628401custom 53031928642331042981custom 58480421117771166151

Signed ⌯𝑩𝑼𝑹𝑰𝑲 |✧| ⌗𝙀𝙉𝙁𝙋 ⌗𝗛𝗘𝗬

19 Nov 2024, 13:37 UTC283 views7 reactionsread 12 August 2026

3>>>70 #репост

custom 52358104151113179632custom 52696513128400302202custom 52669616840601844971custom 52697664566182628401custom 58480421117771166151

Signed ⌯𝑩𝑼𝑹𝑰𝑲 |✧| ⌗𝙀𝙉𝙁𝙋 ⌗𝗛𝗘𝗬

19 Nov 2024, 08:22 UTC276 views8 reactionsread 12 August 2026

5>>90 🙏🏻 #репост

custom 52354636222719706662custom 53030979669307009342custom 52358104151113179631custom 52696513128400302201custom 52697664566182628401custom 58480421117771166151

Signed ⌯𝑩𝑼𝑹𝑰𝑲 |✧| ⌗𝙀𝙉𝙁𝙋 ⌗𝗛𝗘𝗬

19 Nov 2024, 04:31 UTC265 views8 reactionsread 12 August 2026

2>>>95; 7>>>100😭 #репост

custom 52696513128400302203❤‍🔥1custom 52333257593507135771custom 52358104151113179631custom 52697664566182628401custom 58480421117771166151

Signed ⌯𝑩𝑼𝑹𝑰𝑲 |✧| ⌗𝙀𝙉𝙁𝙋 ⌗𝗛𝗘𝗬

19 Nov 2024, 04:31 UTC421 views8 reactionsread 12 August 2026

4>>130 #репост

custom 52333257593507135772custom 52354636222719706662custom 52696513128400302202custom 52358104151113179631custom 53031928642331042981

Signed ⌯𝑩𝑼𝑹𝑰𝑲 |✧| ⌗𝙀𝙉𝙁𝙋 ⌗𝗛𝗘𝗬

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

Mentions

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.

“ЗАКРЫТ. |@ :; 𝑩𝑼𝑹𝑰𝑲 ⌗𝑷𝑹𝑻𝑭. . .” (@PortfBurik), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/PortfBurik.

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.