2 measurements spanning 3 days. 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 46–48 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
10 Aug 2026, 13:32
47
no change
7 Aug 2026, 11:35
47
first reading
Engagement
20 posts held, back to 21 November 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 20 posts for this entry, the most recent from 12 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
Photos
170
Videos
3
Links
836
Lifetime counters from Telegram’s own channel header, read 10 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
3 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
2
66.7%
👍
1
33.3%
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 3 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 3reactions 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 21 November 2025 to 12 May 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
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @solonikas. 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 21 November 2025 to 12 May 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.
Arc — это L1-блокчейн от Circle, специально созданный под финансы на стейблкоинах.
Он:
— совместим с EVM
— использует USDC как gas-токен (а не ETH)
— уже работает в публичном тестнете, mainnet ожидается позже в 2026
Если вы уже деплоили контракты в Ethereum или других EVM-сетях — всё будет знакомо.
Если нет — этот гайд проведет вас с нуля.
Важный момент
В Arc газ оплачивается в USDC. Тестового ETH здесь нет.
Тестовы…
GRASS Season 2 дроп
Со слов проекта, если вы запускали ноды, фармили поинты по эпохам и делали это регулярно — ваши награды уже на подходе. Ждет награды.
Чем больше поинтов нафармлено → тем больше награда.
У меня была одна нода.
Окно клейма откроется в новом дашборд-кошельке
На Season 2 выделено 170 млн токенов
Фиксированных будущих дропов не будет. Будет важен активность и аптайм
Тут можно проверить поинты.
Ревериф Backpack нужно пройти до 15 Марта
На сегодняшней АМА мелькала дата от Армани 23 Марта, на следующей неделе будет больше инфы.
Вероятность TGE Backpack на Polymarket 95%
Не все аккаунты получилось реверифнуть, да и по премаркету копейки выходят. Некоторые аки даже не трогал, там больше на ревериф сил и денег потрачу, делал ток мейны.
Backpack выкатили токеномику и раскрыл детали распределения
Основные цифры токеномики
▫️Тotal Supply составит 1 млрд токенов.
▫️25% (250 млн) - будут доступны на TGE
▫️24% - выделено на поинты
▫️1% - отдельный дроп для владельцев NFT-коллекции Mad Lads.
Сейчас идет вторая неделя из четырех финальной промо-кампании. В рамках этого этапа среди активных пользователей еженедельно распределяют по 10 млн поинтов, которы…
Очень неплохо вышли, давали вроде от 10000 SKR (120$) до 750000 SKR (97500$) на аккаунт.
Я буквально пару раз что-то делал через Wallet, дроп отбил смартфон второй раз
Если покупали и пользовались, в приложении Wallet на последней вкладке показывает уже сколько токенов $SKR будет у вас дроп)
Клейм и листинг 21 января
Showing the 12 most recent of 20 posts we hold for @solonikas. 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.
Forward network
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.
Mentions
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.
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 10 August 2026 — this
entry's latest reading, not the date you are reading this.
“Крипто Солянка” (@solonikas), 47 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/solonikas.
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.