Join before I delete
Signed Done share

Channel
@Natasha_r00
On this record: Topic ยท Previous handles ยท Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Stars ยท Posts ยท Citations ยท Handles named that no longer answer ยท Cite this entry
10,148subscribers
+2,486 since we began measuring on 16 August 2026
Risers and fallers across the register ยท movement among entries of 10,000โ31,623.
| Telegram ID | -1002824554418 |
|---|---|
| Type | Channel |
| Username | @Natasha_r00 |
| Created | 26 July 2025 โ measured โ dated from the channelโs first post |
| First recorded | 16 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/Natasha_r00 |
Gambling & betting โ 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 16 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
@Natasha_r00 was previously reachable at these 2 handles, before switching to its current one. This says nothing about who or what answers at the old handle today โ only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 19:41 | 10,148 | +274 |
| 16 Sept 2026, 13:22 | 9,874 | +1,011 |
| 2 Sept 2026, 02:13 | 8,863 | +32 |
| 1 Sept 2026, 18:00 | 8,831 | no change |
| 1 Sept 2026, 17:45 | 8,831 | +97 |
| 29 Aug 2026, 03:54 | 8,734 | +159 |
| 26 Aug 2026, 00:23 | 8,575 | +203 |
| 23 Aug 2026, 05:02 | 8,372 | +366 |
| 19 Aug 2026, 19:27 | 8,006 | +318 |
| 16 Aug 2026, 18:15 | 7,688 | +26 |
| 16 Aug 2026, 02:00 | 7,662 | no change |
| 16 Aug 2026, 01:45 | 7,662 | first reading |
168 posts held, back to 26 July 2025 โ the reader has not yet reached the start of this channelโs public history, so older posts may sit further back, unread. Read across 14 pages of Telegramโs post history, 20 posts per page.
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. It is computed over the 30 of 88 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days ยท latest post in window 16 September 2026 |
|---|---|
| Posts held | 168 (26 July 2025 โ 16 September 2026) |
| Views total | 44,395 |
| Reactions total | 1,340 |
| Forwards / comments | not exposed by the public surface โ not measured, not estimated |
| Readings taken | 16 Sept 2026, 13:22 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.
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.
3,189 reactions across 55 posts, in 30 distinct kinds. The most used accounts for 61.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 1,972 | 61.8% | |
| ๐ฅ | 228 | 7.15% | |
| ๐ | 189 | 5.93% | |
| ๐ | 171 | 5.36% | |
| ๐ | 145 | 4.55% | |
| ๐ฅฐ | 105 | 3.29% | |
| ๐ฏ | 36 | 1.13% | |
| ๐คฉ | 36 | 1.13% | |
| ๐ค | 31 | 0.972% | |
| ๐ซก | 31 | 0.972% | |
| โ | 24 | 0.753% | |
| โคโ๐ฅ | 23 | 0.721% | |
| ๐จโ๐ป | 20 | 0.627% | |
| ๐ | 18 | 0.564% | |
| ๐ | 18 | 0.564% | |
| ๐ | 17 | 0.533% | |
| ๐ | 15 | 0.47% | |
| ๐ค | 14 | 0.439% | |
| ๐ญ | 12 | 0.376% | |
| โ | 11 | 0.345% | |
| 10 further kinds | 73 | 2.29% |
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 56 of the 168 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 3,189 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 168 most recent posts we hold, published 26 July 2025 to 16 September 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.
A paid reaction is a reader spending Telegram Stars โ bought with money โ on a post by @Natasha_r00. 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 168 most recent posts we hold for this entry, published 26 July 2025 to 16 September 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.
Join before I delete
Signed Done share
Freeeeeeeeeeeeeeeee
Signed Done share
Goooooooo it's fixed
Signed Done share
https://t.me/ELAHMEDg/15128
Signed Done share
๐ฌ Clean // Shares @Done_213 โญ๏ธ @Done_213 100 - 300 Views
Signed Done share
Sticker, posted without a caption
Signed Done share
Posted without readable text
Signed ๐ก๐ฎ๐๐ฎ๐๐ต๐ฎ.๐ฟโจ
๐ TICKET DROP โ TODAYโS DEAL IS LIVE! ๐ For everyone whoโs been waiting on todayโs ticketโฆ ITโS HERE! ๐ฅ๐ฏ The selections are locked, the deal is set, and weโre ready to step into another one with confidence. ๐ ๐๏ธ VIP Ticket: @Natasha_r01 Stay focused. Trust the process. Letโs go after those odds once again! ๐๐ฅ VIP moves only. ๐๐ฐ
โค37๐6๐ฏ4๐ฅฐ4๐ฅ3๐2๐คฉ2๐2
Signed ๐ก๐ฎ๐๐ฎ๐๐ต๐ฎ.๐ฟโจ
2/3 GUYS WE GO AGAIN ๐๐ STAY ACTIVE ๐ค
โค42โคโ๐ฅ6๐5๐ฅ5๐ฏ4๐3๐คฉ3๐ค2
Signed ๐ก๐ฎ๐๐ฎ๐๐ต๐ฎ.๐ฟโจ
๐ฅ ๐๐๐โ๐ ๐๐, ๐ ๐๐๐๐! ๐ฅ ๐ฏ ๐๐๐๐๐โ๐ ๐ ๐๐๐ ๐๐๐๐ ๐๐ ๐๐๐๐! ๐ฐ ๐๐๐๐๐ ๐๐๐๐, ๐๐๐๐ ๐๐๐๐ & ๐๐๐๐ ๐๐๐๐๐. ๐ ๐๐๐๐ ๐๐๐๐ ๐ ๐๐๐๐ โ ๐๐๐โ๐ ๐๐! ๐
โค72๐ซก11โคโ๐ฅ4๐ค2๐2๐ณ1๐ค1๐คฉ1
Signed ๐ก๐ฎ๐๐ฎ๐๐ต๐ฎ.๐ฟโจ
Photo, posted without a caption
โค6๐3โคโ๐ฅ2๐ฏ2๐คฉ2๐ฅฐ2๐2โ1
Signed ๐ก๐ฎ๐๐ฎ๐๐ต๐ฎ.๐ฟโจ
https://t.me/+rXcuob8PXZJmNWVk
Signed แด โแดส ๐งธ
Showing the 12 most recent of 168 posts we hold for @Natasha_r00. 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.
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.
@Natasha_r00 named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handleโs history โ see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today โ not that anything โdiedโ. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant โ a genuine, evidenced change, not an inference from absence.
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.
โ๐ก๐ฎ๐๐ฎ๐๐ต๐ฎ.๐ฟโจโ (@Natasha_r00), 10,148 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/Natasha_r00.
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.