Telegram RegisterThe public register of Telegram
Telegram profile photo for Борщ

Channel

Борщ

@borsch_333

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

181subscribers

+19 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1002502643760
TypeChannel
Username@borsch_333
CreatedBetween 1 February 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live2 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/borsch_333

Growth

162181171.510 August 2026 — 162 subscribers11 August 2026 — 162 subscribers18 August 2026 — 167 subscribers26 August 2026 — 177 subscribers2 September 2026 — 181 subscribers10 August 20262 September 2026
5 measurements spanning 22 days, net +19. 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 159–184 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Sept 2026, 02:52181+4
26 Aug 2026, 01:04177+10
18 Aug 2026, 12:37167+5
11 Aug 2026, 10:19162no change
10 Aug 2026, 16:01162first reading

Engagement

13 posts held, back to 6 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
20.4%
avg views ÷ 181 subscribers
Avg views / post
37.0
1 post measured
Reaction rate
48.6%
reactions ÷ views · ER floor
Posts in window
1
of 13 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 10 August 2026
Posts held13 (6 July 202610 August 2026)
Views total37
Reactions total18
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken10 Aug 2026, 16: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.

What this channel posts

Video runtime
12s
Average length
12s

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

378 reactions across 13 posts, in 12 distinct kinds. The most used accounts for 24.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 54426806459543247449324.6%
custom 54427721115778608898723.0%
custom 54113795685461708314712.4%
4511.9%
custom 5411499273579678431338.73%
custom 5411520877265176419225.82%
❤‍🔥164.23%
custom 5283276155988773824133.44%
💊92.38%
custom 546529811553375918971.85%
custom 528277282018141910451.32%
💋10.265%

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 are Telegram’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 13 of the 13 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 378 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

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

Recent posts

10 Aug 2026, 09:17 UTC37 views18 reactionsread 10 August 2026
Photo

*:..。₊‧°𐐪♡𐑂°‧₊*゚¨゚゚ Ленивая перерисовка старого арта 😋 Сам арт кину в комментарии #арт

💊96❤‍🔥2💋1

6 Aug 2026, 13:49 UTC75 views17 reactionsread 10 August 2026
Photo

🤍🤍🤍🤍🤍 Рисую опять Агату После этого рисунка хочу что-то нарисовать по zzz мээ 🦭 #спойлер

custom 54114992735796784319custom 54427721115778608894custom 541137956854617083121custom 54115208772651764191

4 Aug 2026, 16:40 UTC73 views22 reactionsread 10 August 2026
Video

😀😀😀😀😀😀😀😀 Давно не делал всякие видео.. Говно какое-то ну ладна 🤩 #видео

custom 54114992735796784319custom 54427721115778608896custom 544268064595432474452

29 Jul 2026, 15:29 UTC195 views38 reactionsread 10 August 2026
Photo

💙💙💙💙💙💙💙💙 💙💙💙💙💙💙💙💙 💙💙💙💙💙💙💙💙 💙💙💙💙💙💙💙💙 Артик для @yyulkarip 🦭 #арт

custom 544268064595432474414❤‍🔥10custom 541137956854617083174custom 54115208772651764191custom 54427721115778608891custom 54652981155337591891

29 Jul 2026, 13:45 UTC100 views20 reactionsread 10 August 2026
Photo

🤩🤩🤩 Рисую для юлкии 🤩 #спойлер

custom 54426806459543247449custom 54115208772651764196custom 541149927357967843132

25 Jul 2026, 14:25 UTC124 views32 reactionsread 10 August 2026
Photo

😀😀😀😀😀😀😀😀 Девочкт 🤩🤩🤩 #спойлер

custom 544277211157786088914custom 54426806459543247448custom 54113795685461708314custom 541152087726517641932custom 54114992735796784311

23 Jul 2026, 12:20 UTC118 views23 reactionsread 10 August 2026
Photo

🤍🤍🤍🤍🤍 Скетчи по доки доки 💕 #скетч #спойлер

11custom 54115208772651764195custom 54427721115778608895custom 54113795685461708311custom 54652981155337591891

22 Jul 2026, 12:04 UTC106 views24 reactionsread 10 August 2026
Photo

🤍🤍🤍 Чикенбубре Не спрашивайте.... 🦭 Спасибо за 161 подписчикккк 🦭 #скетч

custom 544277211157786088910custom 54113795685461708316custom 544268064595432474461custom 52832761559887738241

17 Jul 2026, 19:23 UTC204 views44 reactionsread 10 August 2026
Photo

🌸🌸🌸🌸🌸🌸🌸🌸🌸 Закончил прекрасную даму 😢 Буду благодарен репостам хихи #арт

custom 541137956854617083121custom 54426806459543247449custom 541149927357967843172custom 54427721115778608892❤‍🔥1custom 52832761559887738241custom 54115208772651764191

16 Jul 2026, 15:02 UTC164 views30 reactionsread 10 August 2026
Photo

😀😀😀😀😀😀😀😀 Рисую блин 💨 #спойлер

custom 544268064595432474413custom 54427721115778608897custom 541152087726517641952❤‍🔥1custom 52832761559887738241custom 54113795685461708311

11 Jul 2026, 16:14 UTC195 views37 reactionsread 10 August 2026
Photo

🤍🤍🤍🤍🤍🤍🤍🤍 Ой блин 🦭 #спойлер

custom 544268064595432474415custom 52832761559887738248custom 528277282018141910453custom 54427721115778608892custom 54652981155337591892❤‍🔥1custom 54114992735796784311

8 Jul 2026, 16:49 UTC200 views43 reactionsread 10 August 2026
Photo

🪷🎀🎀🎀🩷🎀🎀🪷 Купается 😍 #арт

custom 544277211157786088920custom 544268064595432474497custom 54114992735796784313custom 54652981155337591892❤‍🔥1custom 52832761559887738241

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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

“Борщ” (@borsch_333), 181 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/borsch_333.

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.