Channel
@cryptobattk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
755subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002552965835 |
|---|---|
| Type | Channel |
| Username | @cryptobattk |
| Description | ❗️Канал создан для розыгрышей и новой информации о подарках Владелец - @Sa4iz1k |
| Created | Between 1 March 2025 and 11 May 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/cryptobattk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 02:00 | 755 | no change |
| 7 Aug 2026, 15:47 | 755 | first reading |
18 posts held, back to 11 May 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 18 posts for this entry, the most recent from 2 July 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 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.
33 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 54.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 18 | 54.5% | |
| 🤯 | 9 | 27.3% | |
| 🔥 | 5 | 15.2% | |
| 🤡 | 1 | 3.03% |
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 8 of the 18 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 33reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 11 May 2025 to 2 July 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.
Лутаем 120-150$+ от ByBit 🔥 В честь листинга токена $SPK, ByBit запустил TS, где новые пользователи могут получить 2500 $SPK Как принять участие? 👨💻 ▪️Регистрируемся на ByBit (По этой ссылке, ещё 100 $SKATE получите) ▪️Проходим КУС 1 ▪️Переходим по ссылке и подтверждаем участие Новые пользователи ▪️Депозитим 100$+ на аккаунт ▪️Торгуем в паре USDT/SPK Первые 1k пользователей, получат по 2500 $SPK на свой аккаун…
🤡1
Опа, тут уже лучше, ~130$ за 213 AP 🫡
Если имеете 211 AP, можете забрать дропчик $ZRC, выходит ~90$/аккаунт 🫡
Слабовато для 207 AP В среднем вышло 90-95$
Для сегодняшнего дропчика $ASRR, нужно иметь 207 AP Клейм будет в 16:00 Так же 3-го июня ожидаем дроп $BDXN + 2-го июня дроп $EDGEN 🔥 — В 19:00 сегодня конец турнира по SUI, если кто-то планирует открутить оборот, у вас есть ещё немного времени 🫡
Как у вас дела по TS $NXPC? Самая большая выплата по TS на данный момент + шортик покормил 🫡
Прямо сейчас проходит заносик в новое IDO 💰 Для участия, нужно иметь 193 AP, что не так уж и много, время есть до 13:00 — Так же ваши 15 баллов, которые снимали ранее за дропы, на 16-й день должны быть возвращены Завтра ожидаем ещё один дроп токенов $ASRR, условия получения будут уже завтра, а сегодня нас ожидают выплаты за TS $NXPC (~1100$ по нынешнему прайсу)
Завтра новое IDO 🥰
Нормик, для сегодняшнего дропа $SOPH нужно 195 AP Alpha торговлю откроют в 15:05
👍1
Такс, что у нас по дропам 👨💻 ByBit насыпал USDT за рулетку, которую мы откручивали ранее, можете проверить свой Reward Hub + а так же ещё вчера выдали токены $ELDE за MegaDrop (Листинг сегодня) IDO на Binance уже идёт как час, нужно было иметь 198 AP, я походу всё таки скип, пул небольшой, буду забирать дроп $PFVS 🫡
Для получения дропа $PFVS, нужно иметь 204 AP Клейм будет в 15:00, я решил забрать дроп $HUMA, так как должны ещё сверху докинуть токенов + забираю дроп $PFVS IDO скипнул, хотя в первую минуту можно было слить в +90$, тоже неплохо 🫡
Сейчас стали доступны новые NFT к улучшению 😃 🎁 5000 ★ can be upgraded for unknown ★ 🎁 50 ★ can be upgraded for unknown ★ 🎁 25 ★ can be upgraded for unknown ★ 🎁 25 ★ can be upgraded for unknown ★ 🎁 10 ★ can be upgraded for unknown ★ 🎁 25 ★ can be upgraded for unknown ★ UPD: виды улучшений в чате
🤯4👍2🔥2
Showing the 12 most recent of 18 posts we hold for @cryptobattk. 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.
Citation-graph rank — 1,054,160 of 1,160,990entries 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.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Crypto Bat 🎁” (@cryptobattk), 755 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/cryptobattk.
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.