Channel
@work13z
On this record: Topic · Growth · Engagement · Posts · Cite this entry
128subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1004219912447 |
|---|---|
| Type | Channel |
| Username | @work13z |
| Created | 1 June 2026 — measured — dated from the channel’s first post |
| First recorded | 9 August 2026 |
| Last confirmed live | 5 November 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 5 November 2026 |
| On Telegram | t.me/work13z |
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 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 the other topics.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Nov 2026, 07:35 | 128 | +1 |
| 26 Sept 2026, 07:21 | 127 | +1 |
| 28 Aug 2026, 20:24 | 126 | +5 |
| 9 Aug 2026, 03:47 | 121 | no change |
| 7 Aug 2026, 19:23 | 121 | first reading |
9 posts held, back to 1 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 9 posts for this entry, the most recent from 31 July 2026. An engagement rate over an empty window would be a number about nothing.
Jalsky | FEEDBACK&REVIEWS 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…»
#WTS - WTS KYC/ACCS Paydo Amazon Bybit N26 Stake Genome Mexc Redotpay OKX Blockchain Hawala Binance Payoneer Outlier Plasma one Wise Coinlist Whop •And many other accounts can provide in bulk ESCROW+/REVIEWS+
#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+
Jalsky | FEEDBACK&REVIEWS pinned Deleted message
Jalsky | FEEDBACK&REVIEWS pinned Deleted message
DONE KYC WHOP ✅
DONE READYMADE MOONPAY SPAIN ✅
Channel name was changed to «Jalsky | FEEDBACK&REVIEWS»
Channel created
Showing the 9 most recent of 9 posts we hold for @work13z. 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.
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 5 November 2026 — this entry's latest reading, not the date you are reading this.
“KYC SHOP FEEDBACK&REVIEW•” (@work13z), 128 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/work13z.
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.