Channel
@Apchxi_emae
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
480subscribers
+1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002732052133 |
|---|---|
| Type | Channel |
| Username | @Apchxi_emae |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/Apchxi_emae |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 11:23 | 480 | +1 |
| 10 Aug 2026, 20:16 | 479 | first reading |
17 posts held, back to 23 June 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 pageof 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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 17 (23 June 2026 – 8 August 2026) |
| Views total | 2,300 |
| Reactions total | 360 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 20:16 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.
806 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 42.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5305443624664710414 | 345 | 42.8% | |
| custom 5267033719251697884 | 268 | 33.3% | |
| custom 5195414134568539885 | 162 | 20.1% | |
| custom 5469785308386041323 | 31 | 3.85% |
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 areTelegram’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 16 of the 17 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 806reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 23 June 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 @Apchxi_emae. 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 17 most recent posts we hold for this entry, published 23 June 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.
~ 9 августа 💥. ~ аа, что говорить то, хаха... Настал мой день рождения, йооу 🙇. Не могу сказать что прям счастлив, но вот так вот. Мне будет приятно если вы порепрстите мои работы, хаха ♥️ Автор ──★ ˙🍓 !!реакции/репосты?
custom 546978530838604132315custom 52670337192516978844custom 53054436246647104143custom 51954141345685398852
Нарисовала Кирилла,уж больно меня вдохновил его образ.😛 #полноцен.
custom 526703371925169788431custom 530544362466471041418custom 51954141345685398853
Еее,арт с осом.🍀🍀 #полноцен. #ос.
custom 530544362466471041436
Быстрая хумка хайпующей дамы.😛 #скетч.
custom 526703371925169788437custom 530544362466471041410custom 51954141345685398857
ТВ:Обнажённое тело.❗️ Вот такой вот Джокер из кабаре.🤩 #NSFW(18+) #13карт.
custom 530544362466471041443custom 526703371925169788410custom 51954141345685398856
#Пик Флешмоб Задать вопрос Пику | Канал автора ___ ➡️Подать заявку на вступление в канал аска
custom 526703371925169788435custom 530544362466471041418custom 51954141345685398859custom 54697853083860413231
Posted without readable text
custom 519541413456853988540custom 530544362466471041418custom 526703371925169788410custom 54697853083860413234
Мой любимый мальчик.🥰 #13карт. #полноцен.
custom 519541413456853988547custom 530544362466471041419custom 526703371925169788411custom 54697853083860413235
ЭТО МОЙ СЫН. 🫣
custom 526703371925169788425custom 53054436246647104142
~ я жив, танцуем 🐾 ~ моё сердечко растопил тот скетч, и я не смог ответить взаимностью этому художнику 🫶♥️. Пытаюсь повышать свой скилл, хвхв Автор ──★ ˙🍓 !!реакции/репосты?
custom 530544362466471041428custom 51954141345685398855custom 52670337192516978844
А помните? А вот второй заход, рисую тех, кто не отписался аххаха.📖 #скетч.
custom 526703371925169788440custom 530544362466471041420
Видео для тик тока. 🥰 И кадр отдельно.
custom 530544362466471041449custom 519541413456853988516custom 526703371925169788411custom 54697853083860413232
Showing the 12 most recent of 17 posts we hold for @Apchxi_emae. 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.
Citation-graph rank — 1,086,248 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Апчхи. е.💥[16+]” (@Apchxi_emae), 480 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/Apchxi_emae.
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.