причина седых волос каждого во дворце мамины ангелочки (дьяволята) 🤩🤩🤩 над именами пока думаю
custom 546315475505434983716custom 53593302042107080589custom 54382663301070974949❤🔥1

Channel
@aliiishkas
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
99subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001938095694 |
|---|---|
| Type | Channel |
| Username | @aliiishkas |
| Created | Between 1 April 2023 and 31 October 2023— 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/aliiishkas |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 04:41 | 99 | no change |
| 10 Aug 2026, 04:46 | 99 | first reading |
12 posts held, back to 18 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 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 4 August 2026 |
|---|---|
| Posts held | 12 (18 July 2026 – 4 August 2026) |
| Views total | 1,141 |
| Reactions total | 293 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 04:46 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 2 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.
293 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 31.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463154755054349837 | 93 | 31.7% | |
| custom 5359330204210708058 | 55 | 18.8% | |
| custom 5458850944420685430 | 54 | 18.4% | |
| custom 5438266330107097494 | 47 | 16.0% | |
| ❤🔥 | 20 | 6.83% | |
| custom 5370929755531006449 | 14 | 4.78% | |
| 🍓 | 7 | 2.39% | |
| ❤ | 3 | 1.02% |
Custom emoji. 5 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 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 12 of the 12 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 293reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 12 most recent posts we hold, published 18 July 2026 to 4 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 546315475505434983716custom 53593302042107080589custom 54382663301070974949❤🔥1
Не скучайте, ловите черновые анимации и карту мира по ватану 🤩 #ватан_тлеющие_истоки
custom 535933020421070805811custom 54588509444206854307custom 54631547550543498376custom 54382663301070974943❤1
Время летит
custom 546315475505434983711custom 54588509444206854307custom 53593302042107080583custom 54382663301070974941
File, posted without a caption
custom 53709297555310064495custom 54588509444206854304custom 53593302042107080582
еще один орленок 🤩🤩🤩 #ватан_тлеющие_истоки
custom 535933020421070805815custom 54588509444206854308custom 54631547550543498377custom 53709297555310064492
File, posted without a caption
custom 53593302042107080585custom 54631547550543498372
бабалькин орленок 🐱 #ватан_тлеющие_истоки
custom 546315475505434983711custom 543826633010709749410custom 54588509444206854305custom 53593302042107080582❤🔥1
File, posted without a caption
custom 54631547550543498378custom 53593302042107080585custom 53709297555310064495❤🔥1
хук справа хук слева #ватан_тлеющие_истоки
custom 546315475505434983716❤🔥9custom 54382663301070974948custom 53593302042107080582custom 53709297555310064491
бабалькины орлицы-тигрицы 🐱 #ватан_тлеющие_истоки
custom 543826633010709749412custom 54631547550543498379❤🔥8❤2custom 53593302042107080581custom 53709297555310064491
А еще спешу сообщить! 🔥 уже в разработке отдельный ориг сеттинг для Махача и в целом моих персонажей с кавказскими мотивами 🤩 буду держать вас в курсе, пока что есть основная задумка и поверхностный лор #ватан_тлеющие_истоки
custom 545885094442068543010custom 54631547550543498375🍓3
Эффект канала на 1 папищека Этот горячий аварский мужчина принадлежит @aliiishkas
custom 545885094442068543013🍓4custom 54382663301070974944custom 54631547550543498372
Showing the 12 most recent of 12 posts we hold for @aliiishkas. 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.
Citation-graph rank — 89,321 of 1,478,351entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
“алишкс” (@aliiishkas), 99 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/aliiishkas.
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.