Telegram RegisterThe public register of Telegram

Channel

мегарест 𝜗ৎ ネイエル

@neielvamp

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

138subscribers

+0 since we began measuring on 9 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002038770650
TypeChannel
Username@neielvamp
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live10 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/neielvamp

Growth

1389 Aug 2026, 14:16 — 138 subscribers10 Aug 2026, 00:47 — 138 subscribers9 Aug 2026, 14:1610 Aug 2026, 00:47
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 137–139 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 00:47138no change
9 Aug 2026, 14:16138first reading

Engagement

20 posts held, back to 31 March 2026the 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.

ERR · 30 days
122.1%
avg views ÷ 138 subscribers
Avg views / post
169
4 posts measured
Reaction rate
21.5%
reactions ÷ views · ER floor
Posts in window
5
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held20 (31 March 20269 August 2026)
Views total674
Reactions total145
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 14:16 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.

What this channel posts

Video runtime
4m 39s
Average length
20s

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.

Reaction mix

813 reactions across 18 posts, in 23 distinct kinds. The most used accounts for 12.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 519507172259585252810012.3%
custom 53300236451903313149111.2%
custom 52877191622175339398910.9%
custom 53302391795341444578210.1%
custom 5244530646126198217698.49%
custom 5350297999656368956658.00%
556.77%
custom 5427278605468073398526.40%
❤‍🔥303.69%
🎉293.57%
🆒242.95%
💘242.95%
custom 5253863171973727578202.46%
custom 5350527544183501431202.46%
🕊192.34%
custom 5357428177943697427182.21%
custom 520631086173549019780.984%
💯70.861%
custom 520655377220085158430.369%
💅30.369%
3 further kinds50.615%

Custom emoji. 12 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 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 18 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 813reactions 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 31 March 2026 to 9 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.

Telegram Stars

Stars received
141
across the posts below
Posts paid on
9
of 19 we hold a reading for · 47%
Most on one post
37
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @neielvamp. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 31 March 2026 to 9 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

9 Aug 2026, 11:00 UTC43 views28 reactions4 Starsread 9 August 2026
Video

🌟❤️🤍 #BANDORI 🥹 #EDIT 🌟🤩🤩 ﹫mindy 🌟🤩🤩 ﹫miwra 🌟😻😻 ﹫kiona 🌟😻😻 ﹫seva 🌟🤩🤩 ﹫neiel 🌟😻😻 ﹫ksai 🌟🌟 🌟🤩🤩 ﹫vivy 🌟😻😻 ﹫jules

custom 524453064612619821711💯7custom 52877191622175339396💘4

26 Jul 2026, 09:35 UTC133 views37 reactionsread 9 August 2026

на такой веселой ноте хочу сказать: я ухожу в очень длительный рест. я ,конечно, не ухожу насовсем, но моих новых работ в ближайший год не будет. можете отписываться, можете оставаться — желание ваше. увидимся через год, если не больше 😮‍💨

custom 519507172259585252820custom 528771916221753393911custom 54272786054680733984custom 52445306461261982172

26 Jul 2026, 09:29 UTC152 views34 reactionsread 9 August 2026
Video

🌟🕊🤍 #OTHERS 🥹 #EDIT song : «Love Is A Shield — Camouflage» 🌟🌟🌟🌟🌟🌟: «for rellsan ! »

custom 524453064612619821712custom 519507172259585252811custom 52877191622175339399custom 54272786054680733982

20 Jul 2026, 06:11 UTC346 views46 reactions2 Starsread 9 August 2026
Video

🌟☦🤍 #MILGRAM 🥹 #EDIT song : «シニタイちゃん (feat. IA)» 🌟🌟🌟🌟: «for kaemi ! »

custom 524453064612619821717custom 519507172259585252812custom 542727860546807339810custom 52877191622175339397

6 Jul 2026, 22:19 UTC408 views56 reactionsread 9 August 2026
Video

🌟🤩🤍 #PJSEKAI 🥹 #EDIT song : «Symphonia IX (My Wait Is U)» 🌟: «happy bday jules ! »

custom 528771916221753393926custom 542727860546807339814custom 519507172259585252813custom 52445306461261982173

6 Jul 2026, 19:00 UTC361 views47 reactionsread 9 August 2026
Video

🌟💌🤍 #OURNOTES 🥹 #EDIT song : «Birds Dont Sing — TV Girl» 🌟🌟: «happy bday kifa ! ❤️»

custom 524453064612619821720custom 519507172259585252814custom 528771916221753393910custom 54272786054680733983

2 Jul 2026, 05:43 UTC363 views73 reactions25 Starsread 9 August 2026
Video

🌟🤍🤍🤍 #OURNOTES 🥹 #EDIT 🌟song : «hikari — mercuro» 🌟🌟🌟🌟🦇 : «сессия — ВСЁ» 🐇 art cr : Gemini_mujou on x

custom 519507172259585252830custom 528771916221753393920custom 542727860546807339819custom 52445306461261982174

31 May 2026, 19:43 UTC424 views48 reactions10 Starsread 9 August 2026
Video

🌟🌟🌟 🤍 #WHA 🥹 #EDIT song : «hanagatami — phantom siita» 🌟🦇 : «с первым днём лета вас» 🌟🌟🌟🌟🌟🤩 png by raira

custom 533023917953414445721❤‍🔥8custom 52063108617354901978💘3custom 52065537722008515843custom 53300236451903313143💅1🕊1

28 May 2026, 13:28 UTC314 views16 reactionsread 9 August 2026
Forwarded from @kaemiartVideo

edit for @ neiel 🤍 ♫ mazari – #эдит #hsr

custom 53300236451903313148❤‍🔥3🎉3custom 53505275441835014312

16 May 2026, 12:31 UTC373 views21 reactionsread 9 August 2026

спасибо за звёзды ❤️ love you guys

custom 53300236451903313149custom 53574281779436974276custom 53302391795341444574🎉2

Showing the 12 most recent of 20 posts we hold for @neielvamp. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 225,532 of 1,345,403entries 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.

Forward network

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.

Mentions

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.

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“мегарест 𝜗ৎ ネイエル” (@neielvamp), 138 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/neielvamp.

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.