🩵🩵🩵🩵🩵🩵🩵🩵🩵🩵 У нас новый канал Мы решили начать всё заново и создать это место для нашей маленькой жизни 🐾 Здесь будет всё про Рича — прогулки, обучение, смешные моменты и просто наши будни 😘 Иногда будут и мои мысли, и что-то из повседневной жизни 🤩 Мы только начинаем, но будем стараться делать канал живым и интересным для вас. Спасибо каждому, кто с нами с самого начала 🥰 Дальше будет только интереснее.. Вот ссыло…

Channel
Будка_Рича
@budka_richa
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
43subscribers
-10 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 | -1003848038819 |
|---|---|
| Type | Channel |
| Username | @budka_richa |
| Created | Between 1 February 2026 and 28 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 9 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 9 October 2026 |
| On Telegram | t.me/budka_richa |
Topic
Personal blog — 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 29 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Oct 2026, 09:18 | 43 | -1 |
| 27 Sept 2026, 23:56 | 44 | -1 |
| 14 Sept 2026, 10:36 | 45 | -4 |
| 7 Sept 2026, 20:17 | 49 | -1 |
| 29 Aug 2026, 16:34 | 50 | -1 |
| 15 Aug 2026, 18:43 | 51 | -2 |
| 10 Aug 2026, 09:46 | 53 | no change |
| 7 Aug 2026, 19:08 | 53 | first reading |
Engagement
11 posts held, back to 28 May 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 11 posts for this entry, the most recent from 1 June 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 28s
- Average length
- 4s
Measured directly from 7 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
15 reactions across 4 posts, in 5 distinct kinds. The most used accounts for 40.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5287325017363737325 | 6 | 40.0% | |
| custom 5444927059879029029 | 3 | 20.0% | |
| custom 5445347343903777477 | 3 | 20.0% | |
| custom 5442873056194225015 | 2 | 13.3% | |
| custom 5273980584039827614 | 1 | 6.67% |
Custom emoji. Every 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 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 4 of the 11 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 15 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 11 most recent posts we hold, published 28 May 2026 to 1 June 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
К слову, Рич у нас без документов и родословный, на разведение кидать мы его не собираемся 💋 А ещё всех с 1 июня🥰👅
💙💙💙💙💙💙 – Надела на Рича намордник за долгое время и приятно удивилась, тому что он спокойно себя вёл в наморднике. Были моменты когда он пытался его снять, но быстро успокаивался и также за долгое время погуляли за двором, недолго, так как на улице было + 35°. Пока снимала кадры мимо нас прошла тётенька и попросила щенков от Рича, если мы будем его с кем-то вязать🤩–
custom 52873250173637373255custom 54453473439037774773custom 54449270598790290292custom 54428730561942250151
https://vt.tiktok.com/ZSx72BSkW/
Voice message, posted without a caption
Помните?
custom 52739805840398276141custom 54449270598790290291
Ну вот пару кадров, вчера приезжли родственники по этому была не актив
custom 52873250173637373251
📸 День 17 — самое смешное фото вашего питомца 😳🐾 Наверняка у каждого есть кадр, на котором питомец получился особенно забавным. Показывайте свои самые смешные и нелепые фотографии хвостиков в комментариях 💙
💙💙💙💙💙💙 – Пока гуляли рич спер тапок, а я на четыре написала огэ)– Когда у вас выпускной? ☺️
Новое видео в тт❤️ 💙Ссылка на видео💙 https://vt.tiktok.com/ZSxbrJeLk/
custom 54428730561942250151
💙💙💙💙💙💙 –У Рича Сегодня плюс три новые игрушки, это у нас два сдутый мячика и бутылка– Какая любимая игрушка У вашего питомца? 🥰
Showing the 11 most recent of 11 posts we hold for @budka_richa. 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
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 October 2026 — this entry's latest reading, not the date you are reading this.
“Будка_Рича” (@budka_richa), 43 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/budka_richa.
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.