привет

Channel
РИСК - зовёт
@NEIMEETDNA
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
20subscribers
-3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003773459795 |
|---|---|
| Type | Channel |
| Username | @NEIMEETDNA |
| Created | 12 February 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/NEIMEETDNA |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 1 October 2026 and assigned it the closest of 31 fixed categories, at 84% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 12:56 | 20 | -1 |
| 11 Sept 2026, 22:00 | 21 | -1 |
| 14 Aug 2026, 07:15 | 22 | -1 |
| 11 Aug 2026, 11:48 | 23 | no change |
| 7 Aug 2026, 18:33 | 23 | first reading |
Engagement
7 posts held, back to 12 February 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 7 posts for this entry, the most recent from 17 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
111 reactions across 3 posts, in 14 distinct kinds. The most used accounts for 10.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 4904515389725083455 | 12 | 10.8% | |
| custom 4904486729408316862 | 10 | 9.01% | |
| custom 4904839917453969751 | 10 | 9.01% | |
| custom 4904654267492599378 | 9 | 8.11% | |
| custom 4904717244598060840 | 9 | 8.11% | |
| custom 4904604140929287496 | 8 | 7.21% | |
| custom 4904722553177638470 | 8 | 7.21% | |
| custom 4904735511093970368 | 8 | 7.21% | |
| custom 4904744208402744971 | 8 | 7.21% | |
| custom 4907010057054455094 | 8 | 7.21% | |
| custom 4906859973717264317 | 7 | 6.31% | |
| custom 4906815563755423961 | 6 | 5.41% | |
| custom 5328263554707508284 | 6 | 5.41% | |
| custom 4904698123403658435 | 2 | 1.80% |
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 4 of the 7 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 111 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 12 February 2026 to 17 July 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
lovely list by RISK ❤️ inzara , anara , akuma , tumarym , karina , inkar , zhanna , ernazar , saida , white , asahi , zhanel , nail , kami , sveta , vika , azat , elias , nur , diana , kamila , aneka , damn , elias , ruslan , alikhan , dosya , tima , albina , himera , petrova , isatai , anya , fadeeva , arilana, aisultan , selena порядок не имеет значения,список будет пополняться 😊
custom 49047172445980608407custom 49044867294083168626custom 49045153897250834555custom 49046041409292874963custom 49068155637554239613custom 49047225531776384702custom 49047355110939703682custom 53282635547075082841
💜💜💜💜💜💜💜 в ник:риск адрес:там,где риск био: @NEIMEETDNA
to take a risk info🔥anon
custom 49070100570544550948custom 49047225531776384706custom 49047442084027449715custom 49048399174539697515custom 49046542674925993784custom 49047355110939703684custom 49068599737172643174custom 49044867294083168623
Sticker, posted without a caption
💜💜💜💜💜💜 название RISK является нашей собственностью.Любое его использование без разрешения запрещено.При нарушении мы вправе потребовать смену названия и принять меры. 12.02.2026
custom 49045153897250834557custom 49046542674925993785custom 49048399174539697515custom 49047442084027449713custom 49068599737172643173custom 49046041409292874962custom 49046981234036584352custom 49047172445980608402
Channel created
Showing the 7 most recent of 7 posts we hold for @NEIMEETDNA. 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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“РИСК - зовёт” (@NEIMEETDNA), 20 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/NEIMEETDNA.
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.