Channel
@aligataarw
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
92subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001424180263 |
|---|---|
| Type | Channel |
| Username | @aligataarw |
| Created | 8 August 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 9 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/aligataarw |
Travel — 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 3 October 2026 and assigned it the closest of 31 fixed categories, at 64% 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 |
|---|---|---|
| 3 Oct 2026, 08:37 | 92 | +2 |
| 9 Aug 2026, 14:18 | 90 | no change |
| 7 Aug 2026, 19:46 | 90 | first reading |
13 posts held, back to 20 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 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 13 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
16 reactions across 10 posts, in 6 distinct kinds. The most used accounts for 43.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 6185862897587980095 | 7 | 43.8% | |
| custom 5316663530940804404 | 3 | 18.8% | |
| custom 5244827458431107252 | 2 | 12.5% | |
| custom 5355290641439924844 | 2 | 12.5% | |
| custom 5431557896133427781 | 1 | 6.25% | |
| custom 6211012082884675877 | 1 | 6.25% |
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 10 of the 13 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 16 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 13 most recent posts we hold, published 20 July 2026 to 6 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.
это было very very not safe🙏 но этот experience мне было очень важно прожить! я не видела смысла ехать на этот пляж только ради фото.. ещё до поездки я знала, что обязательно спущусь вниз и проживу этот ✨нишевый✨ experience
custom 61858628975879800951
📍 Kelingking beach тот самый пляж, куда мечтает попасть почти каждый 🐚
custom 61858628975879800952
Video message, posted without a caption
custom 61858628975879800952
еле как встали около 7 утра 🥴 пока я накрасилась, собралась, и мы дошли до пляжа, нас уже встречали вот такие милашки 🐒 время было примерно 8am самое приятное, людей почти вообще не было! потому что первый паром обычно прибывает только около 8:30~ ✨
custom 61858628975879800951
если соберётесь на остров Нуса-Пенида, мой совет оставайтесь там минимум на 2 дня! так вы успеете посмотреть почти все самые красивые споты без огромных очередей, не будете никуда спешить и сможете спокойно насладиться островом 🥰 мы переночевали в 📍 Kelingking Lucky Homestay находится в 5 минутах пешком от самого популярного пляжа Kelingking Beach и до порта тоже совсем недалеко номер был чистый, уютный и без та…
custom 61858628975879800951
гуд моооорнинг саншайнс сегодня продолжу рассказывать о своем путешествии на Бали 🚤🐚🐚
custom 53166635309408044041
Video message, posted without a caption
custom 52448274584311072522custom 62110120828846758771
Video message, posted without a caption
custom 54315578961334277811
как я и писала раньше, после второго дня на Бали я уже устала 🤩 почти все 9 дней там, были очень продуктивные и я вообще не высыпалась.. а дальше была ещё долгая дорога до конечного пункта назначения весь мой путь: Джакарта -> Бали (2 часа) Бали -> Куала Лумпур (3 часа) Куала Лумпур -> Стамбул (10 часов) Стамбул -> Алания (примерно 4 часа, хотя изначально должно было быть 1,5 часа) сейчас я вообще в Белеке😐
custom 53552906414399248442
гуд моня или лучше гуд найт саншайнс! 🫂 ваша пропажа устала от “отдыха”.. слишком много было событий за эти 3~ недели 🤩 сейчас постараюсь все по полочкам вам рассказать 📌потихоньку буду выкладывать фоточки, которые ещё не успела отобрать для постов
custom 53166635309408044042
спойлер с сегодняшнего трипа, но о нем я расскажу завтра 🥺 сорьки сил нет.. а фоток около тысячи 🤪
Video message, posted without a caption
Showing the 12 most recent of 13 posts we hold for @aligataarw. 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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“будущее меня пугает” (@aligataarw), 92 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/aligataarw.
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.