Встречаем милого Барри, ему 7 лет, с передержки. Надеемся на его скорейшее укотовление! 🙏
❤154custom 544533074815012950522custom 595170499575677306318custom 54271888664213761718

Channel
@murkosha
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
11,875subscribers
+157 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001076584253 |
|---|---|
| Type | Channel |
| Username | @murkosha |
| Created | 30 November 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 November 2026 |
| Measurements held | 63 |
| Confirmed unchanged | 1 time, most recently 14 November 2026 |
| On Telegram | t.me/murkosha |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 |
|---|---|---|
| 14 Nov 2026, 21:55 | 11,875 | -1 |
| 11 Nov 2026, 17:18 | 11,876 | +25 |
| 9 Nov 2026, 17:36 | 11,851 | +2 |
| 8 Nov 2026, 11:49 | 11,849 | +2 |
| 7 Nov 2026, 03:19 | 11,847 | +4 |
| 6 Nov 2026, 02:50 | 11,843 | +3 |
| 5 Nov 2026, 00:08 | 11,840 | +5 |
| 3 Nov 2026, 22:17 | 11,835 | -1 |
| 2 Nov 2026, 23:40 | 11,836 | -6 |
| 1 Nov 2026, 21:39 | 11,842 | +7 |
| 31 Oct 2026, 18:11 | 11,835 | -1 |
| 29 Oct 2026, 14:18 | 11,836 | +2 |
| 28 Oct 2026, 16:20 | 11,834 | -1 |
| 27 Oct 2026, 19:46 | 11,835 | +1 |
| 26 Oct 2026, 22:21 | 11,834 | -10 |
| 25 Oct 2026, 21:27 | 11,844 | -6 |
| 24 Oct 2026, 19:26 | 11,850 | -8 |
| 23 Oct 2026, 16:30 | 11,858 | +2 |
| 22 Oct 2026, 15:37 | 11,856 | +4 |
| 21 Oct 2026, 08:55 | 11,852 | first reading |
221 posts held, back to 6 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 71 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 221 (6 August 2026 – 14 November 2026) |
| Views total | 92,290 |
| Reactions total | 19,922 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 21:43 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 56 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.
55,184 reactions across 220 posts, in 18 distinct kinds. The most used accounts for 65.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 36,069 | 65.4% | |
| 🤣 | 3,627 | 6.57% | |
| 😁 | 2,034 | 3.69% | |
| custom 5445330748150129505 | 1,850 | 3.35% | |
| custom 5427188866421376171 | 1,703 | 3.09% | |
| custom 5208700242236546797 | 1,635 | 2.96% | |
| 🙏 | 1,399 | 2.54% | |
| 👏 | 1,372 | 2.49% | |
| custom 5391025250378986854 | 1,357 | 2.46% | |
| 💯 | 1,022 | 1.85% | |
| custom 5951704995756773063 | 949 | 1.72% | |
| custom 5273842895978251304 | 641 | 1.16% | |
| 😭 | 473 | 0.857% | |
| 🏆 | 304 | 0.551% | |
| custom 5208538167350667151 | 216 | 0.391% | |
| 👀 | 197 | 0.357% | |
| custom 5463289097336405244 | 178 | 0.323% | |
| custom 5208632291558958355 | 158 | 0.286% |
Custom emoji. 9 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 220 of the 221 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 55,184 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 221 most recent posts we hold, published 6 August 2026 to 14 November 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.
Telegram’s own ‘edited’ marker: 22 of 86 posts held from the last 30 days (25.6%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Встречаем милого Барри, ему 7 лет, с передержки. Надеемся на его скорейшее укотовление! 🙏
❤154custom 544533074815012950522custom 595170499575677306318custom 54271888664213761718
Карима, Флорса и Касабланка всегда на позитиве, чего и вам желают! Приезжайте за девчонками в приют, украсьте свою жизнь! 🧡 Фоточки от нашей Виктории — мягкое, безвозвратное очарование пушистой красотой. 🥰
❤161custom 544533074815012950528custom 520870024223654679722custom 542718886642137617114
Желаем крепкого здоровья, долголетия и всегда солнечного настроения Ларисе — администратору телеграм-канала и канала «Муркоши» в Дзен! 🎂
❤201custom 544533074815012950539custom 595170499575677306328custom 520863229155895835510
— Оп! И левитируем с Серканом в субботу, подкрадываясь к безделию, сериальчикам и празднику живота. 😄 Красивое.. 😌
🤣125custom 520853816735066715128💯26custom 544533074815012950524
Пришло время представить новеньких подопечных: 1. Вивьен, котику 1 год, уличный. 2. Питтипэт, 6 месяцев, уличная красавица. 3. Пипито, 6 месяцев, котик приехал с передержки. Пусть как можно скорее наладится их жизнь и они станут домашними и любимыми! 🏡
🙏124❤98custom 544533074815012950523custom 539102525037898685411
Та самая встреча за чашечкой кофе! Сервис "Моспитомец" на mos.ru и кондитерская Юлии Высоцкой "СладкоеСолёное" запустили акцию в поддержку питомцев из приютов! ⭐️ Сегодня удалось побывать там! Кондитерская располагается в башне "Федерация" Москва-Сити. Ну а наша Пружиночка теперь строит глазки всем покупателям, напоминая, что её можно и нужно забирать домой! 🥹 Сердечно благодарим за прекрасную возможность для прию…
❤96👏77🏆22custom 546328909733640524410
У нас в гостях побывала Анастасия — волонтёр, благодаря которой наши котики появляются на Авито и Моспитомце. Спасибо большое за твой труд и помощь мурлыкам! 🧡 Присоединяйтесь к нашей команде и вы! 🥰
❤146👏34🏆19custom 54632890973364052448
🥹 Знакомьтесь, Шубат! Да, уже не малыш — ему целых 7 лет. Жизнь не всегда была легкой, и кое‑что навсегда осталось в памяти… Но сейчас всё по‑другому: в приюте его окружают заботой. Шубат ласковый и спокойный кот. Любит сидеть на ручках и нежиться под ласковыми поглаживаниями. Хочет дарить свою любовь тому, кто станет для него самым родным человеком!
❤204custom 544533074815012950535custom 539102525037898685428custom 527384289597825130411
Пышная булочка Минори покидает нас, чтобы начать свою лучшую жизнь! 🎉 Желаем милашке и её хозяйке дружбы навек. 🤗
❤218custom 544533074815012950538custom 542718886642137617122custom 539102525037898685416
Так и представляется ситуация: прошло 4 года с момента отказа в приюте, человек жил свою жизнь, и тут попадается наш ролик в предложках. 😄 А вы не забыли оставить отзыв о наших котиках? 🥰
🤣95custom 595170499575677306330👀14custom 52085381673506671515
Как ощущается работа в пятницу, когда ты становишься хозяйкой положения и приближающегося безделья выходных. Аксинья задаёт ритм дня. 😌
❤173😁35custom 520870024223654679722💯8
Встречаем новеньких уличных парнишек: 1. Мицар, котёнок-подросточек, 7 месяцев. 2. Театрал, 2 года. Пусть им благоволит судьба! 🤗
❤212custom 539102525037898685433custom 546328909733640524411🏆5
Showing the 12 most recent of 221 posts we hold for @murkosha. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 3 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 14 November 2026 — this entry's latest reading, not the date you are reading this.
“Приют «Муркоша»” (@murkosha), 11,875 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/murkosha.
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.