Telegram RegisterThe public register of Telegram
Telegram profile photo for Брянск-север

Channel

Брянск-север

@bryansk_sewer

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

433subscribers

+2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002312413351
TypeChannel
Username@bryansk_sewer
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 14 September 2026
On Telegramt.me/bryansk_sewer

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 50% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

4294334317 August 2026 — 431 subscribers7 August 2026 — 431 subscribers22 August 2026 — 429 subscribers29 August 2026 — 430 subscribers14 September 2026 — 433 subscribers7 August 202614 September 2026
5 measurements spanning 38 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 428–434 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Sept 2026, 01:42433+3
29 Aug 2026, 18:07430+1
22 Aug 2026, 00:35429-2
7 Aug 2026, 22:52431no change
7 Aug 2026, 03:45431first reading

Engagement

18 posts held, back to 30 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

290 reactions across 18 posts, in 27 distinct kinds. The most used accounts for 22.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6422.1%
😁4916.9%
👏258.62%
🔥258.62%
custom 4954287528040465234196.55%
🙈144.83%
💯134.48%
🤯113.79%
82.76%
👀82.76%
😢82.76%
🕊72.41%
🤣72.41%
51.72%
👍51.72%
🦄51.72%
🙉31.03%
🫡31.03%
🤝20.69%
🥰20.69%
7 further kinds72.41%

Custom emoji. One 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 count beside it is 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 18 of the 18 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 290 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 30 July 2026 to 6 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
145
across the posts below
Posts paid on
15
of 18 we hold a reading for · 83%
Most on one post
12
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bryansk_sewer. 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 18 most recent posts we hold for this entry, published 30 July 2026 to 6 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

6 Aug 2026, 17:29 UTC132 views17 reactionsread 7 August 2026
Video message

Video message, posted without a caption

10👍3👏2💯1🔥1

6 Aug 2026, 17:27 UTC135 views11 reactionsread 7 August 2026
Video message

Video message, posted without a caption

6💯31👏1

6 Aug 2026, 17:24 UTC140 views15 reactions1 Starread 7 August 2026
Video message

Video message, posted without a caption

9💯41👏1

6 Aug 2026, 17:22 UTC141 views16 reactionsread 7 August 2026
Video message

Video message, posted without a caption

10💯3👏2🤝1

6 Aug 2026, 10:50 UTC201 views30 reactions10 Starsread 7 August 2026

Что за хуйню я только что прочитала....

😁13🤯73🤣3🥰2👍1custom 49542875280404652341

5 Aug 2026, 17:56 UTC248 views30 reactions12 Starsread 7 August 2026
Photo

Дорогие россияне, обращаю ваше внимание!

16🕊7👏31🏆1🦄1😁1

4 Aug 2026, 15:42 UTC240 views31 reactions10 Starsread 7 August 2026
Photo

Почему пишет она, а стыдно мне

😁15🙈8🤣4🙉3🤷‍♂1

4 Aug 2026, 15:09 UTC238 views17 reactions11 Starsread 7 August 2026
Photo

А сколько вкладок на работе открыто у вас?

👏9🤯411🌚1🤝1

3 Aug 2026, 10:21 UTC281 views13 reactions10 Starsread 7 August 2026
Video

Геленджик, налет дронов. 4ро погибших по предварительным данным Supernova+ пишет, что на втором видео - работа МОГ по беспилотнику, после чего он упал на пляж

😢8👀1💔1🔥1😭1🙈1

3 Aug 2026, 10:13 UTC261 views19 reactions11 Starsread 7 August 2026

Такие дела

12👏41🔥1🦄1

2 Aug 2026, 20:34 UTC284 views8 reactions10 Starsread 7 August 2026

И ещё подробности про взрыв в Москве. Я правда не очень понимаю, кто в итоге погиб. Муж в больнице или ещё какой-то человек прямо там. Напомню, официально в момент взрыва — трое погибших: смертница, охранник и "один из гостей". Может ещё позже сообщали о погибшем в больнице пострадавшем, я не видела, но и не вчитывалась сегодня

🫡3custom 49542875280404652343👀1👍1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

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

“Брянск-север” (@bryansk_sewer), 433 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/bryansk_sewer.

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.