Channel
@NNEVLIFE
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
118subscribers
-1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002367786603 |
|---|---|
| Type | Channel |
| Username | @NNEVLIFE |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 2 times, most recently 9 September 2026 |
| On Telegram | t.me/NNEVLIFE |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 18:24 | 118 | -4 |
| 25 Aug 2026, 04:15 | 122 | +1 |
| 17 Aug 2026, 09:27 | 121 | +1 |
| 9 Aug 2026, 18:42 | 120 | +1 |
| 9 Aug 2026, 04:31 | 119 | no change |
| 9 Aug 2026, 01:16 | 119 | first reading |
16 posts held, back to 17 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 16 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
72 reactions across 6 posts, in 8 distinct kinds. The most used accounts for 30.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5249329773863258630 | 22 | 30.6% | |
| custom 5204026196832042406 | 12 | 16.7% | |
| custom 5312520618372008492 | 12 | 16.7% | |
| custom 5291938001218204544 | 10 | 13.9% | |
| custom 5314430332630485327 | 8 | 11.1% | |
| custom 5404822321716289240 | 6 | 8.33% | |
| custom 5364334974981931871 | 1 | 1.39% | |
| custom 5388849681939842723 | 1 | 1.39% |
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 6 of the 16 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 72 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 17 July 2026 to 8 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.
ズの🎵 #oneshot 🤩 #minje & #keiju ⊹ "тайный ингредиент" минджэ ненавидит свою работу в киоске с мороженым - духота, липкие руки и бесконечные клиенты сводят с ума. но однажды в его жизни появляется кейджу - парень, который приходит каждый день и просит солёную карамель с лавандой. этого вкуса нет в меню, и сначала минджэ это выводит из себя, но постепенно он замечает, что все больше ждет этих встреч. и …
Signed #гав
hyunlix au 🍃 🤩 Хёнджин и Феликс — женатая пара, находящаяся в счастливом браке почти пять лет. у них есть совместная компания бренда косметики, в которой они оба работают. Хёнджин — предприниматель, а Феликс — модель. в этой семье появляется ребёнок из-за чего Феликсу вынужденно приходится уйти с работы. ⭐ после рождения ребёнка их жизнь начинает резко меняться. 🔤 вместе с ребёнком приходят бессонные ночи, постоя…
Signed #гав
давайте хотя бы 10 человек 🤩🤩🤩
Signed #гав
Sticker, posted without a caption
Signed #гав
🎉 Итоги за июль для @nnevlife 📊 35 постов 👁 2.5K просмотров ❤️ 203 реакций Карточка создана в @CreatiqBot
custom 52040261968320424062
Signed #гав
Sticker, posted without a caption
Signed #гав
пока в ресте кину вам интерактивчик 🤩🤩
custom 53144303326304853271
Signed #гав
Sticker, posted without a caption
Signed #гав
🔤🔤🔤🔤🔤🔤🔤🔤🔤🔤 вы как🔤 🔤персонаж лбиск 🤩 🔤 странная песня 🤩 🔤майнкрафтер 🤤 с вас🔤 🔤рк 🤩 🔤подписка 🤩 🔤+ в комм от своего лица (не канала) 🤗 🔤🔤🔤
custom 53144303326304853277custom 52919380012182045445custom 52493297738632586304custom 53643349749819318711custom 54048223217162892401
Signed #гав
Sticker, posted without a caption
Signed #гав
ухожу в небольшой рест, совсем ненадолго. вп продолжу выпускать 😊
custom 52493297738632586307custom 52040261968320424061custom 53888496819398427231
Signed #гав
Sticker, posted without a caption
Signed #гав
Showing the 12 most recent of 16 posts we hold for @NNEVLIFE. 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.
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 6 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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“光がない║ 。writer's failure. 〟、” (@NNEVLIFE), 118 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/NNEVLIFE.
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.