Channel
@aishka88sh
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
563subscribers
+5 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002914269417 |
|---|---|
| Type | Channel |
| Username | @aishka88sh |
| Created | Between 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/aishka88sh |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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 |
|---|---|---|
| 18 Sept 2026, 13:42 | 563 | +5 |
| 10 Sept 2026, 21:57 | 558 | -6 |
| 1 Sept 2026, 18:03 | 564 | -2 |
| 24 Aug 2026, 23:26 | 566 | +2 |
| 17 Aug 2026, 10:53 | 564 | +3 |
| 9 Aug 2026, 21:31 | 561 | +3 |
| 9 Aug 2026, 03:01 | 558 | first reading |
20 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 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 20 posts for this entry, the most recent from 8 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 11 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.
261 reactions across 18 posts, in 7 distinct kinds. The most used accounts for 23.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🕊 | 60 | 23.0% | |
| custom 5364185836537543934 | 57 | 21.8% | |
| custom 5244533777157349664 | 42 | 16.1% | |
| 👻 | 38 | 14.6% | |
| 🌚 | 27 | 10.3% | |
| 👀 | 23 | 8.81% | |
| custom 5244504691638820853 | 14 | 5.36% |
Custom emoji. 3 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 18 of the 20 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 261 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 8 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 @aishka88sh. 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 20 most recent posts we hold for this entry, published 8 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.
⠀⠀⠀⠀⠀⠀⠀⠀🔤ega 🔤ollab ⠀⠀⠀⠀⠀⠀⠀⠀⠀ ⠀⠀with :: кикс , арент , мартва , волакс , оннез , кесс , шаня , айвиша , невралгия , картамановская , ринилс , алиша лол , нолетнова , лавилова , кварта , кисууля , аиша , всегдаксеша , ямайка , киспингс , бэккли , атараксия , нисса , сатоша , кислинка #collab
custom 53641858365375439342
сегодня-завтра начну делать нарезки с кащеем
custom 53641858365375439344
new post #нарезки #cut #cuts #словопацана #спка #словопацанакровьнаасфальте #пальто #андрейвасильев 485х брать строго с отметкой by @aishka88sh
custom 53641858365375439344
Video, posted without a caption
new post #нарезки #cut #cuts #словопацана #спка #словопацанакровьнаасфальте #зима #вахитзималетдинов 131х брать строго с отметкой by @aishka88sh
custom 53641858365375439345
да кстаьи на счет нарезок, я начала делать нарезки с зимой, потом сделаю с пальто из сп 🥺 надеюсь ц меня не грохница тилифон
custom 53641858365375439342
всем привет! у меня день рождения кстати
custom 536418583653754393410
new post #нарезки #cut #cuts #фарма #семен ???х брать строго с отметкой by @aishka88sh нарезки будут пополнятся
custom 53641858365375439346
всем привет, я уже год нахожусь в фд.
…🤍🔤оллаб🤍…с прекрасными ⭐⭐⭐⭐⭐⭐⭐ @neuralgia28 @cesskass @aishka88sh @ataraksiact @kvartaaa @kiksovna banan.b8 satosha_444 @al1shalol @multimaryww @gromova_1212 ⭐⭐⭐️⭐️⭐️⭐️⭐️⭐️⭐️⭐️ ✍️link ✍️link ✍️link 🌲🌲🌟🌲🌲🌟🌲🌲🌟🌲🌲 рп?рк? на 15рк новое видео #коллаб
custom 53641858365375439346
new post #нарезки #cut #cuts #смычок #макс 341х брать строго с отметкой by @aishka88sh
🕊20custom 536418583653754393418
new post #нарезки #cut #cuts #анора #анорамихеева #энимихеева 191х брать строго с отметкой by @aishka88sh
🕊8custom 52445337771573496645custom 52445046916388208534👀1
Showing the 12 most recent of 20 posts we hold for @aishka88sh. 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.
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 11 registered channels — 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“аишка88 | #4” (@aishka88sh), 563 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/aishka88sh.
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.