Telegram RegisterThe public register of Telegram
Telegram profile photo for PornHubSGK

Channel

PornHubSGK

@plcmfsgk

2 usernames

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

177subscribers

+40 since we began measuring on 20 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004290687309
TypeChannel
Usernames@plcmfsgk @qewim
Created8 August 2026 — measured — dated from the channel’s first post
First recorded20 August 2026
Last confirmed live6 November 2026
Measurements held18
Confirmed unchanged3 times, most recently 6 November 2026
On Telegramt.me/plcmfsgk

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 24 September 2026 and assigned it the closest of 31 fixed categories, at 82% 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

137194165.520 August 2026 — 137 subscribers21 August 2026 — 138 subscribers21 August 2026 — 139 subscribers27 August 2026 — 191 subscribers28 August 2026 — 192 subscribers5 September 2026 — 193 subscribers6 September 2026 — 193 subscribers12 September 2026 — 194 subscribers15 September 2026 — 194 subscribers25 September 2026 — 187 subscribers28 September 2026 — 187 subscribers7 October 2026 — 182 subscribers8 October 2026 — 182 subscribers16 October 2026 — 181 subscribers22 October 2026 — 178 subscribers24 October 2026 — 178 subscribers28 October 2026 — 177 subscribers31 October 2026 — 177 subscribers17720 August 202631 October 2026
18 measurements spanning 72 days, net +40. 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”. The vertical axis spans 128–203 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
31 Oct 2026, 10:40177no change
28 Oct 2026, 19:11177-1
24 Oct 2026, 03:47178no change
22 Oct 2026, 15:41178-3
16 Oct 2026, 03:16181-1
8 Oct 2026, 15:20182no change
7 Oct 2026, 00:39182-5
28 Sept 2026, 15:17187no change
25 Sept 2026, 23:39187-7
15 Sept 2026, 02:15194no change
12 Sept 2026, 16:59194+1
6 Sept 2026, 23:37193no change
5 Sept 2026, 15:38193+1
28 Aug 2026, 13:58192+1
27 Aug 2026, 22:15191+52
21 Aug 2026, 04:58139+1
21 Aug 2026, 00:24138+1
20 Aug 2026, 11:00137first reading

Engagement

7 posts held, back to 8 August 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 18 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

18 Aug 2026, 00:02 UTC64 viewsread 20 August 2026

查询间隔改为1000秒,此机器人只用于你社工库,没积分的时候可以来这儿免费查 正式机器人是 @shanghairrr

8 Aug 2026, 16:00 UTC246 viewsread 20 August 2026

🥇免费机器人1号 @plcmfsgk_bot 频道推广赠送机器人特权 查询无时间限制 要求: 频道人数不限 广告浏览超600即可 广告词<点击可复制> 免费高效社工库 无需积分 https://t.me/plcmfsgk_bot 领奖 @PornHubSGKkfbot 找客服拿一个月api

8 Aug 2026, 15:43 UTC182 viewsread 20 August 2026

数据库名称 数据量 综合三要素 12亿 综合二要素 8.2亿 淘宝地址 13亿 顺丰地址 2亿 铁路12306 3.6亿 银行卡四要素 2.6亿 学习通 1.7亿 疫苗接种记录 1.17亿 志愿汇 9000万 4000万随申码 4000万 江苏医保缴费 3128万 河南详细户籍 2100万 宜享花贷款 1762万 云南详细户籍 1600万 陕西一码通 1484万 甘肃户籍地 …

Showing the 7 most recent of 7 posts we hold for @plcmfsgk. 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.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 31 October 2026 — this entry's latest reading, not the date you are reading this.

“PornHubSGK” (@plcmfsgk), 177 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/plcmfsgk.

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.