Channel
@hanlissse
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
120subscribers
+46 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003973711776 |
|---|---|
| Type | Channel |
| Usernames | @hanlissse @phamhann11 |
| Created | Between 1 April 2026 and 7 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 2 times, most recently 11 November 2026 |
| On Telegram | t.me/hanlissse |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 18 October 2026 and assigned it the closest of 31 fixed categories, at 99% 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, 17:57 | 120 | -1 |
| 10 Nov 2026, 00:22 | 121 | no change |
| 9 Nov 2026, 23:47 | 121 | +120 |
| 14 Oct 2026, 02:36 | 1 | -102 |
| 2 Sept 2026, 00:35 | 103 | +10 |
| 25 Aug 2026, 04:27 | 93 | +14 |
| 18 Aug 2026, 09:11 | 79 | +5 |
| 11 Aug 2026, 23:00 | 74 | no change |
| 11 Aug 2026, 22:51 | 74 | first reading |
31 posts held, back to 7 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 2 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. It is computed over the 13 of 19 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 9 November 2026 |
|---|---|
| Posts held | 31 (7 August 2026 – 9 November 2026) |
| Views total | 2,016 |
| Reactions total | 267 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Nov 2026, 00:22 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.
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.
495 reactions across 25 posts, in 7 distinct kinds. The most used accounts for 19.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5267295510393288499 | 98 | 19.8% | |
| custom 5413605040210343911 | 94 | 19.0% | |
| custom 5294129426676619649 | 86 | 17.4% | |
| custom 5294291943944131710 | 83 | 16.8% | |
| custom 5256169689670777654 | 59 | 11.9% | |
| custom 5454386897147152043 | 51 | 10.3% | |
| custom 5249083036582060176 | 24 | 4.85% |
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 25 of the 31 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 495 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 7 August 2026 to 9 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: 3 of 19 posts held from the last 30 days (15.8%) 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).
🤩 join us ive: rei & gaeul, wonyoung 🤩 ryujin ( itzy ) 🐰 megan ( katseye ) 🐰 asa ( babymonster ) ❤️ ningning ( aespa ) 🤩 hanbyeol ( do0t project ) 🤩blackpink : rosé, jennie, jisoo, lisa 🤩 yeri ( red velvet ) 🤩 unchild 🤩 hanni ( newjeans )
custom 52941294266766196499
⋆.ೃ࿔*:･
custom 52672955103932884998custom 52941294266766196492custom 52942919439441317102
ребята как ваша учеба?
custom 52672955103932884999
дружеское напоминание слушать дитто и омг каждый день
custom 529412942667661964912custom 52942919439441317107custom 52672955103932884993
ханни с австралийским певцом newjeans never die 🐰
custom 529412942667661964913custom 52672955103932884997custom 52942919439441317106
ханни и дани вместе на благотворительном забеге miracle365 который помогает больным деткам 🫥
custom 529412942667661964912custom 52942919439441317107custom 52672955103932884995
🫥прочитайте все. и после этого кто-то будет говорить, что все у них было нормально с контрактами и в компании?
custom 529429194394413171011custom 52941294266766196496custom 52672955103932884994
⠀ ⣀⣀⣠⣀⣀⠀⠀⠀⠀⠀⠀⠀⣀⣀⣤⣀⣀⡀⠀ ⠋⠀⠀⠀⠀⠀⠉⠲⣄⠀ ⢀⠔⠋⠁⠀⠀⠀⠀⠉⡆ ⢑⠖⠂⠀⢀⠔⠒⢢⠘⣦⠏⡴⠒⠲⡄⠀⠀⠲⡚⠁ ⠀⠈⠒⢲⠀⢸⡀⠓⠊⣠⠋⢆⠙⠚⢀⡇⠀⡖⠖⠁⠀ ⠀⠀⠀⠀⠉⠉⠈⠉⠉⠀⠀⠀⠉⠉⠁⠈⠉⠁
custom 529412942667661964917custom 52942919439441317108custom 52672955103932884997
у меня сегодня день рождения буду рада если напишите мне поздравления @hanlissebot
custom 529429194394413171015custom 52672955103932884994
28.09.26 ˚˖𓍢ִ໋🍧✧
custom 526729551039328849915custom 52941294266766196496custom 52942919439441317106
𝚑𝚊𝚗𝚕𝚒𝚜𝚜𝚎 𝚒𝚜 𝚢𝚘𝚞𝚛 𝚌𝚘𝚣𝚢 𝚑𝚒𝚍𝚎𝚊𝚠𝚊𝚢 𝚏𝚘𝚛 𝚊𝚕𝚕 𝚝𝚑𝚒𝚗𝚐𝚜 𝚑𝚊𝚗𝚗𝚒 ⁺˖ 𝚒𝚗𝚏𝚙 ⁺˖ 𝟶𝟼𝟷𝟶𝟶𝟺 ⁺˖ 𝚠𝚊𝚜 𝚋𝚘𝚛𝚗 𝚒𝚗 𝙼𝚎𝚕𝚋𝚘𝚞𝚛𝚗𝚎 𝚌𝚘𝚘𝚙 𝚊𝚗𝚘𝚗 𝚋𝚘𝚘𝚜𝚝 𝚊𝚛𝚑𝚒𝚟𝚎
custom 526729551039328849918custom 52942919439441317106custom 52941294266766196495
princess hanni
custom 526729551039328849915
Showing the 12 most recent of 31 posts we hold for @hanlissse. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 12 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.
“hanlisse” (@hanlissse), 120 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/hanlissse.
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.