Channel
@gelyaaaa01102
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
65subscribers
+0 since we began measuring on 31 October 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003290718884 |
|---|---|
| Type | Channel |
| Username | @gelyaaaa01102 |
| First recorded | 31 October 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/gelyaaaa01102 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Oct 2026, 23:29 | 65 | no change |
| 31 Oct 2026, 21:22 | 65 | first reading |
4 posts held, back to 11 May 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 22 September 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 4 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.
131 reactions across 4 posts, in 13 distinct kinds. The most used accounts for 17.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5472408262093594634 | 23 | 17.6% | |
| custom 5312115272243487042 | 19 | 14.5% | |
| custom 5357503885332225999 | 18 | 13.7% | |
| custom 5335006082131592060 | 17 | 13.0% | |
| custom 5190803843658564723 | 15 | 11.5% | |
| custom 5467630488933920298 | 12 | 9.16% | |
| custom 5470092364187983398 | 10 | 7.63% | |
| custom 5418250425298077599 | 7 | 5.34% | |
| custom 5325906128763121048 | 3 | 2.29% | |
| custom 5188652825252482327 | 2 | 1.53% | |
| custom 5359514801905110310 | 2 | 1.53% | |
| custom 5407088818908067259 | 2 | 1.53% | |
| custom 5408975761249958213 | 1 | 0.763% |
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 4 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 131 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 11 May 2026 to 22 September 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 53575038853322259997custom 54676304889339202984custom 54724082620935946344custom 53259061287631210483custom 51908038436585647232custom 53121152722434870422custom 54182504252980775992custom 54700923641879833981
🌟🌟🌟🌟🌟🌟🌟🤍 SUPчемп 🥉viviz - maniac me as Eunha
custom 54676304889339202988custom 54700923641879833987custom 54724082620935946345custom 54182504252980775994custom 53121152722434870423custom 53350060821315920603custom 51908038436585647232
🌟🪷🤩⭐⭐⭐⭐⭐🌟
custom 547240826209359463414custom 535750388533222599910custom 53350060821315920608custom 51908038436585647233custom 53121152722434870422custom 54700923641879833982custom 54182504252980775991
🌟 aespa - dirty work me as giselle💙 🌟🌟🌟🌟🌟🌟 🌟🌟🌟🌟🌟🌟🌟
custom 531211527224348704212custom 51908038436585647238custom 53350060821315920606custom 51886528252524823272custom 53595148019051103102custom 54070888189080672592custom 53575038853322259991custom 54089757612499582131
Showing the 4 most recent of 4 posts we hold for @gelyaaaa01102. 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.
Named by 4 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.
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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“гелюсяя!>_<” (@gelyaaaa01102), 65 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/gelyaaaa01102.
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.