Telegram RegisterThe public register of Telegram
Telegram profile photo for Брудні Реальності Уоі Дослівно

Channel

Брудні Реальності Уоі Дослівно

@BRUOID

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

110subscribers

+16 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-1004402271938
TypeChannel
Username@BRUOID
CreatedBetween 1 June 2026 and 29 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/BRUOID

Growth

941121039 August 2026 — 94 subscribers9 August 2026 — 94 subscribers17 August 2026 — 111 subscribers25 August 2026 — 109 subscribers31 August 2026 — 112 subscribers9 September 2026 — 110 subscribers1109 August 20269 September 2026
6 measurements spanning 32 days, net +16. 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 91–115 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 20:56110-2
31 Aug 2026, 22:08112+3
25 Aug 2026, 03:33109-2
17 Aug 2026, 12:49111+17
9 Aug 2026, 12:4794no change
9 Aug 2026, 02:0094first reading

Engagement

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

What this channel posts

Video runtime
32s
Average length
11s

Measured directly from 3 videos 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

148 reactions across 9 posts, in 20 distinct kinds. The most used accounts for 12.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 52582535906229346361912.8%
custom 5357537970192661526149.46%
custom 5357540521403245265149.46%
custom 5332557869168486566138.78%
custom 5357071717132939693138.78%
custom 5357127740686349192138.78%
custom 526021115511207080296.08%
custom 526028148949650529296.08%
custom 535749600836218159485.41%
custom 525837539589544673374.73%
🤷74.73%
custom 533250227940677360642.70%
👻42.70%
💅42.70%
👀32.03%
custom 535716314410178491621.35%
💘21.35%
🕊10.676%
🗿10.676%
🦄10.676%

Custom emoji. 12 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 9 of the 20 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 148 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 29 July 2026 to 8 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

8 Aug 2026, 21:56 UTC74 views10 reactionsread 9 August 2026
Poll

Подкаст. вже. в. дорозі.

  1. 7-107%
  2. 12-1435%
  3. 16-1830%
  4. 20-2213%
  5. 24-266%
  6. 28-302%
  7. 30+7%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

custom 53325578691684865664custom 53574960083621815943custom 53575379701926615263

5 Aug 2026, 21:30 UTC118 views9 reactionsread 9 August 2026

🔤// Вітаю підписників нашого каналу! Ми відкрили анонімку де ви можете пропонувати ідеї для подкастів, писати що покращити, та навіть можете поділитися своїм досвідом в уоі!! 💕Писати сюди: https://t.me/IncogNoteBot?start=bkpk9705na

custom 53575379701926615263💅1🦄1custom 53325578691684865661custom 53571277406863491921custom 53571631441017849161custom 53574960083621815941

4 Aug 2026, 14:00 UTC162 views43 reactionsread 9 August 2026
Video

14.08 🤩Premiere

custom 535707171713293969312custom 53571277406863491929custom 53575405214032452657custom 53325022794067736064💅2💘2custom 53325578691684865662custom 53574960083621815942

4 Aug 2026, 13:39 UTC145 views31 reactionsread 9 August 2026
Video

17:00

custom 53575405214032452657custom 53325578691684865666custom 53575379701926615266custom 52582535906229346363custom 52602814894965052922custom 53571277406863491922custom 53574960083621815942👻1

4 Aug 2026, 11:25 UTCviews —8 reactionsread 9 August 2026

Posted without readable text

🤷5custom 52582535906229346363

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

8 Aug 2026, 21:56 UTCAnonymous Quiz54 voters

Подкаст. вже. в. дорозі.

  1. 7-107%
  2. 12-1435%
  3. 16-1830%
  4. 20-2213%
  5. 24-266%
  6. 28-302%
  7. 30+7%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 29 July 2026 to 8 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Forward network

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 4 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.

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

“Брудні Реальності Уоі Дослівно” (@BRUOID), 110 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/BRUOID.

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.