Telegram RegisterThe public register of Telegram
Telegram profile photo for 资源出击

Channel

资源出击

@zycj1

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry

16,522subscribers

+1,296 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002253819074
TypeChannel
Username@zycj1
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live28 August 2026
Measurements held21
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/zycj1

Growth

15,22616,52215,8747 August 2026 — 15,226 subscribers7 August 2026 — 15,226 subscribers7 August 2026 — 15,286 subscribers9 August 2026 — 15,369 subscribers10 August 2026 — 15,509 subscribers11 August 2026 — 15,590 subscribers12 August 2026 — 15,626 subscribers13 August 2026 — 15,748 subscribers14 August 2026 — 15,802 subscribers16 August 2026 — 15,947 subscribers17 August 2026 — 16,001 subscribers18 August 2026 — 16,038 subscribers19 August 2026 — 16,138 subscribers20 August 2026 — 16,186 subscribers21 August 2026 — 16,255 subscribers23 August 2026 — 16,261 subscribers24 August 2026 — 16,287 subscribers25 August 2026 — 16,328 subscribers26 August 2026 — 16,391 subscribers27 August 2026 — 16,457 subscribers28 August 2026 — 16,522 subscribers7 August 202628 August 2026
21 measurements spanning 21 days, net +1,296. 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 15,032–16,716 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 21
Measured (UTC)SubscribersChange
28 Aug 2026, 20:2416,522+65
27 Aug 2026, 21:0516,457+66
26 Aug 2026, 18:1616,391+63
25 Aug 2026, 19:0516,328+41
24 Aug 2026, 19:4616,287+26
23 Aug 2026, 06:4916,261+6
21 Aug 2026, 20:2816,255+69
20 Aug 2026, 15:1116,186+48
19 Aug 2026, 13:5516,138+100
18 Aug 2026, 11:0516,038+37
17 Aug 2026, 11:5416,001+54
16 Aug 2026, 03:2215,947+145
14 Aug 2026, 15:1415,802+54
13 Aug 2026, 04:3515,748+122
12 Aug 2026, 03:0515,626+36
11 Aug 2026, 05:5115,590+81
10 Aug 2026, 03:0115,509+140
9 Aug 2026, 01:1015,369+83
7 Aug 2026, 21:4115,286+60
7 Aug 2026, 16:3015,226first reading

Engagement

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

ERR · 30 days
2.27%
avg views ÷ 16,522 subscribers
Avg views / post
375
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 9 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 21 August 2026
Posts held9 (7 March 202621 August 2026)
Views total375
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken28 Aug 2026, 14:16 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.

What this channel posts

Video runtime
1m 35s
Average length
19s

Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

2 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 4 of the 9 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 7 March 2026 to 21 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

21 Aug 2026, 19:44 UTC375 viewsread 28 August 2026
Photo

#福田 #安安 私聊 @anan005 频道 @anan202626 已认证

7 Jul 2026, 09:43 UTC≈2,140 viewsread 28 August 2026
Photo

#福田 #梦瑶 频道 https://t.me/myao66 私聊 @av86855 @av8685 已认证

4 Jul 2026, 19:46 UTC≈1,800 views0 reactionsread 28 August 2026
Photo

┊招┊ ┊聘┊ ┊美女 🚄地址:深圳 🚺急招:住楼安全房 💰工资:日结 日排12到18单,到🖐🏻5k-8k [烟花]进出:无押金 安全可靠 💦年龄:18~28岁形象气质佳 超过看整体 [转圈] 应聘方式:视频 照片 身高 年龄 胖妹 鸽子女 事妈 团队 公主病 改天姐 能上班的联系 非诚勿扰

21 Jun 2026, 16:54 UTC≈2,200 viewsread 28 August 2026

谁有做日租安全房的联系,有开课老师需要

10 Jun 2026, 20:02 UTC≈2,480 viewsread 28 August 2026
Video

🎤深圳商k校长团队(商K,摸摸唱,半真空👙,游戏场👄) 🌆深圳商务场➕小时场均可安排 💸支持U支付(深圳最专业的加密娱乐团队,客户U支付比例达70%) 频道:@qqqzw 微信:18069451619 电报:@XiaoZhang16888 #商K#摸摸唱#可摸可亲#半真空场#游戏场#00后 #可摸可亲#商务招待 #商K一条龙服务。 —————————————————— 商K校长团队永远的宗旨:❤️客户满意度第一

17 May 2026, 06:09 UTC≈2,960 viewsread 28 August 2026
Photo

御姐周老师 频道课表 https://t.me/+HudBiXTGF_U1OTRl 私聊 @zhoulaoshi688 已验证

15 May 2026, 04:55 UTC≈5,860 views1 reactionsread 21 August 2026

#报告模版 出击报告:https://t.me/zycj1 位置:#福田 年龄:22 收费:1400 验证留名:费米 验证时间:5.14 出击体验:本人之前出击过一个人照差很多的老师所以一直很谨慎出击。但是这次很满意,第一眼感觉小师姐本人比照片上还多一丝风韵,事后回味感觉真人比照片还要好看些。老师的🐻又大又圆,居然还不垂,手感也是软软弹弹的,一级棒!小师姐给我穿的是黑色比基尼,很是性感。小师姐这种条件其实穿什么都是好看的。 进门后先老师先放好了水和一次性毛巾,冲完之后用过漱口水,老师帮我擦了后背。接下来就是课表的内容。来的路上说她不是服务型,但是给我下面口的时候特别舒服。服务不多,也不算少,但是细节该有的有,做到位了。服务其实就像烹饪,其价值不在于工序多少,而在于能否精准把握食材本质。小师姐这样的顶级美女正如开水白菜,食材已是顶级,以清汤显真味便是最好。 服务完毕,接着就是和老师爱爱。老师下面很紧。老师给的反馈到位,叫的好听

1

23 Apr 2026, 07:44 UTC≈4,510 views1 reactionsread 21 August 2026

#报告模版 出击报告:https://t.me/zycj1 位置:福田 年龄:24 收费:2000 验证留名:冰 验证时间:4月23 出击体验:再次返食物苏沫了,净身高168左右,身高一点不虚,身材超好:胸是真D关键是手感很好很软!但是视觉上却很挺,虽然高但是一点不壮,手脚细长,非常有模特范儿,皮肤也很白很滑,皮肤质感很强,很细腻,整个人很有高级感。苏沫每次都会让我一个人先进房间,然后花上几分钟时间去换穿性感内衣和丝袜,不得不说苏沫衣品不错(也许是因为身材好使的简单的内衣也充满了高级感——真维密模特),苏沫很有服务意识,前戏服务比较长,温柔而热烈!AA过程就不细说了,要特别赞一下苏沫又白又软的肉肉,真的太香了,一边运动一边啃简直是顶级体验! 联系方式:@sumo256 (关键信息我们会给您打码,需要提供买单记录或约钟记录) (可以是会所资源、也可以是私约资源) 参考上面模版,写好后私发给管理换资源 @zhan

1

7 Mar 2026, 10:48 UTC≈4,290 views0 reactionsread 21 August 2026
Photo

福田 小师姐 私聊 @sanshijie1 频道课表 @sanshijie66 备用频道 https://t.me/+WXzuXUF8U5RjMTE1 已认证

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

Posts edited after publishing

@zycj1 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
21 August 2026
Most recent edit
21 August 2026

Citation-graph rank

Citation-graph rank — 375,449 of 1,623,166entries 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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

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

“资源出击” (@zycj1), 16,522 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/zycj1.

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.