Telegram RegisterThe public register of Telegram

Channel

社工库机器人推荐频道

@sgk44444

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

4,079subscribers

-142 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1004290799304
TypeChannel
Username@sgk44444
CreatedBetween 1 May 2026 and 31 July 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 August 2026
On Telegramt.me/sgk44444

Growth

4,0794,2214,1507 August 2026 — 4,221 subscribers8 August 2026 — 4,179 subscribers11 August 2026 — 4,079 subscribers7 August 202611 August 2026
3 measurements spanning 4 days, net -142. 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 4,058–4,242 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 02:554,079-100
8 Aug 2026, 02:414,179-42
7 Aug 2026, 03:154,221first reading

Engagement

29 posts held, back to 1 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 5 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
2.31%
avg views ÷ 4,079 subscribers
Avg views / post
94.4
29 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
29
of 29 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held29 (1 August 20268 August 2026)
Views total2,737
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12:14 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

8 Aug 2026, 04:02 UTC25 viewsread 8 August 2026

📱📱📱📱 好搜录的群组频道导航机器人 #TG必备 #TG搜索机器人 #搜索神器 #中文搜索 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

7 Aug 2026, 06:22 UTC70 viewsread 8 August 2026

📱📱📱📱 Viber云控 营销与客户管理打造的智能云端管理系统 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

7 Aug 2026, 05:26 UTC72 viewsread 8 August 2026

这里不仅是一个信息分享平台,更是一个探索世界的窗口 吃瓜色色 搭子商铺 货多多号铺 萝莉ai脱衣机器人 吃瓜ღ猎奇【抖音吃瓜】 AI星空脱衣换脸机器人 星耀【海外担保】业务大厅 法律危机公关核心业务频道 东南亚新闻华人吃瓜猎奇大曝光 海外社交账户数据筛选平台 混剪小屋🫦 抖音风裸舞抖音曝光 经典国漫动漫🔞同人动漫之家 🌎 柬埔寨华人社区 · 大事件频道 💬东南亚华人社区出海交流群 中文反差萝莉母狗探花偷拍吃瓜🔞 星耀出海 优质供需 海外项目资源 资源搜索 🔍中文搜索 超级索引 全能搜片 全球新闻头条/吃瓜/全网曝光 投稿骗子曝光频道

7 Aug 2026, 03:57 UTC48 viewsread 8 August 2026

📱📱📱📱 新币中文搜机器人 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

7 Aug 2026, 03:56 UTC45 viewsread 8 August 2026

📱📱📱📱 灰太狼社工库 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

7 Aug 2026, 03:56 UTC38 viewsread 8 August 2026

📱📱📱📱 麻豆社工库 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

7 Aug 2026, 03:56 UTC35 viewsread 8 August 2026

📱📱📱📱 白板社工库 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

7 Aug 2026, 03:55 UTC32 viewsread 8 August 2026

📱📱📱📱 老王社工库 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

7 Aug 2026, 03:54 UTC29 viewsread 8 August 2026

📱📱📱📱 暗网免费社工库 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

6 Aug 2026, 15:32 UTC60 viewsread 8 August 2026

📱📱📱📱 星耀【海外担保】业务大厅 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

6 Aug 2026, 13:16 UTC62 viewsread 8 August 2026

📱📱📱📱 伊人集团免费社工库 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

6 Aug 2026, 13:15 UTC54 viewsread 8 August 2026

📱📱📱📱 AI星空脱衣换脸机器人 社工库开户 搜索机器人 涩涩搬运家 💬聊天社群 📣推荐频道 📣备用频道

Showing the 12 most recent of 29 posts we hold for @sgk44444. 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 — 285,557 of 1,160,990entries 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.

Mentions

Named by 2 registered channels — 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.

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

“社工库机器人推荐频道” (@sgk44444), 4,079 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/sgk44444.

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.