Telegram RegisterThe public register of Telegram
Telegram profile photo for 琴Ws/Tg更新频道

Channel

琴Ws/Tg更新频道

@Qin_Ws

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

2subscribers

-28 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-1003952443018
TypeChannel
Username@Qin_Ws
Created19 April 2026 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live13 November 2026
Measurements held5
Confirmed unchanged7 times, most recently 13 November 2026
On Telegramt.me/Qin_Ws

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 54% 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

230167 August 2026 — 30 subscribers8 August 2026 — 28 subscribers11 August 2026 — 28 subscribers15 August 2026 — 23 subscribers30 September 2026 — 2 subscribers7 August 202630 September 2026
5 measurements spanning 54 days, net -28. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Sept 2026, 12:392-21
15 Aug 2026, 10:1323-5
11 Aug 2026, 06:3028no change
8 Aug 2026, 01:4228-2
7 Aug 2026, 19:1730first reading

Engagement

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

Recent posts

27 May 2026, 14:20 UTC181 viewsread 11 August 2026
Photo

📱打美国语音号,价格便宜,现货不多 可现跑!

16 May 2026, 12:53 UTC284 viewsread 11 August 2026
Photo

📱美国语音号!损耗较低,价格冰点 给钱就卖🥰

6 May 2026, 12:55 UTC237 viewsread 11 August 2026

📱摩洛哥,哥伦比亚,南非,印尼【实】,沙特,加拿大,菲律宾个人/商业,冰点价现货秒发!!!

21 Apr 2026, 06:47 UTC503 viewsread 11 August 2026

Ws协议 巴西 西班牙 墨西哥 马来 哥伦 智利 尼泊尔 摩洛哥 南非 安哥拉 现货秒发不排队,另接其他热门国家现跑🥰

19 Apr 2026, 20:37 UTC418 viewsread 11 August 2026

供应各国Ws/Tg协议直登号!Ws企业API超级接粉号,超级蓝标,接全球定制!全球租卡平台,供应多国实卡,可注册各类APP,可高效复接🥰

Showing the 7 most recent of 7 posts we hold for @Qin_Ws. 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 30 September 2026 — this entry's latest reading, not the date you are reading this.

“琴Ws/Tg更新频道” (@Qin_Ws), 2 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/Qin_Ws.

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.