Cr:Amina✅
custom 52716313142383475042custom 54651194491892294302custom 53549315564041834331custom 54654779758792301641
Signed 𝑨’077

Channel
@ALIEVYl7
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
160subscribers
-88 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004243232363 |
|---|---|
| Type | Channel |
| Username | @ALIEVYl7 |
| Created | 8 June 2026 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 5 |
| On Telegram | t.me/ALIEVYl7 |
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 27 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
@ALIEVYl7 was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 12:22 | 160 | no change |
| 27 Sept 2026, 11:47 | 160 | -87 |
| 16 Aug 2026, 03:26 | 247 | -8 |
| 7 Aug 2026, 16:27 | 255 | +7 |
| 7 Aug 2026, 03:17 | 248 | first reading |
16 posts held, back to 8 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 2 pages 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 16 posts for this entry, the most recent from 24 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
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.
53 reactions across 6 posts, in 12 distinct kinds. The most used accounts for 18.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5271631314238347504 | 10 | 18.9% | |
| custom 5465208578350554566 | 9 | 17.0% | |
| custom 5465477975879230164 | 8 | 15.1% | |
| custom 5465119449189229430 | 7 | 13.2% | |
| custom 5377749631021110000 | 4 | 7.55% | |
| custom 5377799126224227145 | 4 | 7.55% | |
| custom 5409166767035555119 | 3 | 5.66% | |
| custom 5301192255581725456 | 2 | 3.77% | |
| custom 5377390975482089226 | 2 | 3.77% | |
| custom 5429218577771160763 | 2 | 3.77% | |
| custom 5273884462671764896 | 1 | 1.89% | |
| custom 5354931556404183433 | 1 | 1.89% |
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 7 of the 16 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 53 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 8 June 2026 to 24 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 @ALIEVYl7. 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 16 most recent posts we hold for this entry, published 8 June 2026 to 24 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.
Cr:Amina✅
custom 52716313142383475042custom 54651194491892294302custom 53549315564041834331custom 54654779758792301641
Signed 𝑨’077
Sticker, posted without a caption
Signed 𝑨’077
Cr: Eren✅
custom 52716313142383475044custom 54652085783505545664custom 54654779758792301642custom 54091667670355551191custom 54292185777711607631custom 54651194491892294301
Signed 𝑨’077
File, posted without a caption
custom 53011922555817254562custom 53777496310211100002custom 53777991262242271452custom 54091667670355551191
Signed 077Alieva
Sticker, posted without a caption
Signed 077Alieva
Sticker, posted without a caption
Signed 077Alieva
Voice message, posted without a caption
Signed 077Alieva
Cr - Naz✅
custom 52738844626717648961custom 53777496310211100001custom 54091667670355551191custom 54651194491892294301
Signed 077Alieva
Посты на рп Пост 1 Пост 2
Signed а.
Союзов нам. Связь — правила
Signed 077Alieva
Ne ishem vnimanya - pritagivaem👍
Signed 077Alieva
Sticker, posted without a caption
Showing the 12 most recent of 16 posts we hold for @ALIEVYl7. 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.
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.
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.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“ALIEVY — 077” (@ALIEVYl7), 160 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/ALIEVYl7.
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.