Rafsss | feedback&review• pinned «#WTS 🏪 🖥 KYC & READY MADE ALL COUNTRY EU/CIS/ASIA 📱 Airbnb ✅ Airtm 📈 Bybit 📈 Binance 📈 Bitrue 📈 OKX 📈 Bitget 📈 Mexc 📁 Coinbase 📈 Gaetio 📈 Bingx 👥 Bitmart 📞 Bcgame 🖇 Buidlpad 📈 Kucoin ✅ Kraken 🙂 Kast 💋 Cryptocom ✅ Redotpay 👏 Moonpay 📎 Fragment 😚 Pstnet…»
Channel
Rafsss | feedback&review•
@rafsss11zz
On this record: Topic · Growth · Engagement · Posts · Cite this entry
114subscribers
+5 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 | -1004493587546 |
|---|---|
| Type | Channel |
| Username | @rafsss11zz |
| Created | 1 July 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 13 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 6 times, most recently 13 October 2026 |
| On Telegram | t.me/rafsss11zz |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 |
|---|---|---|
| 23 Aug 2026, 11:54 | 114 | +1 |
| 15 Aug 2026, 18:27 | 113 | +4 |
| 9 Aug 2026, 07:32 | 109 | no change |
| 7 Aug 2026, 19:44 | 109 | first reading |
Engagement
4 posts held, back to 1 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 4 posts for this entry, the most recent from 27 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
#WTS WTS-KYC/ACC Kalshi • Redotpay • Hyperbeat Coinbase • OKX • Fragment Mexc • Solcard • HTX • Binance Grvt • Bybit • EPN • Punt Trustyfy • Paypal • Kleos • Pst Cryptocom • Bybit • Sumup Claude • Sumsub • Minipay Dm for others! Price 15-50$ ESCROW
#WTS 🏪 🖥 KYC & READY MADE ALL COUNTRY EU/CIS/ASIA 📱 Airbnb ✅ Airtm 📈 Bybit 📈 Binance 📈 Bitrue 📈 OKX 📈 Bitget 📈 Mexc 📁 Coinbase 📈 Gaetio 📈 Bingx 👥 Bitmart 📞 Bcgame 🖇 Buidlpad 📈 Kucoin ✅ Kraken 🙂 Kast 💋 Cryptocom ✅ Redotpay 👏 Moonpay 📎 Fragment 😚 Pstnet 😶🌫️ Zkme 👍Other account available And other verification Can doing by link / login Just write your request✅ Can work with ads power✅ ESCROW+
Channel created
Showing the 4 most recent of 4 posts we hold for @rafsss11zz. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“Rafsss | feedback&review•” (@rafsss11zz), 114 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/rafsss11zz.
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.