спасибо большое за стримовое! хорошо, что я перезапустила 🐶 очень славно поигрались! хорошего вам вееечера и замечательных снов ^~^
custom 6309933353034327173132custom 630986215106649338425custom 534372867537845278911custom 53415494605120710193

Channel
@nyamuras
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry
8,113subscribers
-363 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001218684956 |
|---|---|
| Type | Channel |
| Username | @nyamuras |
| Description | hii! я Няма. я стримлю. это все ๑•◡<๑ ₍ ᐢ..ᐢ ₎ 📍https://itsnyamuras.carrd.co/ ࣪ . › |
| Created | Between 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/nyamuras |
Gaming — 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 87% 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 |
|---|---|---|
| 10 Nov 2026, 18:08 | 8,113 | -9 |
| 7 Nov 2026, 13:26 | 8,122 | -22 |
| 4 Nov 2026, 20:38 | 8,144 | -18 |
| 2 Nov 2026, 00:36 | 8,162 | -9 |
| 30 Oct 2026, 07:56 | 8,171 | -20 |
| 27 Oct 2026, 05:36 | 8,191 | -7 |
| 24 Oct 2026, 11:40 | 8,198 | -12 |
| 21 Oct 2026, 11:31 | 8,210 | -4 |
| 18 Oct 2026, 07:31 | 8,214 | -27 |
| 15 Oct 2026, 03:27 | 8,241 | +26 |
| 11 Oct 2026, 18:38 | 8,215 | +34 |
| 5 Oct 2026, 09:16 | 8,181 | -31 |
| 27 Sept 2026, 08:01 | 8,212 | -46 |
| 17 Sept 2026, 18:21 | 8,258 | -39 |
| 13 Sept 2026, 16:57 | 8,297 | -35 |
| 9 Sept 2026, 12:41 | 8,332 | -26 |
| 3 Sept 2026, 20:20 | 8,358 | -24 |
| 31 Aug 2026, 20:43 | 8,382 | -34 |
| 28 Aug 2026, 20:12 | 8,416 | -12 |
| 26 Aug 2026, 03:58 | 8,428 | first reading |
112 posts held, back to 5 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 49 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 11 November 2026 |
|---|---|
| Posts held | 112 (5 August 2026 – 11 November 2026) |
| Views total | 148,060 |
| Reactions total | 10,432 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Nov 2026, 02:52 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.
Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
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.
29,820 reactions across 112 posts, in 10 distinct kinds. The most used accounts for 30.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5417984115850911853 | 9,126 | 30.6% | |
| custom 6309933353034327173 | 5,776 | 19.4% | |
| custom 5418227898194632124 | 5,120 | 17.2% | |
| custom 5321135102997051142 | 2,900 | 9.73% | |
| custom 6309862151066493384 | 2,728 | 9.15% | |
| custom 5418295221806999590 | 1,422 | 4.77% | |
| custom 5343728675378452789 | 1,053 | 3.53% | |
| custom 5424614578988283060 | 820 | 2.75% | |
| custom 5341549460512071019 | 447 | 1.50% | |
| custom 5344006074431197828 | 428 | 1.44% |
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 112 of the 112 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 29,820 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 112 most recent posts we hold, published 5 August 2026 to 11 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: 6 of 43 posts held from the last 30 days (14.0%) 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).
спасибо большое за стримовое! хорошо, что я перезапустила 🐶 очень славно поигрались! хорошего вам вееечера и замечательных снов ^~^
custom 6309933353034327173132custom 630986215106649338425custom 534372867537845278911custom 53415494605120710193
включили, щас вернусь 🍮 но если вырубят ещё раз, то пойду отдыхать
custom 6309933353034327173114custom 534372867537845278921custom 630986215106649338411custom 53415494605120710193
сори, у меня вырубили свет 🍥
custom 6309933353034327173113custom 630986215106649338421custom 534154946051207101916custom 53437286753784527895
приветь-приветь! напоминаю, что сегодня в 14:00 стримс. поболтаем, а потом пойдем смотреть ремейк ШРЕКА 🍮
custom 6309933353034327173124custom 630986215106649338421custom 534372867537845278917custom 53415494605120710193
это невероятно, но на бусти + контент 🐶 на ютубчике выйдет на выходных! большое спасибо тем, кто продолжал поддерживать меня на бусти во время затишья, вы лучшие!!!! надеюсь, что скоро восстановлюсь и будет больше контента ✨
custom 6309862151066493384176custom 534400607443119782830custom 534372867537845278914custom 63099333530343271736custom 53415494605120710193
У уважаемого АлонДеВульфа сегодня день рождения 🥰
custom 6309933353034327173215custom 630986215106649338435custom 534372867537845278918custom 53440060744311978287
Спасииибо большое за стримс, было весело 🥰 Хорошего вам вечера и доброй ночи! ✨
custom 6309933353034327173187custom 630986215106649338438custom 534154946051207101915custom 53437286753784527895custom 53440060744311978285
расписание⭐️ на этой неделе расслабончик, тк возможно на следующей будет кукинг.. 💬пн в 14:00 - стримс; 💬ср в 14:00 - шрековая коллаба; 💬пт в 14:00 - фильмовый аук; 💬вс в 14:00 - стримс 🐶 ✨ • twitch.tv/nyamuras
custom 6309933353034327173136custom 630986215106649338426custom 534372867537845278917
Только что поняла, что вообще-то я могу опубликовать свои любимые места в телеге 🍮 Итак! Я обожаю свою гирлянду в комнате, часть которой я засунула в картонную звезду и потому она очень красиво светится через отверстия 🍮 очень вайбик! Мне нравится, как Хорнет и Полый лезут на мой холодильник! Конечно, как и вы, рабочее место - одна из самых любимых вещей 🍮 Люблю свои полочки с книгами и фигурками, надеюсь, что в …
custom 6309933353034327173230custom 534154946051207101929custom 534400607443119782816custom 63098621510664933845
☆*: артик для Нямуры :*☆ буду рада активу и репостам ( ˘͈ ᵕ ˘͈♡)
custom 6309862151066493384189custom 630993335303432717380custom 534400607443119782823custom 53415494605120710193custom 53437286753784527893
буськи, напоминаю про стримс в 14:00 и про ивент, который на нём будет! не забудьте скинуть фотки, кто хотел!
custom 6309933353034327173127custom 630986215106649338427custom 534372867537845278917
у вас есть что-то из песен, на чем вы словили недавно гиперфикс? летс го топ-1 трек за последнее время 🤩 вот моё 🤩
custom 6309933353034327173170custom 630986215106649338434custom 534372867537845278920
Showing the 12 most recent of 112 posts we hold for @nyamuras. 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.
@nyamuras edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
We recorded 9 posts on @nyamuras as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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 19 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.
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“nyamura's space 🍂” (@nyamuras), 8,113 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/nyamuras.
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.