Channel
@killerechodispetcher
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
69subscribers
-4 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002377230322 |
|---|---|
| Type | Channel |
| Username | @killerechodispetcher |
| Created | Between 1 September 2024 and 31 March 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 | 6 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/killerechodispetcher |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 15:01 | 69 | -3 |
| 10 Sept 2026, 09:01 | 72 | -1 |
| 25 Aug 2026, 12:09 | 73 | +2 |
| 17 Aug 2026, 11:47 | 71 | -2 |
| 9 Aug 2026, 22:32 | 73 | no change |
| 9 Aug 2026, 03:02 | 73 | first reading |
20 posts held, back to 17 April 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 28 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.
165 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 67.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5837091293792048073 | 112 | 67.9% | |
| custom 5837108671229728499 | 25 | 15.2% | |
| custom 5837078249976370238 | 19 | 11.5% | |
| custom 5834484063959782392 | 7 | 4.24% | |
| custom 5836949615705855561 | 1 | 0.606% | |
| 💘 | 1 | 0.606% |
Custom emoji. 5 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 19 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 165 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 17 April 2026 to 28 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.
Я перешёл с UE4 обратно на GMS2 для удобства и большей оптимизации Хотел больше сделать визуального, но пока-что в основном другим занимаюсь в плане игры. Сейчас выглядит всё мягко говоря так себе Хочу хотя-бы к сентябрю уже сделать версию где будет и рабочий инвентарь и ещё некоторые вещи Ещё пытаюсь понять новый музыкальный стиль чтобы делать к игре ещё и что-то энергичное
custom 58370912937920480732
Скоро покажу скриншоты с моей игры
custom 58370912937920480734
Photo, posted without a caption
custom 58370912937920480734custom 58371086712297284993
Ютуб дегенераты, сами ищите где было нарушение Я даже не знаю что сказать
Забыл сделать пост в телеграмме о новом кавере вчера https://youtu.be/a3DzcxvG4pE?si=PXShhG_fPD_N3Z9L
custom 58370912937920480736custom 58371086712297284994
Угадайте какой будет следующий кавер
custom 58370912937920480737custom 58371086712297284993
Урааа 70 подписчиков Спасибо До сотни не долго осталось Будет скоро кавер, тоже на тему из блэк соулс. Также попробую блэк метал кавер сделать может быть
custom 58370912937920480738custom 58371086712297284993
Решил что будет интересно создать телеграмм канал где будет больше подробностей про разработку и другие мои хобби, а также там где будут всякие смешные и красивые картинки и видео по Touhou, Black souls и другим вещам что мне нравятся, ну и музыка которая мне нравится Не хочу засорять этот основной канал Также там будут фото моей кошки — Муси! Ну и в целом мемы всякие Ну, вообщем, если интересно то вот
custom 58370912937920480735custom 58371086712297284991
Разработка идёт, пока что показывать прямо чего-то интересного нечего
custom 583709129379204807312
Ждите контент Будут каверы, а также я уже не буду держать под сильным секретом некоторые игровые проекты
custom 58370912937920480737custom 58371086712297284992
Photo, posted without a caption
custom 583709129379204807311custom 58371086712297284991
Летом будет много контента
custom 58370912937920480739
Showing the 12 most recent of 20 posts we hold for @killerechodispetcher. 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 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.
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.
“Echo (AlstoЯ)” (@killerechodispetcher), 69 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/killerechodispetcher.
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.