Channel
@alexoshart
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Declared links · Cite this entry
964subscribers
-3 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001643733323 |
|---|---|
| Type | Channel |
| Username | @alexoshart |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/alexoshart |
Gaming — 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 19 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 20:37 | 964 | +1 |
| 10 Sept 2026, 14:57 | 963 | -3 |
| 1 Sept 2026, 16:07 | 966 | +3 |
| 24 Aug 2026, 20:07 | 963 | -3 |
| 16 Aug 2026, 17:37 | 966 | -1 |
| 8 Aug 2026, 09:41 | 967 | no change |
| 8 Aug 2026, 05:17 | 967 | first reading |
13 posts held, back to 5 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 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 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.
203 reactions across 12 posts, in 9 distinct kinds. The most used accounts for 30.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5463258057607760727 | 62 | 30.5% | |
| 🔥 | 52 | 25.6% | |
| custom 5341281411603116139 | 36 | 17.7% | |
| custom 5418194728162182625 | 28 | 13.8% | |
| 🏆 | 12 | 5.91% | |
| 😎 | 6 | 2.96% | |
| 😁 | 3 | 1.48% | |
| 🤯 | 3 | 1.48% | |
| 🎉 | 1 | 0.493% |
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 12 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 203 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 5 June 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @alexoshart. 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 13 most recent posts we hold for this entry, published 5 June 2026 to 6 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.
Второстепенный персонаж - донор и хранитель квестового предмета 🧛♀️ Дозаписал одного персонажа для подсказки игроку что этот персонаж есть где-то в здании 🐸
🔥8custom 53412814116031161394🏆2custom 54181947281621826251custom 54632580576077607271
Правильный ответ: 14-18, а точнее 1️⃣8️⃣ 19 если считать плачущий голос в телефоне 👍
🔥8custom 54181947281621826253custom 54632580576077607272custom 53412814116031161391
Posted without readable text
custom 54181947281621826254🤯2😎2
Прошел все руты в Scottside ⚠️ Нашел все отсылки к The Hungry Town 🧛♀️ Кстати, в «Голодном городе» тоже есть ответная пасхалка на Scottside - внимательные игроки смогут найти ее в одном из метро 👀 Круто, когда разрабы так коллабятся 🫠
🔥12custom 53412814116031161394custom 54181947281621826253🎉1
‼️Вышла SCOTTSIDE - атмосферная визуальная новелла в духе “Очень странных дел” 📼 Описание игры: Ты переезжаешь в тихий заснеженный городок, где всё кажется обычным. Но одна находка в лесу меняет всё. Разработчик обещает много иммерсивных элементов, которые усилят погружение, а прохождение не будет ограничиваться только чтением текста. В Scottside вас ждёт: 😥 геймплейные фишки нестандартные для жанра 😥 история про п…
custom 546325805760776072713🏆5😎4
небольшая раскадровка одной из финальных сцен 😱 Можно получить только если плохо себя вести 🤫
custom 53412814116031161399custom 54632580576077607276custom 54181947281621826255🏆1🔥1
🎧🎧😎🎧🎧
🔥4custom 53412814116031161394custom 54632580576077607274
Давно не было постов, исправляюсь 🤔 Третий ролик с кастом актёров озвучки "Голодного города" 🧛♀️ Пишите в комментариях, кого узнали и в каких проектах уже слышали эти голоса 👍
🔥10custom 54632580576077607274custom 54181947281621826253custom 53412814116031161391
👀 Вот так поворот! Ждём, осталось не долго❗️
🔥Игра выйдет 29 июля в 20:00 по МСК! Вы наконец-то сможете посетить новую школу. Обрести новых друзей (или врагов). И стать частью событий, которые навсегда изменят жизни многих жителей Скоттсайда. 📹 Блогерам: Если у вас есть свой канал, блог или медиа с живой аудиторией — напишите в личные сообщения канала и пришлите ссылку на себя, с минимальной информацией. По возможности я выдам бесплатный ключ специально для …
🔥8custom 54632580576077607275🏆4custom 54181947281621826252
Смотрим красивое, слушаем музыку) www.kickpunch.games 🧛♀️ Постепенно наполню 😃 Корректно пока только с пк отображается🖥
custom 54632580576077607279custom 53412814116031161395custom 54181947281621826253🔥1🤯1
🤔🤔🤔
custom 54632580576077607279custom 53412814116031161394custom 54181947281621826252
Showing the 12 most recent of 13 posts we hold for @alexoshart. 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.
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 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.
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
2 URLs this entry has put in its own public description, shown exactly as written there. A declaration, not a verified association — we measured that the description contained this text, and nothing more. It is not a claim that this entry owns, runs or is connected to whatever the link resolves to; a description is text anyone controls, and anyone can put anyone else’s URL into it. How this is measured.
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.
“The Hungry Town” (@alexoshart), 964 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/alexoshart.
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.