Telegram RegisterThe public register of Telegram
Telegram profile photo for 东星集团业务频道

Channel

东星集团业务频道

@tg111

3 usernames

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

2,149subscribers

-410 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-1001681979475
TypeChannel
Usernames@pp333 @tg111 @xx444
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live31 October 2026
Measurements held66
Confirmed unchanged1 time, most recently 31 October 2026
On Telegramt.me/tg111

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

2,1262,5602,3432,1497 August 202631 October 2026
66 measurements spanning 85 days, net -410. 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 2,061–2,625 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 66
Measured (UTC)SubscribersChange
31 Oct 2026, 07:552,149no change
30 Oct 2026, 17:552,149+2
29 Oct 2026, 19:392,147+2
28 Oct 2026, 07:372,145+6
27 Oct 2026, 09:592,139+1
26 Oct 2026, 20:562,138+12
25 Oct 2026, 04:072,126-5
23 Oct 2026, 12:502,131-2
22 Oct 2026, 06:342,133+3
21 Oct 2026, 08:082,130-2
20 Oct 2026, 07:162,132-3
18 Oct 2026, 16:062,135-1
18 Oct 2026, 02:562,136+2
17 Oct 2026, 16:072,134-3
15 Oct 2026, 17:052,137-3
15 Oct 2026, 02:082,140-1
15 Oct 2026, 01:402,141+2
12 Oct 2026, 11:162,139no change
12 Oct 2026, 06:002,139-2
11 Oct 2026, 15:572,141first reading

Engagement

8 posts held, back to 17 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 4 pages 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 8 posts for this entry, the most recent from 13 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

13 Jul 2026, 12:15 UTC≈1,450 viewsread 13 August 2026

来会议车 下载付 丝滑必过产品 单笔5万 单鱼20万 汇率11 需善后 @nn222 朝阳

11 Jul 2026, 16:09 UTC≈1,670 viewsread 13 August 2026
Photo

独家缴费通道,单笔1-30万。常规色来直盘 单笔1-30万丝滑必须过,🈲️ 河南 江苏 浙江 安徽 新疆 联系人: @nn222 朝阳

11 Jul 2026, 05:45 UTC≈1,660 viewsread 13 August 2026
Photo

电费单码5000,支持连刷,大区有量的来谈包养,付款方式微信支付宝(支持花呗信用卡) @qqqq3 东星

5 Jun 2026, 15:44 UTC≈3,120 viewsread 13 August 2026

无视ab,等额ab, 16-20个点 只要入款不秒死的A卡+有额度B卡 无视ab,等额ab, 只要入款不秒死的A卡+有额度B卡 5万起大量来 无限收 点位:16-20个点 什么卡都可以来问 联系客服 @dxkf000 @dxkf777

28 Apr 2026, 05:44 UTC≈6,110 viewsread 13 August 2026
Photo

简简单单4天800w 每天200+ 大量收人头,送给别的公群破不开的也来 (马上五一节假日开不了营业执照,五一期间有营业执照的人头正常来) 上人联系 @dxkf000 @dxkf777

26 Apr 2026, 19:30 UTC≈5,680 viewsread 13 August 2026
Photo

微信牛户每天稳定在开,三个半小时射满 200 万 收人头 有营业执照的优先 没营业执照的29 号之前落地操作点郑州 天津 上人联系 @dxkf000 @dxkf777

17 Apr 2026, 07:28 UTC≈4,200 viewsread 13 August 2026
Photo

4月2号接到人、从无到有、4月17号完美下车 历经俩个星期(做资料有快有慢、还请各位中介不要催进展) 上人联系客服 @dxkf000 @dxkf777

17 Apr 2026, 07:28 UTC≈3,560 viewsread 13 August 2026
Photo

单人打量最高记录 10000000×0.02=200000 一步步见证奇迹时刻发生、风控了解开、限额了解开!创造辉煌 上人联系客服 @dxkf000 @dxkf777

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

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.

“东星集团业务频道” (@tg111), 2,149 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/tg111.

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.