Telegram RegisterThe public register of Telegram
Telegram profile photo for 问鼎起源的粉圈资源

Channel

问鼎起源的粉圈资源

@QYQYGE

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

10,923subscribers

+6,721 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1004394205199
TypeChannel
Username@QYQYGE
CreatedBetween 1 June 2026 and 20 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live13 November 2026
Measurements held33
Confirmed unchanged1 time, most recently 13 November 2026
On Telegramt.me/QYQYGE

Topic

Other / unclassifiable — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 48% 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/179613 Nov 2026, 15:39 UTC@QYQYGE/1838 · this entry3 Nov 2026, 15:40 UTC1.00under a minute
@QYQYGE/1954 · this entry7 Nov 2026, 14:31 UTC@DOODTPE/184757 Nov 2026, 16:32 UTC1.002.0 hours
@DOODTPE/185238 Nov 2026, 04:45 UTC@QYQYGE/1974 · this entry8 Nov 2026, 11:59 UTC1.007.2 hours
@QYQYGE/2013 · this entry9 Nov 2026, 13:24 UTC@DOODTPE/1883410 Nov 2026, 06:05 UTC1.0017 hours
@jygdh/9753 Nov 2026, 15:39 UTC@QYQYGE/1838 · this entry3 Nov 2026, 15:40 UTC1.00under a minute
@QYQYGE/2072 · this entry10 Nov 2026, 15:35 UTC@jygdh/109310 Nov 2026, 15:36 UTC1.00under a minute
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
@DOODTPE11 (8/8 hand-verifiable sample passed)0.992.0 hoursthis entry (6–5)
@jygdh8 (7/8 hand-verifiable sample passed)1.00under a minutethis entry (7–1)

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. 6 of the 6 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 39 comparable posts for this entry, running 2 August 2026 to 13 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. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 14 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

4,20210,9237,562.58 August 2026 — 4,202 subscribers9 August 2026 — 4,352 subscribers12 August 2026 — 4,335 subscribers15 August 2026 — 4,569 subscribers18 August 2026 — 4,828 subscribers21 August 2026 — 5,035 subscribers24 August 2026 — 5,112 subscribers27 August 2026 — 5,324 subscribers30 August 2026 — 5,318 subscribers2 September 2026 — 5,541 subscribers6 September 2026 — 5,793 subscribers11 September 2026 — 6,090 subscribers14 September 2026 — 6,295 subscribers19 September 2026 — 6,760 subscribers29 September 2026 — 7,227 subscribers6 October 2026 — 7,498 subscribers12 October 2026 — 7,741 subscribers15 October 2026 — 7,885 subscribers19 October 2026 — 8,921 subscribers22 October 2026 — 9,509 subscribers25 October 2026 — 9,575 subscribers29 October 2026 — 9,810 subscribers1 November 2026 — 10,035 subscribers2 November 2026 — 10,112 subscribers3 November 2026 — 10,259 subscribers4 November 2026 — 10,359 subscribers5 November 2026 — 10,446 subscribers5 November 2026 — 10,544 subscribers6 November 2026 — 10,604 subscribers8 November 2026 — 10,607 subscribers9 November 2026 — 10,722 subscribers11 November 2026 — 10,811 subscribers13 November 2026 — 10,923 subscribers8 August 202613 November 2026
33 measurements spanning 97 days, net +6,721. 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 3,194–11,931 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
13 Nov 2026, 14:1810,923+112
11 Nov 2026, 02:0910,811+89
9 Nov 2026, 12:1610,722+115
8 Nov 2026, 05:2010,607+3
6 Nov 2026, 23:0610,604+60
5 Nov 2026, 21:4910,544+98
5 Nov 2026, 00:3710,446+87
4 Nov 2026, 00:4110,359+100
3 Nov 2026, 03:4510,259+147
2 Nov 2026, 03:3710,112+77
1 Nov 2026, 06:0910,035+225
29 Oct 2026, 03:099,810+235
25 Oct 2026, 15:289,575+66
22 Oct 2026, 21:019,509+588
19 Oct 2026, 07:078,921+1,036
15 Oct 2026, 22:157,885+144
12 Oct 2026, 18:477,741+243
6 Oct 2026, 06:167,498+271
29 Sept 2026, 11:587,227+467
19 Sept 2026, 05:166,760first reading

Engagement

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

ERR · 30 days
8.71%
avg views ÷ 10,923 subscribers
Avg views / post
951
239 posts measured
Reaction rate
0.206%
reactions ÷ views · ER floor
Posts in window
239
of 255 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. It is computed over the 115 of 239 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 14 November 2026
Posts held255 (20 July 2026 – 14 November 2026)
Views total227,366
Reactions total229
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken14 Nov 2026, 12:38 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
86
Videos
25
Links
19

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. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
1m 12s
Average length
24s

