Telegram RegisterThe public register of Telegram
Telegram profile photo for лудик Kuscalp

Channel

лудик Kuscalp

@kuscalp

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

112subscribers

+17 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-1002402890242
TypeChannel
Username@kuscalp
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live13 October 2026
Measurements held7
Confirmed unchanged2 times, most recently 13 October 2026
On Telegramt.me/kuscalp

Topic

Crypto & trading — 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 26 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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

941121037 August 2026 — 95 subscribers9 August 2026 — 95 subscribers16 August 2026 — 94 subscribers25 August 2026 — 96 subscribers10 September 2026 — 104 subscribers17 September 2026 — 110 subscribers1 October 2026 — 112 subscribers7 August 20261 October 2026
7 measurements spanning 55 days, net +17. 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 91–115 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Oct 2026, 19:57112+2
17 Sept 2026, 23:38110+6
10 Sept 2026, 15:57104+8
25 Aug 2026, 02:3696+2
16 Aug 2026, 19:3994-1
9 Aug 2026, 12:4695no change
7 Aug 2026, 15:1195first reading

Engagement

12 posts held, back to 24 June 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 12 posts for this entry, the most recent from 30 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

25 reactions across 8 posts, in 5 distinct kinds. The most used accounts for 36.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤936.0%
👍832.0%
🤝624.0%
🔥14.00%
🤯14.00%

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 12 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 25 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 12 most recent posts we hold, published 24 June 2026 to 30 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.

Recent posts

30 Jun 2026, 21:21 UTC200 viewsread 9 August 2026
Photo

#ИтогиМесяца Июнь 2026 С кб где-то -2%. Буквально месяц можно описать 3-ей картинкой ахзахах. Понять это можно, если посмотреть на винку. С каждой неделей винрейт растет и повышается качество сетапов. Даже несмотря на разъебы на КАЖДОЙ неделе, получалось закрывать в 0 без кешбека. Сейчас чувствую некую уверенность, хотя совсем недавно говорил про тильт. Надеюсь это не ложная хуйня. По итогу можно сказать, что м…

30 Jun 2026, 21:07 UTC54 viewsread 9 August 2026
Photo

#ИтогиДня 30.06.2026 Конечно не день, а лютый пиздец. Ночью забрал SLX от ндашки и решил полутать отскок по TAC'у. Вроде первые отскоки были лютой халявой, но случился срыв стопов, так как половина снг топов решили скинуться в хаи. Хз нахуя они это сделали, ведь заработали точно не все))). Но все же я сам допустил ошибку, что отскакивал от монеты, у которой есть пробойная формация + сайз межбирж. Да, риски я не кид…

30 Jun 2026, 20:58 UTC29 viewsread 9 August 2026
Photo

норм движуха, на ней отбил эту палку вчерашнюю

29 Jun 2026, 22:53 UTC31 views1 reactionsread 9 August 2026
Photo

как обычно нахуй, сидишь крабишь по копейке ебаной а потом такая хуйня

❤1

29 Jun 2026, 18:28 UTC31 views3 reactionsread 9 August 2026
Photo

начинаю неделю с минуса.😔

❤1👍1🤝1

28 Jun 2026, 20:35 UTC156 views4 reactionsread 9 August 2026
Photo

#ИтогиНедели Гордый 0. На этой неделе было много чего на самом деле и я на многое попал, только есть одно НО. Заключается оно в том, что я попал и на все ситуации, где можно опиздюлится, в частности я имею ввиду пару ножей. Еще было пару обидных мисскликов, которые заруинили весь профит в пятницу. К тому же я мисскликнул в субботу, cлучайно зайдя в падающий SLX на 7 плечей нахуй, но повезло что успел выскользнуть в …

❤2👍1🤝1

27 Jun 2026, 18:27 UTC50 views3 reactionsread 9 August 2026
Photo

нашли лютого алгоса с тимой, cпалю за 1000$

❤1🤝1🤯1

26 Jun 2026, 21:25 UTC41 views3 reactionsread 9 August 2026

ща чет в микротильте, завтра отчеты за два дня напишу, пока не хочу открывать ни терминал, ни тмм

❤1👍1🤝1

25 Jun 2026, 13:12 UTC46 views3 reactionsread 9 August 2026
Photo

Я видимо решил абсолютно всю хуйню схавать подобную

❤1👍1🤝1

24 Jun 2026, 22:49 UTC57 views5 reactionsread 9 August 2026
Photo

перепробой уровня на секунде, моя главная лучшая торговая система, всегда кормит

👍3❤1🔥1

24 Jun 2026, 20:56 UTC53 views3 reactionsread 9 August 2026
Photo

#ИтогиДня 24.06.2026 В начале дня (ночью) опиздюлился на заточке по beat. Мог выходить в микро-минус, но чет тупняк поймал и растянуло на 7 процентов на плечо. Далее получилось отбиться из-за двух ситуаций, даже не думал, что день в плюс получится вырулить.

❤1👍1🤝1

Showing the 12 most recent of 12 posts we hold for @kuscalp. 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.

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 1 October 2026 — this entry's latest reading, not the date you are reading this.

“лудик Kuscalp” (@kuscalp), 112 subscribers as measured 1 October 2026. Telegram Register, tgregister.com/channel/kuscalp.

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.