Telegram RegisterThe public register of Telegram
Telegram profile photo for BYSGS会所---数据售卖商店

Channel

BYSGS会所---数据售卖商店

@SHUJUKUSGK

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

1,650subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001377288800
TypeChannel
Username@SHUJUKUSGK
CreatedBetween 1 March 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/SHUJUKUSGK

Growth

1,6481,6501,6497 August 2026 — 1,650 subscribers7 August 2026 — 1,650 subscribers7 August 2026 — 1,649 subscribers10 August 2026 — 1,648 subscribers12 August 2026 — 1,650 subscribers7 August 202612 August 2026
5 measurements spanning 5 days. 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 1,648–1,650 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 23:351,650+2
10 Aug 2026, 08:181,648-1
7 Aug 2026, 19:031,649-1
7 Aug 2026, 16:331,650no change
7 Aug 2026, 14:461,650first reading

Engagement

20 posts held, back to 10 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 31 March 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Mar 2026, 14:16 UTC≈3,850 viewsread 7 August 2026

本频道所有数据不再进行售卖!等待伤肝肾通知(不要抱太大希望,很可能回不来了)

31 Mar 2026, 13:12 UTC≈2,040 viewsread 7 August 2026
Forwarded from @SGSYYDSNB

今天是你离开的第一天,我回想了很多关于我们之间的故事。我认为我是一个极其冷血的动物,对于你是否自杀成功与否,我并没有对你的回归抱太大希望。我认为你对这个世界失望透顶,自杀对于你来说甚至是一种享受。当我知道你再也不会回来后,我的大脑告诉我我应该哭泣,去为你难过,但是我并没有这样做,我只是为你的离开感到了遗憾和惋惜。 晚安,伤肝肾

19 Mar 2026, 08:31 UTC≈5,450 viewsread 7 August 2026
File

🤪数据全库:山西政务330W🤪 😡数据字段:名字 身份证 婚姻状态 结婚日期 工作单位 手机号码 登记住址 户籍地址 子女信息 查询状态😡 😪数据质量:超高(未公开未泛滥)😪 🥳商品编号:0122🥳 🥰出售价格:40USDT/280RMB🥰 😄联系方式:@KHCHADANG 😄 😢双向方式:@SHANGGANSHEN_bot 😢 ☺️支持任何担保交易 此数据未泛滥未公开☺️

14 Mar 2026, 03:43 UTC≈5,240 viewsread 7 August 2026
File

🤪数据全库:福建职工1300W🤪 😡数据字段:信用代码 名字 身份证 国籍 地址 手机号码 职位身份😡 😪数据质量:超高(未公开未泛滥)😪 🥳商品编号:0121🥳 🥰出售价格:150USDT/1050RMB🥰 😄联系方式:@KHCHADANG 😄 😢双向方式:@SHANGGANSHEN_bot 😢 ☺️支持任何担保交易 此数据未泛滥未公开☺️

12 Mar 2026, 10:18 UTC≈4,710 viewsread 7 August 2026
File

🤪数据全库:黑龙江政务常用号841W🤪 😡数据字段:姓名 身份证 手机号😡 😪数据质量:超高(未公开未泛滥)😪 🥳商品编号:0120🥳 🥰出售价格:100USDT/700RMB🥰 😄联系方式:@KHCHADANG 😄 😢双向方式:@SHANGGANSHEN_bot 😢 ☺️支持任何担保交易 此数据未泛滥未公开☺️

12 Mar 2026, 07:46 UTC≈4,230 viewsread 7 August 2026
File

🤪数据全库:甘肃法人144W🤪 😡数据字段:注册日期 经营范围 营业期限开始 邮政编码 人民币注册资本 数据来源 法定代表人身份证号 系统ID 注册地址 企业名称 币种 联系手机 登记机关 经营状态 法定代表人 主体ID 所属行业编码 核准日期 企业登记注册类型 联系电话 行业分类 注册资本 营业期限结束 注册号 统一社会信用代码😡 😪数据质量:超高(未公开未泛滥)😪 🥳商品编号:0119🥳 🥰出售价格:50USDT/350RMB🥰 😄联系方式:@KHCHADANG 😄 😢双向方式:@SHANGGANSHEN_bot 😢 ☺️支持任何担保交易 此数据未泛滥未公开☺️

