Telegram RegisterThe public register of Telegram
Telegram profile photo for lowlife bA$$ota

Channel

lowlife bA$$ota

@randomnyebukovy

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

145subscribers

-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-1002475134996
TypeChannel
Username@randomnyebukovy
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 31 August 2026
On Telegramt.me/randomnyebukovy

Growth

1451471467 August 2026 — 147 subscribers8 August 2026 — 147 subscribers15 August 2026 — 146 subscribers31 August 2026 — 145 subscribers7 August 202631 August 2026
4 measurements spanning 24 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 145–147 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Aug 2026, 15:27145-1
15 Aug 2026, 19:32146-1
8 Aug 2026, 20:45147no change
7 Aug 2026, 19:23147first reading

Engagement

18 posts held, back to 3 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
10s
Average length
10s

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

135 reactions across 17 posts, in 6 distinct kinds. The most used accounts for 51.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥7051.9%
custom 59924002790378090212417.8%
💔2317.0%
custom 597643987562319601085.93%
😈53.70%
🤡53.70%

Custom emoji. 2 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 17 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 135 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 3 July 2026 to 5 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

5 Aug 2026, 08:52 UTC93 views4 reactionsread 8 August 2026
Video message

Video message, posted without a caption

❤‍🔥4

2 Aug 2026, 12:35 UTC110 views10 reactionsread 8 August 2026

Голову не ебите

custom 59764398756231960107❤‍🔥3

2 Aug 2026, 12:35 UTC109 views17 reactionsread 8 August 2026
Video message

Video message, posted without a caption

custom 599240027903780902111❤‍🔥6

30 Jul 2026, 10:25 UTC138 views6 reactionsread 8 August 2026
Photo

Волк зиму переживет Но холод не забудет.

💔5custom 59924002790378090211

24 Jul 2026, 21:17 UTC180 views12 reactionsread 8 August 2026
Photo

Не имей 100 рублей а имей 100 друзей

❤‍🔥12

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

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

“lowlife bA$$ota” (@randomnyebukovy), 145 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/randomnyebukovy.

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.