Video message, posted without a caption
😁28custom 521092827799618783021custom 52876567262779284928❤4

Channel
@brodyagisevera
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
2,596subscribers
-21 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001728485897 |
|---|---|
| Type | Channel |
| Username | @brodyagisevera |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 2 times, most recently 5 November 2026 |
| On Telegram | t.me/brodyagisevera |
Memes & entertainment — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Nov 2026, 08:27 | 2,596 | +1 |
| 27 Oct 2026, 11:47 | 2,595 | +2 |
| 24 Oct 2026, 04:59 | 2,593 | +3 |
| 21 Oct 2026, 10:07 | 2,590 | +1 |
| 15 Oct 2026, 10:36 | 2,589 | -1 |
| 6 Oct 2026, 02:17 | 2,590 | -4 |
| 28 Sept 2026, 18:14 | 2,594 | -10 |
| 19 Sept 2026, 00:16 | 2,604 | -3 |
| 14 Sept 2026, 05:18 | 2,607 | +1 |
| 5 Sept 2026, 07:00 | 2,606 | +4 |
| 1 Sept 2026, 21:26 | 2,602 | -1 |
| 30 Aug 2026, 03:29 | 2,603 | -6 |
| 27 Aug 2026, 09:42 | 2,609 | -3 |
| 24 Aug 2026, 14:04 | 2,612 | -3 |
| 20 Aug 2026, 13:52 | 2,615 | -1 |
| 17 Aug 2026, 10:03 | 2,616 | -1 |
| 14 Aug 2026, 03:05 | 2,617 | -2 |
| 11 Aug 2026, 06:33 | 2,619 | +1 |
| 7 Aug 2026, 21:22 | 2,618 | +1 |
| 7 Aug 2026, 14:03 | 2,617 | first reading |
8 posts held, back to 2 August 2026 — the 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 8 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
1,187 reactions across 8 posts, in 14 distinct kinds. The most used accounts for 27.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 326 | 27.5% | |
| 😁 | 291 | 24.5% | |
| ❤ | 226 | 19.0% | |
| 🥰 | 106 | 8.93% | |
| 🔥 | 88 | 7.41% | |
| custom 5210928277996187830 | 50 | 4.21% | |
| ❤🔥 | 27 | 2.27% | |
| custom 5287656726277928492 | 21 | 1.77% | |
| custom 5408880430155836385 | 12 | 1.01% | |
| custom 5258072862694060532 | 11 | 0.927% | |
| 🤪 | 10 | 0.842% | |
| 😍 | 9 | 0.758% | |
| custom 5211212381492884111 | 6 | 0.505% | |
| custom 5246742889291068566 | 4 | 0.337% |
Custom emoji. 6 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 8 of the 8 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 1,187 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 2 August 2026 to 7 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.
Video message, posted without a caption
😁28custom 521092827799618783021custom 52876567262779284928❤4
Полагаю, что все собачники и кошатники утешают себя тем, что говно - это к деньгам. Ну а как еще? Но правда денег владельцы большого количества собак почему-то не наблюдают. Но это, видимо, такой замкнутый финансовый цикл. Говно - к деньгам. Собаки - к тому, чтобы эти деньги немедленно заканчивались. Поэтому баланс во Вселенной соблюден идеально. Новое «к деньгам в этот раз ну может быть точно» принес на себе Оникс…
❤81🤣60custom 521092827799618783020custom 52467428892910685664❤🔥1
Ладно. Я решила что эту кошку-обосрешку тоже надо показать 🤣🤣🤣
🤣122❤34😁20🤪10❤🔥2
Video message, posted without a caption
🔥57🤣53custom 528765672627792849213😍9❤7
Кошки-гавношки 🤣🤣🤣 Благо их я щас в ведре помою, как приеду. А Оникса на днях пришлось полоскать в озере, где я грозилась утопить эту волосатую и говняную муму.
🤣88❤32❤🔥14🥰8
Смешнее всех в нашей стае злится Нюша Она зачем-то высовывает язык 🤣
🥰84😁74🔥31❤12❤🔥5
Алясковое недоумение 😆 Вышла после течки в стаю, а там ничего не изменилось 😆 #Баечка_и_КО
😁127❤48custom 540888043015583638512custom 52112123814928841116❤🔥5
Video message, posted without a caption
😁42🥰14custom 525807286269406053211custom 52109282779961878309❤8🤣3
Showing the 8 most recent of 8 posts we hold for @brodyagisevera. 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.
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.
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 November 2026 — this entry's latest reading, not the date you are reading this.
“Бродяги Севера” (@brodyagisevera), 2,596 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/brodyagisevera.
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.