Закрыли сделку в б/у👌

Channel
BLACK GUARDS CRYPTO
@BLACKGUARDSCRYPTO
On this record: Topic · Growth · Engagement · Posts · Cite this entry
3subscribers
-1 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 | -1002325935356 |
|---|---|
| Type | Channel |
| Username | @BLACKGUARDSCRYPTO |
| Created | Between 1 September 2024 and 7 December 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 3 times, most recently 3 October 2026 |
| On Telegram | t.me/BLACKGUARDSCRYPTO |
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 3 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 10 Sept 2026, 12:55 | 3 | -1 |
| 13 Aug 2026, 06:18 | 4 | no change |
| 7 Aug 2026, 14:05 | 4 | first reading |
Engagement
20 posts held, back to 7 December 2024 — 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 9 December 2024. An engagement rate over an empty window would be a number about nothing.
Recent posts
TAIUSDT.P Заходим в сделку👌Вход: по рыночной цене.Тейки: 0.42403, 0.46432, 0.5047.Стоп лосс: 0.318.
1CATUSDT.P Заходим в сделку👌Вход: по рыночной цене.Тейки: 0.002699, 0.002999, 0.0033 Стоп лосс: 0.002173.
Все цели достигнуты 🎯🎯🎯😎
Словили стоп.
CLOUDUSDT.P Заходим в сделку👌Вход: по рыночной цене.Тейки: 0.4883, 0.5398, 0.592. Стоп лосс: 0.3556
ALEOUSDT.P Заходим в сделку👌Вход: по рыночной цене.Тейки: 1.8589, 2.0327, 2.2065. Стоп лосс: 1.4629
MOODENGUSDT.P Заходим в сделку👌Вход: по рыночной цене. Тейки: 0.62417, 0.72863, 0.834. Стоп лосс: 0.43607.
ONDOUSDT.P Заходим в сделку👌Вход: по рыночной цене. Тейки: 1.8644, 2.0153, 2.1671. Стоп лосс: 1.6228
Вторая цель есть 🎯😎 Стоп переводим на первую цель.
Первая цель есть 🎯😎 Стоп переводим в б/у.
SILLYUSDT.P Заходим в сделку👌Вход: по рыночной цене. Тейки: 0.0183, 0.01998, 0.0217. Стоп лосс: 0.01452
Showing the 12 most recent of 20 posts we hold for @BLACKGUARDSCRYPTO. 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“BLACK GUARDS CRYPTO” (@BLACKGUARDSCRYPTO), 3 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/BLACKGUARDSCRYPTO.
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.