💓
custom 534586836366079746417custom 539537232851320503316custom 518841250894737607013custom 52290392230755244732custom 51908311811254146511

Channel
@nutka_aaaa
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Cite this entry
70subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002247557548 |
|---|---|
| Type | Channel |
| Username | @nutka_aaaa |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 10 October 2026 |
| On Telegram | t.me/nutka_aaaa |
Other / unclassifiable — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 91% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 1 Oct 2026, 03:01 | 70 | -6 |
| 9 Aug 2026, 21:02 | 76 | no change |
| 7 Aug 2026, 17:36 | 76 | first reading |
8 posts held, back to 27 December 2025 — 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 8 posts for this entry, the most recent from 11 February 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
414 reactions across 7 posts, in 11 distinct kinds. The most used accounts for 18.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5345868363660797464 | 76 | 18.4% | |
| custom 5395372328513205033 | 66 | 15.9% | |
| custom 5246840333509098817 | 53 | 12.8% | |
| ❤ | 49 | 11.8% | |
| custom 5188412508947376070 | 45 | 10.9% | |
| custom 5294316747380265500 | 35 | 8.45% | |
| 🎄 | 30 | 7.25% | |
| 🎅 | 24 | 5.80% | |
| custom 5190831181125414651 | 23 | 5.56% | |
| custom 5229039223075524473 | 8 | 1.93% | |
| custom 5215367590553082661 | 5 | 1.21% |
Custom emoji. 8 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 7 of the 8 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 414 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 8 most recent posts we hold, published 27 December 2025 to 11 February 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nutka_aaaa. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 8 most recent posts we hold for this entry, published 27 December 2025 to 11 February 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
💓
custom 534586836366079746417custom 539537232851320503316custom 518841250894737607013custom 52290392230755244732custom 51908311811254146511
🫶❤️
🎅21custom 518841250894737607017custom 539537232851320503315custom 53458683636607974642❤1custom 52290392230755244731
до/после ❤️❤️❤️
custom 534586836366079746425custom 539537232851320503317custom 518841250894737607015❤3🎅1
🌟
custom 519083118112541465122custom 534586836366079746418custom 539537232851320503316🎄3❤1custom 52943167473802655001
nutaa pinned a photo
Photo, posted without a caption
❤23custom 524684033350909881714custom 534586836366079746414custom 52290392230755244733custom 52153675905530826612custom 52943167473802655001
с новым годом друзья ❤️❤️
🎄27custom 524684033350909881722custom 529431674738026550018🎅2custom 53953723285132050332
❤️❄️
❤21custom 524684033350909881717custom 529431674738026550015custom 52153675905530826613custom 52290392230755244732
Showing the 8 most recent of 8 posts we hold for @nutka_aaaa. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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 1 October 2026 — this entry's latest reading, not the date you are reading this.
“nutaa” (@nutka_aaaa), 70 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/nutka_aaaa.
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.