жарко конечно

Channel
кабак Nemesis'a
@kabaknemesis
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
279subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002208641474 |
|---|---|
| Type | Channel |
| Username | @kabaknemesis |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/kabaknemesis |
Topic
Gambling & betting — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 64% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 10:39 | 279 | +1 |
| 4 Sept 2026, 16:42 | 278 | -1 |
| 28 Aug 2026, 20:43 | 279 | -1 |
| 15 Aug 2026, 17:57 | 280 | -1 |
| 8 Aug 2026, 08:32 | 281 | no change |
| 7 Aug 2026, 19:30 | 281 | first reading |
Engagement
20 posts held, back to 21 July 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
до 12 числа еще продлили, окно для абуза осталось. нововведения: нужно прожимать Join на вкладке с ивентом(тут уже вшит реф код, для рефбека 40%) не удивлюсь, если еще раз продлят ну и в целом, как будто бы мало людей фри бабос забирают(см. скрин) по хеджу тут можно с бинансом просто лупаситься, потому что одинаковые стаканы(ну я так делаю). вход лимиткой на оранже с рефбеком, потом бинанс маркетом в другую сторону…
подсказка для тех кто в танке
вы знаете что завтра наступает месяц Х?
Заклеймил кто? Ну просто сыновья сами знаете кого P.S. говорили там кус, + транза была+ акк мунпея ахахаха ладно я ревоукаюсь
Photo, posted without a caption
на моб аппке есть кнопка, жду
MoonPay выкатили PayBox - штука, через которую агенты на GPT или Claude могут самостоятельно делать обмены в сети Solana. Подключить и потестить можно тут(это мы не делаем): https://paybox.sh/ На сайте есть видео-гайд, настройка несложная. Ещё вчера за подключение X раздавали дроп в USDC. Насыпало от 10$ до 200–300$, сегодня запустят Wave2(ибо вчера арбузеры все сложили) - это мы делаем. Я уже подключил свои акки…
арк умер до оф лаунча если че это чел рандом, но хз че будет с теми кто завел до оф бриджа
вроде говорят, что рабочий бридж, но не коннектите норм коши, я с бернера бриджу на данный момент копейку https://dyorarc.fun как дойдет кеш, дам апдейт upd: Дошло, все окей
Там на Arc движ по щиткам начался Кидаю копипасту по заводу денег туда Переведете через нейронку Step 1 — Deposit on Base. In your wallet or basescan's Write Contract tab: On USDC: approve(0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE, amount) — amount in 6-decimal units (9,000 USDC = 9000000000). On GatewayWallet: deposit(0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, amount). Step 2 — Wait for finality. ~13–19 min (65 …
Промо продлили еще на +10 дней, но из-за двух индивидуумов которые легчайше спалились на откруте - промку порезали, вместо 20% будет - 10% бонус, но и лузануть, соответственно, нужно меньше. Если раньше надо было 60% от тотал депа влузать, то сейчас нужно 30%. Поэтому, открут стал чуточку быстрее, особенно если крутить не один акк за раз(но аккуратнее, РК сняли, но вот такие минусовые штуки получили все)
Showing the 12 most recent of 20 posts we hold for @kabaknemesis. 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
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 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.
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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“кабак Nemesis'a” (@kabaknemesis), 279 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/kabaknemesis.
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.