Channel
@niaamhhh
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
95subscribers
+0 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002603631175 |
|---|---|
| Type | Channel |
| Username | @niaamhhh |
| Description | рисовальщица и жена Вила подробнее в инфопосте!! art cr: @sivalizsizuzi https://boosty.to/niamhsi |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/niaamhhh |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Aug 2026, 12:45 | 95 | no change |
| 9 Aug 2026, 05:15 | 95 | first reading |
12 posts held, back to 11 June 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 pageof 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 2 August 2026 |
|---|---|
| Posts held | 12 (11 June 2026 – 2 August 2026) |
| Views total | 221 |
| Reactions total | 109 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 9 Aug 2026, 12:45 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 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
429 reactions across 12 posts, in 38 distinct kinds. The most used accounts for 7.93% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5451715749611606789 | 34 | 7.93% | |
| custom 5282735930707315796 | 30 | 6.99% | |
| custom 5264730847981901257 | 24 | 5.59% | |
| custom 5382221387760950768 | 24 | 5.59% | |
| custom 5316877214153720577 | 22 | 5.13% | |
| custom 5433980326407841341 | 19 | 4.43% | |
| custom 5393493808602187621 | 18 | 4.20% | |
| custom 5447180186837618862 | 18 | 4.20% | |
| custom 5364261067184707450 | 17 | 3.96% | |
| custom 5332524080660777573 | 16 | 3.73% | |
| custom 5305720190493824784 | 14 | 3.26% | |
| custom 5375364846135034018 | 14 | 3.26% | |
| custom 5190867641102779065 | 13 | 3.03% | |
| custom 5265259756024531425 | 11 | 2.56% | |
| custom 5444894787494750345 | 11 | 2.56% | |
| custom 5451711360155033691 | 11 | 2.56% | |
| custom 5222246886915738658 | 10 | 2.33% | |
| custom 5314506044314002549 | 10 | 2.33% | |
| custom 5413419497623158035 | 10 | 2.33% | |
| custom 5429392313493242588 | 10 | 2.33% | |
| 18 further kinds | 93 | 21.7% |
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 areTelegram’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 12 of the 12 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 429reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 11 June 2026 to 2 August 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.
вот это другое дело😁
custom 533252408066077757316custom 526525975602453142511custom 544718018683761886211custom 52647308479819012574custom 52469944541155502202custom 53324162340319802902
🤍·.༄࿔ девочки для @niamhsi и @viperxie !!
custom 54450193114815902987custom 54223380659327874375custom 52832513138979339313
ко мне приехала большая королева 😏 ради него пришлось реорганизовать алтарь вхвх очень рада его приезду☺️ прям мечта сбылась
custom 545171574961160678922custom 54518023103824929809custom 54518411712465866359custom 54517736242959253725custom 54517840997211654503
Интерактив с @niamhsi ! Спасибо большое что предложила этот трейдик, так здорово придумывать и видеть взаимодействия наших персонажей 🥹❤️
custom 54339803264078413417custom 54448947874947503455custom 54449389440535202842
внезапный трейдик с Лоттей :3
custom 543398032640784134112custom 54449389440535202848custom 54448947874947503456
накопилос всякое🐈 возможно что-то из этого закончу
custom 537536484613503401814custom 542939231349324258810custom 593615738164898075910
обновлённый реф увии!! и первые несколько аутфитов готовлюсь к поступлению в вуз (опять), тяжело....
custom 526473084798190125720custom 538222138776095076813custom 528273593070731579611custom 53034141323582919494custom 51908676411027790651
випка🤤 хочу немного обновить референс Ю (нынешнему уже почти год оказывается...о_о), заодно порисовать ей разных нарядиков из-за жары хочется лентяйствовать капец
custom 528273593070731579619custom 519086764110277906512custom 538222138776095076811
наткнулась на открытку в этом стиле к 5й годовщине и не сдержалась вхвх кстати хочу поблагодарить вас всех за поздравления под прошлым постом😳 мне очень приятно правда
custom 530572019049382478414custom 531450604431400254910custom 52513085511958947747custom 52851986649548481812
😋
custom 531687721415372057722custom 522224688691573865810custom 541341949762315803510
🌟🌟 🩷🩷 🌟🌟
custom 536426106718470745017custom 52200903881313836039custom 54471801868376188627custom 52670116431198009932custom 52469944541155502201custom 52805049700749496711custom 52832513138979339311custom 53683690745543153771
хвастаюс коммишкой от Ауры!!🥺 и бонус!!
custom 539349380860218762118custom 545171574961160678912custom 545171136015503369111
Showing the 12 most recent of 12 posts we hold for @niaamhhh. 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.
Citation-graph rank — 265,598 of 1,568,528entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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 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.
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 9 August 2026 — this entry's latest reading, not the date you are reading this.
“няму” (@niaamhhh), 95 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/niaamhhh.
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.