Telegram RegisterThe public register of Telegram

Channel

О фуфлодемии без цензуры

@budilnik1

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

28subscribers

+0 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-1001617738157
TypeChannel
Username@budilnik1
Created1 December 2021measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/budilnik1

Growth

287 August 2026 — 28 subscribers11 August 2026 — 28 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. 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 27–29 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 05:4628no change
7 Aug 2026, 02:0928first reading

Engagement

18 posts held, back to 1 December 2021the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 1 December 2021. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Links
16

Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

1 Dec 2021, 23:02 UTC≈1,350 viewsread 11 August 2026

https://bastyon.com/post?s=8b3605ebcf3cb008c56a3f5771c33400b4376aa9e9ce06dfdcd33b40362b493c

1 Dec 2021, 23:01 UTC≈1,300 viewsread 11 August 2026

https://bastyon.com/post?s=0e7ce9d0a51db26e9e216fb7ba66a99dd14609a4d87f028d746747ca7614ea3a

1 Dec 2021, 23:00 UTC972 viewsread 11 August 2026

https://bastyon.com/post?s=4284952da30fbc6714ae3ca7a975ee8c28a1c3b9094f3d713ef2814379d09c3c

1 Dec 2021, 22:59 UTC718 viewsread 11 August 2026

https://zen.yandex.ru/video/watch/6071978e7760aa0c74c4a5a5

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

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

“О фуфлодемии без цензуры” (@budilnik1), 28 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/budilnik1.

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.