На верификацию КБ, 1 человек из РФ, 10$ Кто раньше никогда не делал! ЛС: @D1998_KYC

Channel
@D1998_KYC - reputation/work
@D1998KYC2_reputation
On this record: Topic · Growth · Engagement · Posts · Cite this entry
571subscribers
-15 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 | -1002297516320 |
|---|---|
| Type | Channel |
| Username | @D1998KYC2_reputation |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 27 October 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 27 October 2026 |
| On Telegram | t.me/D1998KYC2_reputation |
Topic
Hacking & security — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 59% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Oct 2026, 19:18 | 571 | -8 |
| 21 Oct 2026, 09:01 | 579 | -5 |
| 13 Oct 2026, 18:48 | 584 | -7 |
| 3 Oct 2026, 20:18 | 591 | -7 |
| 18 Sept 2026, 19:38 | 598 | -8 |
| 9 Sept 2026, 14:38 | 606 | +4 |
| 30 Aug 2026, 16:17 | 602 | +3 |
| 24 Aug 2026, 00:56 | 599 | +8 |
| 16 Aug 2026, 02:03 | 591 | +5 |
| 8 Aug 2026, 03:19 | 586 | no change |
| 7 Aug 2026, 18:26 | 586 | first reading |
Engagement
20 posts held, back to 20 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
На верификацию Bybit 🇰🇿 Казахстан 15$ ЛС: @D1998_KYC
@D1998_KYC оплатил за связку Фонбет+ пари +. Бетбум.как.всегда красава
+реп @D1998_KYC оплатил кб
@D1998_KYC +rep мужчинский, все фастом без проблем ❤️
@D1998_KYC +реп фастом оплатил вериф кб ракета бомба петарда ❤️
@D1998_KYC +реп оплатил есим
@D1998_KYC + реп оплатил пак документов, всё гуд ❤
🦋 ࿐𝕿𝖍𝖊 𝕷𝖔𝖘𝖙 𝕬𝖓𝖌𝖊𝖑ִֶָ.࿐ активировал(а) ваш чек и получил(а) 🪙 15 USDT (1,195.30 RUB).
@D1998_KYC +репа за байбит , лучший 🤝
Стоп
Без выписки, если что
Showing the 12 most recent of 20 posts we hold for @D1998KYC2_reputation. 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 27 October 2026 — this entry's latest reading, not the date you are reading this.
“@D1998_KYC - reputation/work” (@D1998KYC2_reputation), 571 subscribers as measured 27 October 2026. Telegram Register, tgregister.com/channel/D1998KYC2_reputation.
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.