4 measurements spanning 7 days, net -19. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 5,303–5,328 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
13 Aug 2026, 05:18
5,306
-9
10 Aug 2026, 03:41
5,315
-9
7 Aug 2026, 02:32
5,324
-1
6 Aug 2026, 09:18
5,325
first reading
Engagement
20 posts held, back to 28 January 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 8 pagesof 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 17 June 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
373 reactions across 20 posts, in 2 distinct kinds. The most used accounts for 98.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
368
98.7%
👎
5
1.34%
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 20 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 373reactions 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 28 January 2026 to 17 June 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.
Telegram Stars
Stars received
26
across the posts below
Posts paid on
5
of 20 we hold a reading for · 25%
Most on one post
18
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @in_crypto_info. 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 20 most recent posts we hold for this entry, published 28 January 2026 to 17 June 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.
❗️ РАБОТА
Я пишу код на заказ с 2021 года и по сей день это мой главный источник дохода. За все время работы у меня накопилось очень много опыта, которым я бы хотел поделиться с вами
В следующих постах я хочу разобрать:
🤩Из чего складывается цена за заказ
🤩Как объяснить заказчику за что он платит
🤩Как грамотно составлять план работ
🤩Как управлять ожиданиями заказчика
Эти идеи уже разобраны в черновиках, скоро нач…
🚫 НЕАКТУАЛЬНО
Теперь инвайт код на сайт API не нужен, любой желающий может туда зайти и не надо дрочиться с каптчами. Просто заходите на api.byesu.com и регистрируетесь
Cегодня до 00:00 будет акция, за реферала дают +4pt вместо +1pt. То есть получить кредит в 1000$ можно за 13 рефералов, а не за 50. Сука, почему это сделали не вчера 🤓
🌟 Теперь путь такой
1. Заходите в бота @banyesugy_bot
2. Подписываетесь на кана…
🌟 GPT 5.5 БЕСПЛАТНО
Привет медвед, в этом посте расскажу как получить бесплатные $ для использования API OpenAI. Их нам даст китайский провайдер Byesu, который по сути является прокси для официальных API
Сейчас через их Telegram бота можно фармить поинты за рефералов (+1pts) и за ежедневные крутки (+1-10pts). На эти поинты можно покупать купоны, которые после дают $ на счет
Перед тем как действовать по гайду — пол…
☂️☂️ Бисмаля друзья мои
Идей для постов много, просто нет времени и желания писать. Сил уходит на это очень много, а радости приносит мало. Наверное повзрослел/постарел/прихуел
Однако щитпостить не перестаю, поэтому подписывайтесь на @by_asynco. Я даже открыл там комментарии до 1 мая, еще есть время выразить свое ценное мнение
Я бы мог и сюда щитпостить, но все же хочу поддерживать стиль, да и вам не хочу засорять…
💪 АГЕНТ ДЛЯ РЕСЕРЧА
Поиск решения проблемы, готовых фрагментов кода и самой свежей документации — вот база для твоего нейрослопуса. Без этого будешь страдать в лупе бесконечных правок микро багов, создавая все больше ошибок
Я сделал отдельного агента для ресерча, в этом мне помог пост из приватки Итера. Я его немного пофиксил и теперь расскажу вам, как все красиво настроить
Если нужна серия постов "Вайбдолбаёбинг …
😈 ШОК КОНТЕНТ
Сделал свой первый тред в твиттере, буду рад активу. Кому-то будет полезно, хотя себя ощущаю инфоцыганом. Ну короче начинаю становится на пусть истинный
🔗 https://x.com/asynco_dev/status/2026758875211550955
Хорошо что знаю про Typefully, наверное никто не делает треды в обычном редакторе. Хотел вообще как статью закинуть, но такой формат тоже интересно протестировать
😵💫 щитпост | твиттер | мои ссыл
💀 ZachXBT x Polymarket
Провел небольшой ресерч, чтобы вы были в курсе происходящего. Кратко: ZachXBT 26 числа разоблачит проект, замешанный в инсайдерской торговле длительное время
Сейчас на polymarket в ставке лидирует Meteora, в пике доходила до 67%, текущий топ выглядит так:
🤩Meteora ⠀⠀38%
🤩Other ⠀⠀⠀⠀21%
🤩Axiom⠀⠀⠀⠀14%
🤩MEXC ⠀⠀⠀⠀6%
🤩Pump.fun ⠀5%
Моя ставка на данный момент на Meteora NO, но я не уверен в этом и…
🤩 0$ за SOLSCAN API PRO
Начитался постов про то, что вайбкодеры делают дырявые приложения ($CLAW токен пример). А как вам кейс с обходом платной подписки за 200$ на API Solscan?
Компания, зарабатывающая на платном доступе к данным не может настроить нормальную защиту, генерируя ключи доступа к API за 200$/m на стороне клиента 👍
🤩 Как работает обход?
Автор, который нашел обход, решил чекнуть Network вкладку dev to…
🌀 АПДЕЙТ НА МНЕНИЕ
В посте про приложения для проксирования я написал, что ProxyCap — лучшее решение для компьютеров. Я никогда еще так не ошибался, коллеги, и вот почему...
Проблема в том, что ProxyCap больше подходит для Unix-среды, а на Windows возникают проблемы с драйверами. Из-за этого приходилось каждый день переустанавливать приложение
Уже хотел начинать вайбкодить своё решение, как наткнулся на гениальных…
🎧 OBSIDIAN (3/4) ~ ПЛАГИНЫ
В этом посте про плагины, которые улучшают работу в Обсидиане. Надеюсь, вы до этого поста делали заметки и настроили систему, сформировав четкое представление о том, чего вам не хватает
Раньше я уже делал подборку плагинов и в целом сжатый обзор на обсидиан, можете почитать отсюда. Тогда я только начинал изучать все, сейчас список расширился
❤️ Мой топ плагинов
🤩Daily Notes — встроенны…
🤩 Сделал Twitter красивым
Наконец-то купил галочку для @asynco_dev и немного обновил дизайн профиля. Мне кажется выглядит круто и будет выделяться в ленте, что думаете?
Осталось составить план по тредам, почитать гайды и выбрать направление для постинга. Правда совсем не хочется реплаи хуярить, но наверное иначе никак
https://x.com/asynco_dev — кидайте подписку, интересно кто меня читает. В ответ тоже подпишусь 💗
…
👍18👎5
Signed asynco
Showing the 12 most recent of 20 posts we hold for @in_crypto_info. 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.
Polls
The 2 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 28 January 2026 to 17 June 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank
Citation-graph rank — 197,110 of 1,478,351entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Mentions
Named by 14 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@in_crypto_info named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@asynco_dev named in 3 posts, 8 August 2026 – 13 August 2026
Cite this entry
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 13 August 2026 — this
entry's latest reading, not the date you are reading this.
“Asynco” (@in_crypto_info), 5,306 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/in_crypto_info.
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.