Channel
@ncromancy
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
13subscribers
+0 since we began measuring on 31 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003433353161 |
|---|---|
| Type | Channel |
| Username | @ncromancy |
| Description | рисую и ною |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 31 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/ncromancy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Aug 2026, 05:15 | 13 | no change |
| 31 Aug 2026, 05:00 | 13 | first reading |
15 posts held, back to 15 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 15 posts for this entry, the most recent from 13 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 31 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.
Measured directly from 1 video 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.
100 reactions across 14 posts, in 5 distinct kinds. The most used accounts for 30.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5339240833986102414 | 30 | 30.0% | |
| custom 5221989850302942808 | 28 | 28.0% | |
| custom 5222191387348338969 | 17 | 17.0% | |
| custom 5222221022622681919 | 17 | 17.0% | |
| custom 5456359515496678874 | 8 | 8.00% |
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 15 of the 15 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 100 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 15 July 2026 to 13 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.
хедканон, саймон не выдержал депрессии и что бы полностью не отчаиваться решил попробовать новое хобби – в фурри сфере его очень быстро приняли прямо как во вторую семью, углубляясь, тот понял – то что он не хочет возвращаться к прошлой серой и скучной жизни; полной горя и несчастья
custom 52221913873483389694custom 52219898503029428082custom 53392408339861024142
Photo, posted without a caption
custom 52222210226226819193custom 53392408339861024142
Sticker, posted without a caption
пиздец вроде так хотелось рисовать но мало того сил рисовать у меня нету через неделю в колледж
custom 52219898503029428082custom 52222210226226819192
Photo, posted without a caption
custom 53392408339861024144custom 52219898503029428083custom 52222210226226819192
кстати совсем недавно перепрошел коф за 1,2 часа на концовку с Дэвидом, бля, какой же это ужас что б вы только знали 🌟 а ведь я еще наивно думал что хуже первой концовки бляьм не будет
custom 52219898503029428085custom 54563595154966788742
быстрый арт Саймона который мне не зашел от слова совсем 🌟 думаю лучше пока сфокусируюсь на скетчах нежели на полноценных артах
custom 52219898503029428084custom 52222210226226819192
Photo, posted without a caption
custom 52219898503029428084custom 52222210226226819192custom 54563595154966788742
нарисовал Софи в честь десять подпищеков 🌟 старательно учусь рендеру и освещению выходит довольно неплохо хоть и мне кажется что чего то не хватает
custom 52221913873483389694custom 53392408339861024142
Photo, posted without a caption
custom 52219898503029428083custom 53392408339861024143custom 54563595154966788742
рисовал смотря Заводной Апельсин, мне дико понравился этот фильм и скорее всего я буду его пересматривать 🌟 клянусь будет больше контента по фандомам и я перестану рисовать себя (нет) сказал бы я если бы в этом тгк было больше 6 человек 🌟
custom 52222210226226819194custom 53392408339861024143custom 52219898503029428082
Photo, posted without a caption
custom 53392408339861024146custom 52222210226226819192custom 54563595154966788742
Showing the 12 most recent of 15 posts we hold for @ncromancy. 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 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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“necromancer's cemetery” (@ncromancy), 13 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/ncromancy.
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.