Measured directly from 3 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

264 reactions across 112 posts, in 6 distinct kinds. The most used accounts for 60.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤15960.2%
👍4416.7%
👎3111.7%
🤮145.30%
💩103.79%
😁62.27%

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 130 of the 255 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 264 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 255 most recent posts we hold, published 20 July 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: 10 of 239 posts held from the last 30 days (4.18%) 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, 11:20 UTC284 viewsread 14 November 2026

✨✨✨✨:A组04-编号1004 ✨✨✨✨ ✨✨✨✨✨ 公群链接:https://t.me/+k7GJluX56FkxOWM9 公群业务:天擎集团收色粉 公群负责人: 天擎 😎 公群大全 各类业务 ✨ 问鼎官方人员

Signed 问鼎起源-粉圈负责人 @wdqy

14 Nov 2026, 11:20 UTC291 viewsread 14 November 2026

✨✨✨✨:A组02-编号1002 ✨✨✨✨ ✨✨✨✨✨ 公群链接:https://t.me/+5J9M8IzwSKI5ZDNl 公群业务:虾仁 日收十万 好粉包结 公群负责人: 虾仁 😎 公群大全 各类业务 ✨ 问鼎官方人员

Signed 问鼎起源-粉圈负责人 @wdqy

14 Nov 2026, 10:46 UTC367 views2 reactionsread 14 November 2026

问鼎 01 公群 https://t.me/+jODW6ZUDB8MyNjQ1

👍2

Signed 问鼎起源-粉圈负责人 @wdqy

14 Nov 2026, 00:31 UTC≈1,010 views2 reactionsread 14 November 2026

研究出来了 一天打 2000 粉的协议

❤2

Signed 问鼎起源-粉圈负责人 @wdqy

13 Nov 2026, 22:34 UTC≈1,130 views3 reactionsread 14 November 2026

需要介绍靠谱中介 打粉找不到靠谱老板 价格不理想的 联系起源 @WDQY 帮你找到一个好老板

❤3

Signed 问鼎起源-粉圈负责人 @wdqy

13 Nov 2026, 22:30 UTC986 viewsread 14 November 2026

打 soul 的进来一下 bro 们 以后这个群会是灵魂最大交流群 这个群不上管理 打广告直接飞 https://t.me/soulsf1

Signed 问鼎起源-粉圈负责人 @wdqy

13 Nov 2026, 16:45 UTC≈1,080 views5 reactionsread 14 November 2026

如果我变得很有钱

👍4❤1

Signed 问鼎起源-粉圈负责人 @wdqy

13 Nov 2026, 15:27 UTC≈1,020 views2 reactionsread 14 November 2026

打手贵宾厅才是打手的归宿 什么打手都有 https://t.me/DSGPT9

👍2

Signed 问鼎起源-粉圈负责人 @wdqy

13 Nov 2026, 13:59 UTC898 views1 reactionsread 14 November 2026

✨✨✨✨正式营业 ✨✨✨✨负责人如下 问鼎逍遥 @wdxy 问鼎瓜瓜 @wdgg 问鼎起源 @wdqy 收粉✨✨✨✨✨✨✨起 目前市场主要还是面向粉圈 有其他类业务需要上押可以联系 @wdxy 目前收粉类公群 福利如下 收粉类✨✨✨✨✨起 月租百十 俩月起租 ✨✨✨✨✨以上单月起租 月租百10 公群福利:30 个会员号群发引流流量 给公群➕粉圈流量扶持➕推荐打手工作室 更多细节福利待遇请联系我们 问鼎担保官方大群 问鼎担保验群机器人 @wddbnb_bot 机器人可以用于 验证公群 自助供需 报备资金 等等 如需加入VIP贵宾群请联系 @wdgg 公群上押推广类流量扶持业务联系 @wdqy 公群总负责人投诉联系 @wdxy

❤1

Signed 问鼎起源-粉圈负责人 @wdqy

13 Nov 2026, 12:54 UTC766 views4 reactionsread 14 November 2026

https://t.me/+q0NutDOkz4QyNTU1 问鼎担保的第一个公群

👍3❤1

Signed 问鼎瓜瓜

13 Nov 2026, 12:40 UTC741 viewsread 14 November 2026

回来了有业务来谈 @WDQY 大群新群 打手群 将会管理 严格🈲广告

Signed 问鼎起源-粉圈负责人 @wdqy

Showing the 12 most recent of 255 posts we hold for @QYQYGE. 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 5 posts on @QYQYGE 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
11 November 2026
Most recent seen missing
14 November 2026
Median time before seen missing
22 hours
Seen missing in the last 30 days
5

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

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

“问鼎起源的粉圈资源” (@QYQYGE), 10,923 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/QYQYGE.

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.