Telegram RegisterThe public register of Telegram
Telegram profile photo for 粉圈大事件(手子免费找资源)

Channel

粉圈大事件(手子免费找资源)

@xtsyk

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Posts · Posts recorded as deleted · Citations · Handles named that no longer answer · Cite this entry

6,980subscribers

-3,955 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-1003199227396
TypeChannel
Username@xtsyk
Description📢本供需频道免费 帮打手、粉商寻找资源发布供求,各类代发、号商、等一系列,关注一下,更新粉圈大事件以及新闻、曝光,全部为免费公益,每天按时发布,有需求寻找资源或 曝光 新闻 请联系帝小天投稿即可 🏅本频道寻付费常驻盘口、大中介 欢迎实力大盘中介入驻 ♻️投稿负责人: @dxtdw ✅粉圈大家庭社群: @xtsyu ✅粉圈纯手子群: @xtsyg
CreatedBetween 1 October 2025 and 31 December 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live9 November 2026
Measurements held41
Confirmed unchanged1 time, most recently 9 November 2026
On Telegramt.me/xtsyk

Topic

Marketing & affiliate — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 8 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@DOODTPE/104537 Aug 2026, 16:21 UTC@xtsyk/2828 · this entry7 Aug 2026, 16:21 UTC1.00under a minute
@xtsyk/2898 · this entry9 Aug 2026, 07:33 UTC@DOODTPE/106189 Aug 2026, 08:34 UTC1.0061 minutes
@xtsyk/2916 · this entry9 Aug 2026, 16:49 UTC@DOODTPE/106799 Aug 2026, 18:01 UTC1.0072 minutes
@DOODTPE/1072110 Aug 2026, 09:24 UTC@xtsyk/3066 · this entry12 Aug 2026, 19:11 UTC1.002 days
@DOODTPE/1097912 Aug 2026, 14:19 UTC@xtsyk/3059 · this entry12 Aug 2026, 14:19 UTC1.00under a minute
@xtsyk/3166 · this entry14 Aug 2026, 15:53 UTC@DOODTPE/1150817 Aug 2026, 20:22 UTC1.003 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@DOODTPE7 (7/7 hand-verifiable sample passed)1.0072 minutesthis entry (6–1)
@FQDSJ5 (5/5 hand-verifiable sample passed)1.0015 daysthis entry (3–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 432 comparable posts for this entry, running 7 August 2026 to 12 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 8 channels, the one whose matching posts we hold earliest is @xtsyk — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 13 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 8 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

6,98010,9518,965.57 August 2026 — 10,935 subscribers8 August 2026 — 10,948 subscribers9 August 2026 — 10,949 subscribers10 August 2026 — 10,951 subscribers11 August 2026 — 10,950 subscribers12 August 2026 — 10,942 subscribers13 August 2026 — 10,945 subscribers14 August 2026 — 10,944 subscribers16 August 2026 — 10,936 subscribers17 August 2026 — 10,929 subscribers18 August 2026 — 10,927 subscribers19 August 2026 — 10,925 subscribers21 August 2026 — 10,916 subscribers22 August 2026 — 10,627 subscribers23 August 2026 — 10,662 subscribers25 August 2026 — 10,545 subscribers26 August 2026 — 10,542 subscribers27 August 2026 — 10,541 subscribers28 August 2026 — 10,542 subscribers29 August 2026 — 10,535 subscribers30 August 2026 — 10,528 subscribers31 August 2026 — 10,521 subscribers1 September 2026 — 10,518 subscribers2 September 2026 — 10,523 subscribers3 September 2026 — 10,521 subscribers5 September 2026 — 10,533 subscribers9 September 2026 — 9,532 subscribers12 September 2026 — 9,533 subscribers16 September 2026 — 9,536 subscribers2 October 2026 — 8,068 subscribers8 October 2026 — 7,948 subscribers13 October 2026 — 7,526 subscribers16 October 2026 — 7,480 subscribers19 October 2026 — 7,467 subscribers22 October 2026 — 7,462 subscribers25 October 2026 — 7,438 subscribers28 October 2026 — 7,422 subscribers1 November 2026 — 7,343 subscribers3 November 2026 — 7,286 subscribers6 November 2026 — 7,167 subscribers9 November 2026 — 6,980 subscribers7 August 20269 November 2026
41 measurements spanning 94 days, net -3,955. 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 6,384–11,547 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 41
Measured (UTC)SubscribersChange
9 Nov 2026, 20:596,980-187
6 Nov 2026, 19:457,167-119
3 Nov 2026, 23:367,286-57
1 Nov 2026, 03:417,343-79
28 Oct 2026, 17:517,422-16
25 Oct 2026, 08:107,438-24
22 Oct 2026, 14:417,462-5
19 Oct 2026, 07:467,467-13
16 Oct 2026, 15:387,480-46
13 Oct 2026, 19:317,526-422
8 Oct 2026, 09:567,948-120
2 Oct 2026, 06:158,068-1,468
16 Sept 2026, 10:429,536+3
12 Sept 2026, 19:199,533+1
9 Sept 2026, 02:589,532-1,001
5 Sept 2026, 19:3810,533+12
3 Sept 2026, 18:2110,521-2
2 Sept 2026, 14:0810,523+5
1 Sept 2026, 10:2510,518-3
31 Aug 2026, 10:2510,521first reading

Engagement

643 posts held, back to 7 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 59 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
0.194%
avg views ÷ 6,980 subscribers
Avg views / post
13.6
106 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
106
of 643 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 14 November 2026
Posts held643 (7 August 2026 – 14 November 2026)
Views total1,437
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 07:07 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

Photos
≈227
Videos
≈5
Links
≈1,140

Lifetime counters from Telegram’s own channel header, read 14 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Video runtime
59s
Average length
59s

Measured directly from 1 video 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 3 of the 643 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 643 most recent posts we hold, published 7 August 2026 to 14 November 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

Telegram’s own ‘edited’ marker: 0 of 106 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

14 Nov 2026, 06:38 UTC4 viewsread 14 November 2026

☹️☹️😂😂☹️☹️ 全平台收粉 价格置顶 无限卡密 常规数据要求 无特殊产值要求 浏览器 微信码 qq码 抖音码 微博码 都能开 抖音全系v转 抖音全系公众号转 陌陌站街 陌陌全系列 陌陌拉群 陌陌闪码 浏览器 陌陌语音厅 陌陌纯动态 陌陌聊天室 楼凤平台 小红书自热粉丝群 陌陌纯动态 V转 Q群转 陌陌拉群 V转 浏览器 陌陌语音厅 V转 浏览器 Q群转 陌陌站街 V转 浏览器 Q群转 色播浏览器 V转 探探动态V转 微信视频号V转 抖音点赞粉丝群V转 公众号 抖音全系列 抖音自热V转 公众号 抖音点赞 抖音热评 抖音橱窗 小红书自热 小红书全…

Signed 毅燊🛫️(全渠道开码)

14 Nov 2026, 05:35 UTC5 viewsread 14 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 有量都可以来聊聊 价格包你满意 可以预付 可以担保 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

Signed 小友 (收色粉)

14 Nov 2026, 04:41 UTC9 viewsread 14 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 Q群后通过也有 有量都可以来聊聊 价格包你满意 可以预付 可以担保 拿着你的实力找我换钱 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

Signed 小友 (收色粉)

13 Nov 2026, 18:25 UTC12 viewsread 14 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 Q群后通过也有 有量都可以来聊聊 价格包你满意 可以预付 可以担保 拿着你的实力找我换钱 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

Signed 小友 (收色粉)

13 Nov 2026, 17:50 UTC11 viewsread 14 November 2026

游戏粉无限来🙃王者 金铲铲 部落冲突来包结算 各种游戏粉都来 单价拉满🙃 15-25拉起来干🙃 其他渠道也可以来测试 不怕高价 粉有量直接来射🙃 🙃@BHNL88888 https://t.me/gtroppo

Signed 不会捏蓝

13 Nov 2026, 13:50 UTC14 viewsread 14 November 2026

游戏粉无限来🙃王者 金铲铲 部落冲突来包结算 各种游戏粉都来 单价拉满🙃 15-25拉起来干🙃 其他渠道也可以来测试 不怕高价 粉有量直接来射🙃 🙃@BHNL88888 https://t.me/gtroppo

Signed 不会捏蓝

13 Nov 2026, 13:41 UTC14 viewsread 14 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 Q群后通过也有 有量都可以来聊聊 价格包你满意 可以预付 可以担保 拿着你的实力找我换钱 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

Signed 小友 (收色粉)

13 Nov 2026, 07:38 UTC13 viewsread 14 November 2026

大量收CPA 能打的来报 包站 包天 大量收CPA 能打的来报 包站 包天 大量收CPA 能打的来报 包站 包天 大量收CPA 能打的来报 包站 包天 📩 TG:@YiShen01

Signed 毅燊🛫️(全渠道开码)

13 Nov 2026, 05:31 UTC16 viewsread 14 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ ⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 有量都可以来聊聊 价格包你满意 可以预付 可以担保 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

Signed 小友 (收色粉)

13 Nov 2026, 04:41 UTC10 viewsread 14 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 Q群后通过也有 有量都可以来聊聊 价格包你满意 可以预付 可以担保 拿着你的实力找我换钱 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

Signed 小友 (收色粉)

12 Nov 2026, 19:29 UTC10 viewsread 14 November 2026

视频号小红书直播抖音系列兼职粉 手工活外发 短剧 无限接带打粉视频来对接

Signed 认准+888! 坤坤

12 Nov 2026, 18:25 UTC13 viewsread 14 November 2026

❤️❤️❤️❤️❤️❤️❤️ ❤️❤️❤️❤️❤️❤️❤️ 🎈全天24小时卡密 Q群 实时隔夜 应有尽有 收一切好粉 支持担保预付 🎈 任何真粉 好粉 Q群 Q群后通过也有 有量都可以来聊聊 价格包你满意 可以预付 可以担保 拿着你的实力找我换钱 大量收地推。收地推域名访问量,所有想做地推打粉得,联系免费扶持,一个粉结账 👊.小友🎈 👊.小乐🎈 👊.力总😀 诚信经营 长久合作

Signed 小友 (收色粉)

Showing the 12 most recent of 643 posts we hold for @xtsyk. 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 recorded as deleted after publishing

We recorded 4 posts on @xtsyk as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
9 August 2026
Median time before seen missing
10 hours
Seen missing in the last 30 days
0

Forward network

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

“粉圈大事件(手子免费找资源)” (@xtsyk), 6,980 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/xtsyk.

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.