23 Feb 2026, 11:34 UTC43 viewsread 12 August 2026
Саламчик, есть кто живой.. Го туда @viinelss
Channel
♱𝖭𝖤𝖵𝖤𝖱𝖭𝖨𝖦𝖧𝖳
@nevernightm
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
7subscribers
+0 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003551074331 |
|---|---|
| Type | Channel |
| Username | @nevernightm |
| Description | 𝐨𝐰𝐧𝐞𝐫: @v_komtrikru 𝐢𝐧𝐟𝐨: @infonevernightm |
| Created | 5 January 2026 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/nevernightm |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 19:17 | 7 | no change |
| 11 Aug 2026, 16:46 | 7 | first reading |
Engagement
6 posts held, back to 5 January 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 6 posts for this entry, the most recent from 23 February 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 1
- Videos
- 3
Lifetime counters from Telegram’s own channel header, read 12 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.
- Video runtime
- 2s
- Average length
- 1s
Measured directly from 3 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.
Reaction mix
22 reactions across 3 posts, in 4 distinct kinds. The most used accounts for 40.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5409076538362587556 | 9 | 40.9% | |
| custom 5411184512606431947 | 6 | 27.3% | |
| custom 5411241893369506252 | 5 | 22.7% | |
| custom 5411381973727864728 | 2 | 9.09% |
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 3 of the 6 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 22reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 6 most recent posts we hold, published 5 January 2026 to 23 February 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.
Recent posts
9 Jan 2026, 11:15 UTC106 views4 reactionsread 12 August 2026
Video
𝒏𝒆𝒘 𝒑𝒐𝒔𝒕 𝒇𝒓𝒐𝒎♱𝑵𝑬𝑽𝑬𝑹𝑵𝑰𝑮𝑯𝑻 𝑴𝒂𝒅𝒆𝒍𝒚𝒏 𝑪𝒍𝒊𝒏𝒆 𝒔𝒕𝒊𝒄𝒌𝒆𝒓𝒔 ♱ 32/1:1 𝒄𝒐𝒍𝒐𝒓 10
custom 54090765383625875562custom 54111845126064319471custom 54112418933695062521
8 Jan 2026, 07:37 UTC132 views9 reactionsread 12 August 2026
Video
𝒏𝒆𝒘 𝒑𝒐𝒔𝒕 𝒇𝒓𝒐𝒎♱𝑵𝑬𝑽𝑬𝑹𝑵𝑰𝑮𝑯𝑻 𝐸𝑙𝑖𝑧𝑎𝑏𝑒𝑡ℎ 𝑂𝑙𝑠𝑒𝑛 𝒔𝒕𝒊𝒄𝒌𝒆𝒓𝒔 ♱ 55/1:1 𝒄𝒐𝒍𝒐𝒓 10
custom 54090765383625875563custom 54111845126064319473custom 54112418933695062522custom 54113819737278647281
7 Jan 2026, 08:11 UTC177 views9 reactionsread 12 August 2026
Video
𝒏𝒆𝒘 𝒑𝒐𝒔𝒕 𝒇𝒓𝒐𝒎♱𝑵𝑬𝑽𝑬𝑹𝑵𝑰𝑮𝑯𝑻 𝐵𝑖𝑙𝑙𝑦 𝐴𝑙𝑖𝑠ℎ 𝒔𝒕𝒊𝒄𝒌𝒆𝒓𝒔 ♱ 36/1:1 𝒄𝒐𝒍𝒐𝒓 хз
custom 54090765383625875564custom 54111845126064319472custom 54112418933695062522custom 54113819737278647281
6 Jan 2026, 10:53 UTC110 viewsread 12 August 2026
Photo
♱• не принимаем к-поп фд ♱• делаем:стикеры, нарезки, ремини, аватарки ♱• обязательно укажите имя и фамилию (персонажа или селебрити), одну фотку с ним, фандом, формат и колор. колоры/рамки тут: @infonevernightm ♱• запросы выполняются по мере возможности ♱• если стоит реакция значит ваш запрос принят ♱• без подписки не выполняем
5 Jan 2026, 12:07 UTCviews —
Channel created
Showing the 6 most recent of 6 posts we hold for @nevernightm. 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
Citation-graph rank — 679,610 of 1,183,361entries 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.
Mentions
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.
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.
Cite this entry
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 August 2026 — this entry's latest reading, not the date you are reading this.
“♱𝖭𝖤𝖵𝖤𝖱𝖭𝖨𝖦𝖧𝖳” (@nevernightm), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/nevernightm.
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.