12 Mar 2026, 07:45 UTC≈3,820 viewsread 7 August 2026
File

🤪数据全库:长安汽车100W🤪 😡数据字段:省份 经销商名称 姓名 地址 身份证号码 电话号码 车型型号 车辆识别码 车牌号码😡 😪数据质量:超高(未公开未泛滥)😪 🥳商品编号:0118🥳 🥰出售价格:30USDT/210RMB🥰 😄联系方式:@KHCHADANG 😄 😢双向方式:@SHANGGANSHEN_bot 😢 ☺️支持任何担保交易 此数据未泛滥未公开☺️

11 Mar 2026, 05:55 UTC≈3,700 viewsread 7 August 2026
File

🤪数据全库:四川学籍300W🤪 😡数据字段:姓名 身份证 手机号 学院 班级 地址 专业 学校名字😡 😪数据质量:超高(未公开未泛滥)😪 🥳商品编号:0117🥳 🥰出售价格:30USDT/210RMB🥰 😄联系方式:@KHCHADANG 😄 😢双向方式:@SHANGGANSHEN_bot 😢 ☺️支持任何担保交易 此数据未泛滥未公开☺️

11 Mar 2026, 05:23 UTC≈3,620 viewsread 7 August 2026
File

🤪数据全库:河南医保2200W🤪 😡数据字段:psn号 psn管理代码 编号 姓名 psn名称 别名 性别 出生日期 psn证书类型 证书编号 安全控制码 电话号码 移动电话号码 国籍 国家注册代码 电子邮件地址 邮政编码 首次工作日期 居住国家 居住地址 地址邮政编码 实时管理地址 实时地址 地址邮政编码 居住记录编号 婚姻状况 备注 监管状态 多省份管理标志 管理员类型 返回类型 学历等级 教育背景 专业技能等级 自然资质水平 有效标志 创建时间 更新时间 创建者ID 创建者名称 创建选项编号 选项ID 选项名称 选项时间 选项编号 户籍地址😡 😪数据质量:超高(未公开未泛滥)😪 🥳商品编号:0116🥳 🥰出售价格:230USDT/1610RMB🥰 😄联系方式:@KHCHADANG 😄 😢双向方式:@SHANGGANSHEN_bot 😢 ☺️支持任何担保交易 此数据未泛滥未公开☺️

6 Mar 2026, 12:51 UTC≈3,780 viewsread 7 August 2026
File

🤪数据全库:北京机主1000W🤪 😡数据字段:手机号 姓名 身份证 归属地😡 😪数据质量:超高(未公开未泛滥)😪 🥳商品编号:0115🥳 🥰出售价格:120USDT/840RMB🥰 😄联系方式:@KHCHADANG 😄 😢双向方式:@SHANGGANSHEN_bot 😢 ☺️支持任何担保交易 此数据未泛滥未公开☺️

26 Feb 2026, 17:10 UTC≈4,430 viewsread 7 August 2026
File

🤪数据全库:全国银行2000W🤪 😡数据字段:姓名 身份证 手机号 营业时间 赠送日期 有效期 CVV码 银行卡号 卡类型 性别 区域代码 备用电话 生日😡 😪数据质量:超高(未公开未泛滥)😪 🥳商品编号:0114🥳 🥰出售价格:300USDT/2100RMB🥰 😄联系方式:@KHCHADANG 😄 😢双向方式:@SHANGGANSHEN_bot 😢 ☺️支持任何担保交易 此数据未泛滥未公开☺️

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

Citation-graph rank

Citation-graph rank — 1,065,045 of 1,481,217entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“BYSGS会所---数据售卖商店” (@SHUJUKUSGK), 1,650 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SHUJUKUSGK.

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.