🤩
custom 51906904479320345856custom 54652486332155439784custom 53752631155396636263custom 53774066005731148582
Signed أَمَلَ

Channel
@namaevr
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
170subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002589319378 |
|---|---|
| Type | Channel |
| Username | @namaevr |
| Created | Between 1 March 2025 and 31 July 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 | 4 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/namaevr |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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, 11:37 | 170 | +1 |
| 31 Aug 2026, 04:07 | 169 | -1 |
| 8 Aug 2026, 15:15 | 170 | no change |
| 7 Aug 2026, 19:45 | 170 | first reading |
13 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 13 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 7 videos 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.
160 reactions across 12 posts, in 11 distinct kinds. The most used accounts for 20.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5377406600573114858 | 32 | 20.0% | |
| custom 5375263115539663626 | 25 | 15.6% | |
| custom 5465248633215543978 | 24 | 15.0% | |
| custom 5190690447932034585 | 23 | 14.4% | |
| custom 5226519971353361834 | 19 | 11.9% | |
| custom 5273829508565190033 | 13 | 8.13% | |
| custom 5325870961570898811 | 8 | 5.00% | |
| custom 5278428971862609102 | 7 | 4.38% | |
| custom 5429320913956910949 | 4 | 2.50% | |
| custom 5300897015234849206 | 3 | 1.88% | |
| custom 5336902954437860723 | 2 | 1.25% |
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 12 of the 13 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 160 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 11 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.
🤩
custom 51906904479320345856custom 54652486332155439784custom 53752631155396636263custom 53774066005731148582
Signed أَمَلَ
🤐🤐🤐
custom 52784289718626091024custom 51906904479320345852custom 54293209139569109492custom 53752631155396636261custom 53774066005731148581
Signed أَمَلَ
Photo, posted without a caption
custom 52738295085651900336custom 52265199713533618345custom 54652486332155439785
Signed أَمَلَ
Posted without readable text
custom 53752631155396636269custom 54652486332155439782custom 52265199713533618341custom 53774066005731148581
Signed أَمَلَ
Photo, posted without a caption
custom 53774066005731148586custom 54652486332155439782custom 51906904479320345851custom 52265199713533618341custom 52738295085651900331custom 52784289718626091021custom 53752631155396636261
Signed أَمَلَ
Video, posted without a caption
custom 54652486332155439786custom 51906904479320345852custom 53774066005731148582custom 52265199713533618341custom 53752631155396636261
Signed أَمَلَ
Сюда го https://t.me/SneakerZoneSe
Signed أَمَلَ
Video, posted without a caption
custom 51906904479320345856custom 52265199713533618341custom 53752631155396636261custom 53774066005731148581
Signed أَمَلَ
Home💕
custom 51906904479320345855custom 52265199713533618343custom 53752631155396636262custom 54652486332155439782custom 53774066005731148581
Signed أَمَلَ
🪷
custom 53774066005731148585custom 52738295085651900333custom 53752631155396636263custom 52784289718626091022
Signed أَمَلَ
Posted without readable text
custom 53774066005731148586custom 53752631155396636264custom 52265199713533618342custom 54293209139569109492custom 51906904479320345851
Signed أَمَلَ
Чуть грустно
custom 52738295085651900333custom 53774066005731148583custom 54652486332155439783
Signed أَمَلَ
Showing the 12 most recent of 13 posts we hold for @namaevr. 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.
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.
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.
“𝙽𝚊𝚍𝚢𝚞𝚜𝚑” (@namaevr), 170 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/namaevr.
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.