Channel
@aminoyak
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
245subscribers
+1 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001898895146 |
|---|---|
| Type | Channel |
| Username | @aminoyak |
| Created | Between 1 November 2022 and 31 August 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/aminoyak |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 11:37 | 245 | -2 |
| 9 Sept 2026, 17:20 | 247 | +1 |
| 1 Sept 2026, 02:04 | 246 | +4 |
| 18 Aug 2026, 16:22 | 242 | -2 |
| 11 Aug 2026, 19:26 | 244 | no change |
| 10 Aug 2026, 23:46 | 244 | first reading |
4 posts held, back to 27 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 4 posts for this entry, the most recent from 18 July 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 3 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.
46 reactions across 3 posts, in 8 distinct kinds. The most used accounts for 23.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5312062302411838309 | 11 | 23.9% | |
| custom 5312381667590045072 | 8 | 17.4% | |
| custom 5323703983066324828 | 8 | 17.4% | |
| custom 5422553355463450187 | 6 | 13.0% | |
| custom 5384130225846120298 | 5 | 10.9% | |
| custom 5309945171297728548 | 3 | 6.52% | |
| custom 5463314545017636323 | 3 | 6.52% | |
| custom 5420324636804019005 | 2 | 4.35% |
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 3 of the 4 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 46 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 4 most recent posts we hold, published 27 June 2026 to 18 July 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.
Photo, posted without a caption
custom 53123816675900450728custom 53237039830663248287custom 54225533554634501874custom 54203246368040190052custom 54633145450176363232custom 53120623024118383091
Signed aminoyaka
Подборка 🏴
custom 53120623024118383098custom 53841302258461202982custom 54225533554634501872custom 53237039830663248281custom 54633145450176363231
Signed aminoyaka
Video message, posted without a caption
Signed aminoyaka
Photo, posted without a caption
custom 53099451712977285483custom 53841302258461202983custom 53120623024118383092
Signed aminoyaka
Showing the 4 most recent of 4 posts we hold for @aminoyak. 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“aminoyáka” (@aminoyak), 245 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/aminoyak.
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.