Аххаахах 🤩🤩🤩🤩

Channel
Мишанетроль
@nepabgery
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
16subscribers
-1 since we began measuring on 14 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002735992801 |
|---|---|
| Type | Channel |
| Username | @nepabgery |
| Created | 9 June 2025 — measured — dated from the channel’s first post |
| First recorded | 14 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 13 October 2026 |
| On Telegram | t.me/nepabgery |
Topic
Memes & entertainment — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 95% 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 |
|---|---|---|
| 3 Oct 2026, 17:01 | 16 | -1 |
| 31 Aug 2026, 11:58 | 17 | -1 |
| 24 Aug 2026, 01:13 | 18 | +1 |
| 14 Aug 2026, 20:31 | 17 | no change |
| 14 Aug 2026, 20:17 | 17 | first reading |
Engagement
14 posts held, back to 9 June 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 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 14 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
137 reactions across 9 posts, in 14 distinct kinds. The most used accounts for 15.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5307882843966292182 | 21 | 15.3% | |
| custom 5275988184897964890 | 20 | 14.6% | |
| custom 5363854720328823157 | 17 | 12.4% | |
| custom 5366148735376061173 | 14 | 10.2% | |
| custom 5366477386273552383 | 13 | 9.49% | |
| custom 5206675659077732910 | 12 | 8.76% | |
| custom 5310081734077858101 | 12 | 8.76% | |
| custom 5204392196765143110 | 11 | 8.03% | |
| custom 5366524304496291685 | 7 | 5.11% | |
| custom 5474370031355705958 | 4 | 2.92% | |
| custom 5275998402625162217 | 2 | 1.46% | |
| ❤ | 2 | 1.46% | |
| custom 5204181442719928027 | 1 | 0.73% | |
| ❤🔥 | 1 | 0.73% |
Custom emoji. 12 of the rows above are 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 9 of the 14 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 137 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 9 June 2025 to 9 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
Троль 4 пул настоящего мужчины
Спасиба шо вы еще тут
Тут остались только мои самые преданные фанаты
Накидайте реакций если хотите что бы я велечайший вернулся в тг
custom 52759881848979648907custom 53638547203288231574custom 53661487353760611734
Пацани я ухажу с тролинга я теперь добрый можете меня не боятся 😀
custom 52759984026251622172custom 53661487353760611732custom 53665243044962916852
Photo, posted without a caption
custom 52759881848979648902
Новую клаву на оценочку🤩
custom 53078828439662921829custom 53638547203288231576custom 52759881848979648905custom 53664773862735523832custom 53661487353760611731
🍑
custom 52759881848979648906custom 53664773862735523835custom 53078828439662921824
🇺🇸
custom 53661487353760611736custom 53078828439662921824custom 53638547203288231574custom 53664773862735523834
Уже не Лучший троль в исламе🙂
custom 53100817340778581014custom 54743700313557059584custom 53078828439662921823
🤩
custom 520439219676514311011custom 520667565907773291011custom 53100817340778581018custom 53664773862735523832custom 53665243044962916852custom 53638547203288231571custom 53661487353760611731
Showing the 12 most recent of 14 posts we hold for @nepabgery. 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.
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 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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Мишанетроль” (@nepabgery), 16 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/nepabgery.
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.