Channel
@Natayeggg
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,472subscribers
-33 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001650986958 |
|---|---|
| Type | Channel |
| Username | @Natayeggg |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Natayeggg |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 74% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 22:38 | 2,472 | -14 |
| 10 Sept 2026, 17:56 | 2,486 | -5 |
| 5 Sept 2026, 07:19 | 2,491 | -10 |
| 1 Sept 2026, 02:08 | 2,501 | +4 |
| 29 Aug 2026, 06:33 | 2,497 | -2 |
| 26 Aug 2026, 08:26 | 2,499 | +13 |
| 23 Aug 2026, 15:59 | 2,486 | -1 |
| 20 Aug 2026, 04:47 | 2,487 | -8 |
| 16 Aug 2026, 22:13 | 2,495 | -10 |
| 13 Aug 2026, 23:47 | 2,505 | -4 |
| 10 Aug 2026, 21:21 | 2,509 | +4 |
| 7 Aug 2026, 17:06 | 2,505 | no change |
| 7 Aug 2026, 16:32 | 2,505 | first reading |
20 posts held, back to 11 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 20 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
115 reactions across 19 posts, in 4 distinct kinds. The most used accounts for 69.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 80 | 69.6% | |
| 🥰 | 28 | 24.3% | |
| 👏 | 6 | 5.22% | |
| 🔥 | 1 | 0.87% |
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 19 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 115 reactions 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 11 July 2026 to 27 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.
سلامممممم آقا من از ساب صدات نتیجه گرفتم (مودهیپنو صدای فوق العاده) خیلی خفن بودددددد،تقریبا یه هفته گوش دادم جوری که بداهه آهنگ میخونم حتی صدای دوبلوری هم دارم الانننن پ.ن:نتیجه برا ۶سال پیشه🙏🏻،داشتم تلگراممو میگشتم چنلتو دیدم یهو یادم افتاد که بیام بگم حلال کن این همه دیر اعلام کردم 😭😂
🥰13❤1🔥1
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
سلام هاردین من از خیلی سابای چنل تون نتیجه گرفتم رفع محدودیت خانواده که خیلی خوبه پول اروز کد آرزو که خیلی نتیجه داشتم و دیگه خیلی یادم نیست بازم خیلی ممنونم ❤️
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
سلام من از پنتونیکس سرما نتیجه دیدم ، شبایی که از گرما نمیتونم بخوابم یه بار گوش میدم حس و حالم بهتر میشه ،انگار دمای بدنم خنک تر میشه .
🥰4
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
سلام از پنتونیکس پک سلامتی و ساب ارزو نتیجه دیدم،حالم خوب نبود گوش دادم اوکی شدم💘
🥰4
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
سلام وقت بخیر خواستم نتیجمو از ساب افزایش قد بگم🙏💕 ولی متاسفانه عکس ندارم از قبل و بعدش😅
🥰2
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
ای وولکککککک سلامممممم هاردیننننن من 4 یا بیشترمین باره ک از ارزوی اختصاصی نتیجع دیدم البته موضوع یکی بودااا ولی زیر چندساعت و کنارش ۲تا ساب دیگم گوش دادممممم و بوممممم نتیجههههه😍😍🥹🥹🥹 البته دفعه های قبل مال تو تنهارو. گوش میدادم،، خلاصه عالیییی چش نخورممم خودمو نتیجه هام چشم حسود کور😂😍
👏6
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
درود از پنتونیکس پک سلامتی نتیجه دیدممممم همین امروز دوبار گوشش کردم یکم دلشوره و استرس و تهوع داشتم خوب خوب شددد 🫠🎀✨
❤5🥰2
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
درود از ساب ثروت سفارشی نتیجه دیدمممم یبار اینا گوشش کردم و ۵۰۰ تومن جذب کروم مرسییی
❤5
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
درود از این ساب نتیجه گرفتم فقط یه بار گوش دادم
❤5🥰1
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
درود از ساب ثروت نتیجه دیدم رندوم گوشش کردم و برام مشتری اومد ✨🦋
❤8
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
سلام هاردین من از ساب خوراکی نتیجه گرفتم قبل اینکه گوش بدم بابام اومد خونه حس کردم یه چیزایی گرفته ولی نمیدونستم انقد خوب و زیادن نودل گرفته که من عاشقشم تن ماهی چوب شور حتی من خیلی وقت بود میخواستم از این چوب شور گردیا تست کنم بابام گرفته ویفر که عاشق ویفرم و اون کیکا ام که دیگه حرفی برای گفتن نمیذارن خیلییییی خوشحالم و اینم بگم کم پیش میاد مثلا بابام یهو اینهمه خوراکی بگیره خلاصه که گوش کنید و لذتشو ببرین🥹🥹
❤9
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
سلام هاردینی از ارزوی اختصاصی بازم نتیجه دیدم زیر یک ساعت مرسی ازتتتت🥹🧸 برای دیدار با کسی بود و خوب بود مرسیبیی
❤4
Signed 𝘏𝘢𝘳𝘥𝘪𝘯 𖦹
Showing the 12 most recent of 20 posts we hold for @Natayeggg. 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 2 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“𝗥𝗲𝘀𝘂𝗹𝘁 𝗛𝗮𝗿𝗱𝗶𝗻💗𖧷” (@Natayeggg), 2,472 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Natayeggg.
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.