Channel
@eblan_typ0i
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
72subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002318515138 |
|---|---|
| Type | Channel |
| Username | @eblan_typ0i |
| 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 | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/eblan_typ0i |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 06:57 | 72 | -1 |
| 9 Aug 2026, 22:31 | 73 | no change |
| 7 Aug 2026, 15:31 | 73 | first reading |
13 posts held, back to 13 April 2025 — 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 pageof 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 15 June 2025. An engagement rate over an empty window would be a number about nothing.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 100.0% |
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 2 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 2reactions 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 13 April 2025 to 15 June 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
мои услуги⬇️ продам полную инструкцию по покупке звезд через фрагмент-125₽ продам рассыл бота и расскажу как им пользоваться-70₽ продам папку по продаже/покупке нфт (100+ чатов)- 50₽ ⭐️продам звезды на ваш телеграмм аккаунт⭐️ пополняю на любую сумму от 50⭐️ по вашему username (пример: 112⭐️,666⭐️,52⭐️) курс⬇️ 1⭐️- 1.37₽ 100⭐️- 137₽ от 1000 звезд курс 1.35₽‼️ 1000⭐️- 1350₽ 10000⭐️- 13500₽ все звезды с fragme…
Signed Косой дурак | 𝒔𝒂𝒍𝒆 𝒔𝒕𝒂𝒓𝒔 1.37₽
https://t.me/virus_play_bot/app?startapp=inviteCodeZzyrhlLFn6sH1goc пожалуйста зайдите если не сложно
Signed Косой дурак | 𝒔𝒂𝒍𝒆 𝒔𝒕𝒂𝒓𝒔 1.42₽
‼️ СЕЙЛ ЗВЕЗД ‼️ 1 ⭐️= 1.45₽ 50⭐️ - 75 рублей 100⭐️ - 145 рублей 200⭐️ - 290 рублей 500⭐️ - 725 рублей 1000🌟 - 1450 рублей КУЧА ОТЗЫВОВ ✅ СКАМ МИМО ✅ ГАРАНТЫ/ВАШЕ ДОВЕРИЕ К НАМ✅ пишите в любое время суток! @pustovalow
Signed Косой дурак
Channel name was changed to «Возвращение КОСЫХ»
в лс @kocoi_dyrak
Signed Косой дурак
Куплю нфт желе Писать в лс @kocoi_dyrak
Signed Косой дурак
Продажа нфт с дьявольским номером По поводу покупки писать @kocoi_dyrak
Signed Косой дурак
😅😚😍🙂🥸 🎁🎁📍🌸 Могу еще рассмотреть редкий ширп, по поводу продажи писать в лс @kocoi_dyrak
Signed Косой дурак
Хотело бы высказаться по якобы смерти снойзена,Я в это не поверю пока не увижу его тело,считаю его поступок если это тупой черный хайп очень тупым,если нет то я хз что у него в голове было... Дисклеймер;не хейт
👍2
Signed 𝓓𝓤𝓡𝓐 𝓚𝓞𝓢𝓞𝓡𝓨𝓛𝓐𝓨𝓐
Продам нфт по поводу покупки писать в лс @kocoi_dyrak
Signed Косой дурак
Обменяю новый подарок (за 200зв) на нфт подарок Писать в лс @kocoi_dyrak
Signed Косой дурак
Писать так же ему
Signed 𝓓𝓤𝓡𝓐 𝓚𝓞𝓢𝓞𝓡𝓨𝓛𝓐𝓨𝓐
Showing the 12 most recent of 13 posts we hold for @eblan_typ0i. 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.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“Возвращение КОСЫХ” (@eblan_typ0i), 72 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/eblan_typ0i.
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.