Telegram RegisterThe public register of Telegram
Telegram profile photo for Няшные хотелки

Channel

Няшные хотелки

@nyahotelki

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

192subscribers

+6 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-1002207217266
TypeChannel
Username@nyahotelki
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live18 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/nyahotelki

Topic

Ecommerce storefront — 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 24 September 2026 and assigned it the closest of 31 fixed categories, at 30% 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

1861921897 August 2026 — 186 subscribers8 August 2026 — 186 subscribers25 August 2026 — 189 subscribers2 September 2026 — 191 subscribers10 September 2026 — 190 subscribers18 September 2026 — 192 subscribers7 August 202618 September 2026
6 measurements spanning 41 days, net +6. 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 185–193 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Sept 2026, 08:57192+2
10 Sept 2026, 13:20190-1
2 Sept 2026, 04:04191+2
25 Aug 2026, 03:42189+3
8 Aug 2026, 12:16186no change
7 Aug 2026, 22:26186first reading

Engagement

7 posts held, back to 1 July 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 7 posts for this entry, the most recent from 21 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

38 reactions across 7 posts, in 5 distinct kinds. The most used accounts for 28.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1128.9%
💘1026.3%
🤩1026.3%
🤔513.2%
🤯25.26%

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 7 of the 7 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 38 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 1 July 2026 to 21 July 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

21 Jul 2026, 20:08 UTC440 views8 reactionsread 8 August 2026
Photo

🚬 Уж не думала, что попрошу чекап в подарок, ахахах 🚬 В последнее время вопрос состояния моего организма стал особенно важным, так что решила пройти чекап организма чтобы чуть-чуть успокоиться! 35000 💕💕💕💕💕💕💕💕💕💕💕 Лс тг

🤔5🤯2💘1

21 Jul 2026, 20:07 UTC431 views4 reactionsread 8 August 2026
Photo

😒 Подарочные игрули в стим! 😒 Elden Ring - 5000 The last of us - 3900 The Quarry - 3400 Skyrim - 1700 Silent Hill 2 - 1300 Fallout 3 - 1200 Far Cry 3 - 900 Cofee talk - 700 This is the Police - 500 💕💕💕💕💕💕💕💕💕💕💕 Лс тг

🔥2💘1🤩1

21 Jul 2026, 20:07 UTC410 views4 reactionsread 8 August 2026
Photo

🌟 Подарочки на др 🌟 Ну просто фешн образы, конечно! Юбочка + футболочка 🥺 Няшни Чоколла - 6000 Эминем и Онидзука - 6500 💕💕💕💕💕💕💕💕💕💕💕 Лс тг

🔥2💘1🤩1

21 Jul 2026, 18:59 UTC393 views5 reactionsread 8 August 2026
Photo

☺️ Подарочки на др ☺️ Выбрала самые качественные варианты косплеев! Рамиэль из ZZZ - 20000 Райден из Genshin Impact - 15000 💕💕💕💕💕💕💕💕💕💕💕 Лс тг

🤩3💘1🔥1

4 Jul 2026, 17:45 UTC862 views7 reactionsread 8 August 2026
Photo

Маникюр и педикюр :з Это уже на следующий месяц! 8000 Оплативший получит фоточки и видосик с результатом до и после, а также 3 сетика фото на заказ^^ 💕💕💕💕💕💕💕💕💕💕💕 Лс тг

💘3🔥2🤩2

1 Jul 2026, 18:36 UTC840 views5 reactionsread 8 August 2026
Photo

Вы знаете зачем она… 2000 Оплативший получит персональный видос с приседанием на эту игрушку (на прозрачном стуле, да) 💕💕💕💕💕💕💕💕💕💕💕 Лс тг

🔥2🤩2💘1

1 Jul 2026, 18:34 UTC742 views5 reactionsread 8 August 2026
Photo

Я так хочу больше подобных кофточек! 2500 Оплатившему распаковочка и сетик фоточек^^ 💕💕💕💕💕💕💕💕💕💕💕 Лс тг

💘2🔥2🤩1

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

Named by 2 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.

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

“Няшные хотелки” (@nyahotelki), 192 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/nyahotelki.

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.