Или нет?

Channel
𝙈𝙚𝙣𝙞𝙡𝙖 𝙭 𝙚𝙙𝙞𝙩𝙨
@menila_edits
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
401subscribers
-6 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 | -1003620086307 |
|---|---|
| Type | Channel |
| Username | @menila_edits |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 3 times, most recently 17 September 2026 |
| On Telegram | t.me/menila_edits |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 |
|---|---|---|
| 31 Aug 2026, 03:55 | 401 | -3 |
| 24 Aug 2026, 01:34 | 404 | +6 |
| 15 Aug 2026, 19:24 | 398 | -7 |
| 8 Aug 2026, 02:01 | 405 | -2 |
| 7 Aug 2026, 05:02 | 407 | first reading |
Engagement
18 posts held, back to 25 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 18 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
44 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 25.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5280542619758268993 | 11 | 25.0% | |
| custom 5348309872179949637 | 11 | 25.0% | |
| custom 5346013744008802496 | 10 | 22.7% | |
| custom 5409177182331218478 | 4 | 9.09% | |
| custom 5348440572329734136 | 3 | 6.82% | |
| custom 5364084406589863344 | 2 | 4.55% | |
| custom 5406611523487411073 | 2 | 4.55% | |
| custom 5283198919591892528 | 1 | 2.27% |
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 18 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 44 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 25 July 2026 to 6 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.
Recent posts
https://vt.tiktok.com/ZS4CrHUL1/ Активчик на видосик Лайк+комент+репост Тебе не сложно а мне приятно Заранее спасибо
Signed skippa
Наебал
седня дроп
🌟😉
Signed end 悶
Sticker, posted without a caption
Signed skippa
Вы наверно щас ахуеете Я ПАЦАН БЛЯ А то я куда только не зайду, банально к себе в тт комментарии, все на фулл ебле пишут что я девочка нахуй Я ахуеваю
custom 54091771823312184784custom 53640844065898633442custom 54066115234874110732
Добро пожаловать @novator_pubg
FEDERATION все!
Любимую в бравлик затащил хапзхазхпап
custom 52805426197582689932custom 53483098721799496372custom 52831989195918925281custom 53460137440088024961
смотрим с евой и моим любимым «барби марипосу»🥱
Опять взял заказ у менилки это просто шикарно,спасибо большое 😘
Showing the 12 most recent of 18 posts we hold for @menila_edits. 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.
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 11 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.
@kustikeditor · 1452 postsɴɪᴋᴏʟʟ ᴇᴅɪᴛꜱ
@nikolllinxx · 1,0382 postsꜱᴋᴀɴʟʏx ᴇᴅɪᴛꜱ友
@skanlyxedits · 5762 postsvexsach
@vexsach · 72 posts𝐔𝐓𝐎𝐏𝐈𝐀
@fd_UTOPIA · 9951 postFD 𝔵𝔱𝔞𝔰𝛾
@hlvy_edit · 581 postᴍᴀɴᴇʀᴀ💍
@manerawhat66 · 4431 post_
@pabelka_edits · 261 postPadington
@padington_ae · 211 post.
@ri22all_nxdm · 1271 post𝚑𝚝𝚝𝚙𝚜://𝚠𝚡𝚗𝚍𝚎𝚛.𝚏𝚞𝚌𝚔
@wxnderfuck · 1,8801 post
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 31 August 2026 — this entry's latest reading, not the date you are reading this.
“𝙈𝙚𝙣𝙞𝙡𝙖 𝙭 𝙚𝙙𝙞𝙩𝙨” (@menila_edits), 401 subscribers as measured 31 August 2026. Telegram Register, tgregister.com/channel/menila_edits.
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.