Channel
@NoiBuonMangTenAnh
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
21subscribers
+1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002367005972 |
|---|---|
| Type | Channel |
| Username | @NoiBuonMangTenAnh |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 15 September 2026 |
| On Telegram | t.me/NoiBuonMangTenAnh |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 23:18 | 21 | +1 |
| 11 Aug 2026, 16:16 | 20 | no change |
| 10 Aug 2026, 05:01 | 20 | first reading |
20 posts held, back to 13 August 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 20 posts for this entry, the most recent from 8 April 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 14 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.
15 reactions across 8 posts, in 10 distinct kinds. The most used accounts for 20.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6231177985131549277 | 3 | 20.0% | |
| 🤡 | 3 | 20.0% | |
| custom 6068914777818665658 | 2 | 13.3% | |
| custom 5240297307315921185 | 1 | 6.67% | |
| custom 5269233975162853023 | 1 | 6.67% | |
| custom 5269490182846960033 | 1 | 6.67% | |
| custom 6242516045957960999 | 1 | 6.67% | |
| custom 6294041304024224084 | 1 | 6.67% | |
| ❤ | 1 | 6.67% | |
| 💩 | 1 | 6.67% |
Custom emoji. 7 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 8 of the 20 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 15 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 13 August 2025 to 8 April 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.
我希望的生活是这样的：清晨有阳光和你，傍晚有晚霞和你，余生每一个平凡的日子，都有你。 Cuộc sống mà tôi mong muốn là thế này: buổi sáng có ánh nắng và có em, buổi chiều có hoàng hôn và có em, mỗi ngày bình thường của quãng đời còn lại, đều có em ở bên.
Signed Ka 🍬
“Chấp niệm” có phải: 错过了日出 我就等你看日落 Nếu lỡ mất bình minh, ta sẽ đợi người cùng ngắm hoàng hôn 错过了雪花 我就等你看雪落 Nếu lỡ mất hoa tuyết, ta sẽ đợi người cùng ngắm tuyết rơi 没赶上花开 我就等你看花落 Không kịp mùa hoa nở, thì ta đợi người đến khi hoa tàn 没赶上今生 我就等轮回 Không kịp kiếp này, vậy ta đợi người cho đến kiếp luân hồi
Signed Nekyo
如果平淡的就能避开猛烈的悲伤和痛苦 我愿意做一个淡淡的人 Nếu một cuộc sống bình dị có thể giúp tôi tránh khỏi nỗi buồn và đau khổ tột cùng, tôi thà là một người sống an nhiên tự tại.
Signed Nekyo
Tình yêu đẹp không phải là tìm được một người khiến thế giới hoàn hảo, mà là yêu họ bất chấp thế giới không hoàn hảo.
Signed Nekyo
多时候我们都鼓励自己说我们要做最真实的自己，但很多时候最真实的那个自己，往往是你最放肆，你也最瞧不起的那个自己。 Chúng ta thường tự nhắc nhở bản thân phải sống đúng với con người thật của mình , nhưng rất nhiều lúc, cái phiên bản chân thật nhất của chúng ta lại là một con người càn rỡ, láo xược, đến chính chúng ta cũng xem thường.
Signed Nekyo
"Đời này kiếp này, ta chưa từng hối hận, nhưng nếu có thể được một lần làm lại. Ta không bao giờ muốn yêu chàng nữa" “我这辈子从未后悔过什么，但如果可以重来一次，我绝不会再爱上他。”
Signed Nekyo
人生没有地图，只有行走的脚步绘制出的痕迹。🫶 Cuộc đời không có bản đồ,chỉ có những dấu vết được vẽ nên từ bước chân đang đi.
💩1
Signed 𝑯𝒚𝒆𝒓𝒊𝒏 ⋆ 𐙚 .
🫶Mặt trời luôn cô đơn, nhưng vẫn toả sáng đấy thôi. Bạn cũng vậy, một mình cũng ổn mà..🫶
Signed Techin
“Hai thế giới khác, người khác người”
🤡2❤1
“做我们自己吧,因为在风雨来袭时,只有我 们自己能够成为自己最坚实的依靠。” 🥀 Cứ là mình thôi, vì đơn giản chỉ có mình mới có thể trở thành chỗ dựa vững chắc cho bản thân những lúc bão giông. 🎀
Signed tung tung tung sahur
“既然你已经不期待了,那我翻山越岭就没有 意义。" "Vì em không còn mong đợi nó nữa, nên dù anh có trèo đèo lội suối cũng không có ý nghĩa gì."🖤
Signed tung tung tung sahur
“列车已经离站了,无论你追得多远, 耳边只剩下渐远的汽笛声。” Chuyển tàu đã rời ga, dù em có chạy theo bao xa, cũng chỉ còn tiếng còi vọng lại.
🤡1
Signed tung tung tung sahur
Showing the 12 most recent of 20 posts we hold for @NoiBuonMangTenAnh. 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.
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Nỗi Buồn Không Tên ❤️🩹” (@NoiBuonMangTenAnh), 21 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/NoiBuonMangTenAnh.
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.