Video message, posted without a caption
custom 52264644245413064424custom 52894906515435164164custom 53055455270587840483custom 54539017462313256223custom 52895045328778182502

Channel
@netesanetesa
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Cite this entry
287subscribers
+24 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002307460541 |
|---|---|
| Type | Channel |
| Username | @netesanetesa |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/netesanetesa |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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 |
|---|---|---|
| 3 Oct 2026, 03:58 | 287 | +12 |
| 17 Sept 2026, 20:36 | 275 | -1 |
| 10 Sept 2026, 15:20 | 276 | +8 |
| 1 Sept 2026, 08:36 | 268 | +4 |
| 24 Aug 2026, 07:57 | 264 | +2 |
| 15 Aug 2026, 19:47 | 262 | -1 |
| 8 Aug 2026, 09:03 | 263 | no change |
| 7 Aug 2026, 16:25 | 263 | first reading |
15 posts held, back to 31 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 15 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
434 reactions across 15 posts, in 9 distinct kinds. The most used accounts for 27.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5226464424541306442 | 119 | 27.4% | |
| custom 5453901746231325622 | 60 | 13.8% | |
| custom 5305545527058784048 | 56 | 12.9% | |
| custom 5262477699548457626 | 46 | 10.6% | |
| custom 5425045531711781230 | 42 | 9.68% | |
| custom 5375525263163549705 | 38 | 8.76% | |
| custom 5289490651543516416 | 29 | 6.68% | |
| custom 5377363719619632988 | 29 | 6.68% | |
| custom 5289504532877818250 | 15 | 3.46% |
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 15 of the 15 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 434 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 31 July 2026 to 8 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @netesanetesa. 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 15 most recent posts we hold for this entry, published 31 July 2026 to 8 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.
Video message, posted without a caption
custom 52264644245413064424custom 52894906515435164164custom 53055455270587840483custom 54539017462313256223custom 52895045328778182502
Video message, posted without a caption
custom 52264644245413064424custom 53055455270587840484custom 52894906515435164163custom 52895045328778182501custom 54250455317117812301
Ну какой он у меня лев 🥹
custom 545390174623132562212custom 52264644245413064428custom 52624776995484576267custom 53755252631635497053custom 54250455317117812303custom 53055455270587840481custom 53773637196196329881
Video message, posted without a caption
custom 545390174623132562210custom 52264644245413064426custom 53055455270587840485custom 52624776995484576262custom 52894906515435164161custom 52895045328778182501custom 53755252631635497051custom 53773637196196329881
Video message, posted without a caption
custom 526247769954845762610custom 54250455317117812305custom 52264644245413064423custom 53755252631635497052custom 52894906515435164161custom 52895045328778182501custom 53055455270587840481custom 53773637196196329881
Video message, posted without a caption
custom 522646442454130644211custom 52624776995484576267custom 53773637196196329885custom 54250455317117812304custom 54539017462313256222custom 52894906515435164161custom 52895045328778182501custom 53055455270587840481
Video message, posted without a caption
custom 54539017462313256228custom 52264644245413064424custom 52894906515435164164custom 53055455270587840482custom 52624776995484576261custom 52895045328778182501custom 53755252631635497051custom 53773637196196329881
Video message, posted without a caption
custom 52624776995484576268custom 53055455270587840486custom 52264644245413064425custom 54250455317117812305custom 52894906515435164161custom 52895045328778182501custom 53755252631635497051custom 53773637196196329881
Video message, posted without a caption
custom 52264644245413064427custom 54539017462313256226custom 54250455317117812305custom 53055455270587840483custom 52624776995484576262custom 53755252631635497052custom 52894906515435164161custom 52895045328778182501
5️⃣2️⃣
custom 522646442454130644214custom 542504553171178123011custom 53055455270587840487custom 53755252631635497053custom 52624776995484576262custom 52894906515435164161custom 52895045328778182501custom 53773637196196329881
🐈⬛💇🏽♀️ У меня сегодня челлендж успеть ВСЁ за 24 часа 🤭
custom 522646442454130644210custom 53055455270587840488custom 53773637196196329885custom 54539017462313256223custom 52624776995484576261custom 52894906515435164161custom 52895045328778182501custom 54250455317117812301
Video message, posted without a caption
custom 53055455270587840488custom 52264644245413064427custom 52894906515435164162custom 53773637196196329882custom 54250455317117812302custom 52624776995484576261custom 52895045328778182501custom 53755252631635497051
Showing the 12 most recent of 15 posts we hold for @netesanetesa. 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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Netesa” (@netesanetesa), 287 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/netesanetesa.
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.