Channel
@nancyheheh3
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
271subscribers
-1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001720499678 |
|---|---|
| Type | Channel |
| Username | @nancyheheh3 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/nancyheheh3 |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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 |
|---|---|---|
| 12 Sept 2026, 05:36 | 271 | -3 |
| 3 Sept 2026, 00:13 | 274 | -2 |
| 25 Aug 2026, 22:55 | 276 | +1 |
| 18 Aug 2026, 19:03 | 275 | +3 |
| 10 Aug 2026, 08:45 | 272 | no change |
| 10 Aug 2026, 08:31 | 272 | first reading |
7 posts held, back to 29 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 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 2 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.
190 reactions across 7 posts, in 8 distinct kinds. The most used accounts for 21.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5341434419813056748 | 41 | 21.6% | |
| custom 5334795843482449705 | 35 | 18.4% | |
| custom 5258499653594275994 | 34 | 17.9% | |
| custom 5397750194206972586 | 27 | 14.2% | |
| custom 5215289211694884153 | 25 | 13.2% | |
| custom 5397993740327490784 | 18 | 9.47% | |
| custom 5228697081685769585 | 7 | 3.68% | |
| custom 5472016196003990754 | 3 | 1.58% |
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 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 190 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 29 July 2026 to 9 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @nancyheheh3. 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 7 most recent posts we hold for this entry, published 29 July 2026 to 9 August 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.
chat. chat!
custom 533479584348244970512custom 52152892116948841539custom 53977501942069725865custom 52286970816857695851custom 52584996535942759941custom 53414344198130567481custom 53979937403274907841
Signed нэnсу
😆
custom 534143441981305674810custom 53979937403274907848custom 53347958434824497055custom 52584996535942759943custom 52152892116948841531custom 52286970816857695851custom 53977501942069725861
Signed нэnсу
а я ещё я убегала от мишки сегодня.. эх, жестко было
custom 53414344198130567489custom 53977501942069725865custom 52584996535942759944custom 53347958434824497054custom 54720161960039907541
Signed нэnсу
🌟🌟🌟🌟🌟🌟
custom 533479584348244970510custom 53414344198130567488custom 53977501942069725864custom 52584996535942759942custom 53979937403274907842custom 52152892116948841531custom 52286970816857695851
Signed нэnсу
запускаем тренд снимать кавера на мыльницу 😯
custom 525849965359427599410custom 53414344198130567486custom 53977501942069725866custom 53979937403274907842custom 53347958434824497051
Signed нэnсу
Video message, posted without a caption
custom 525849965359427599413custom 53414344198130567486custom 53977501942069725865
Signed нэnсу
👅
custom 521528921169488415314custom 53979937403274907845custom 52286970816857695854custom 53347958434824497053custom 54720161960039907542custom 52584996535942759941custom 53414344198130567481custom 53977501942069725861
Signed нэnсу
Showing the 7 most recent of 7 posts we hold for @nancyheheh3. 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.
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 1 registered channel — 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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“ɴᴀɴᴄʏ|月亮 🪷” (@nancyheheh3), 271 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/nancyheheh3.
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.