Telegram RegisterThe public register of Telegram
Telegram profile photo for 东莞公开榜置顶有抽奖 @vcaaa

Channel

东莞公开榜置顶有抽奖 @vcaaa

@dg9876543210

2 usernames

On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

24,526subscribers

+914 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-1002786524229
TypeChannel
Usernames@dg9876543210 @vcaaa
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held65
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/dg9876543210

Topic

Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 2026 and assigned it the closest of 31 fixed categories, at 72% 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 why it has no browse page of its own yet.

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 word for word on 2 other registered channels. 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
@fsmeishi/31 Jul 2026, 13:06 UTC@dg9876543210/1926 · this entry1 Jul 2026, 13:06 UTC1.00under a minute
@fsmeishi/65 Jul 2026, 12:00 UTC@dg9876543210/1932 · this entry5 Jul 2026, 12:00 UTC1.00under a minute
@fsmeishi/86 Jul 2026, 07:11 UTC@dg9876543210/1935 · this entry6 Jul 2026, 07:11 UTC1.00under a minute
@fsmeishi/1010 Jul 2026, 07:00 UTC@dg9876543210/1941 · this entry10 Jul 2026, 07:00 UTC1.00under a minute
@fsmeishi/1213 Jul 2026, 14:39 UTC@dg9876543210/1948 · this entry13 Jul 2026, 14:39 UTC1.00under a minute
@fsmeishi/1316 Jul 2026, 14:00 UTC@dg9876543210/1954 · this entry16 Jul 2026, 14:00 UTC1.00under a minute
Every channel this entry shares post bodies with
ChannelMatching postsText overlapTypical gapPublished first
@fsmeishi6 (6/6 hand-verifiable sample passed)1.00under a minuteeven
@dongguanligongxueyuan5 (5/5 hand-verifiable sample passed)1.003 minutesthis entry (41)

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. 1 of the 4 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 17 comparable posts for this entry, running 30 June 2026 to 7 August 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).

Across the whole group of 3, the earliest publisher we hold is @dg9876543210 — 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 7 August 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.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word 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

23,33824,52623,9327 August 202619 September 2026
65 measurements spanning 42 days, net +914. 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 23,160–24,704 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
19 Sept 2026, 01:5824,526+89
18 Sept 2026, 03:0024,437+154
16 Sept 2026, 19:5824,283+124
16 Sept 2026, 00:1924,159+115
14 Sept 2026, 20:3724,044+71
14 Sept 2026, 06:4023,973+130
13 Sept 2026, 09:5723,843+83
12 Sept 2026, 11:5823,760+107
11 Sept 2026, 12:3723,653+130
10 Sept 2026, 11:4023,523+185
8 Sept 2026, 22:3723,338-9
7 Sept 2026, 06:5423,347no change
5 Sept 2026, 17:4223,347-12
4 Sept 2026, 16:3923,359-1
3 Sept 2026, 19:0023,360-5
2 Sept 2026, 23:1323,365+3
2 Sept 2026, 10:3923,362-14
1 Sept 2026, 20:1423,376-1
1 Sept 2026, 07:5823,377no change
31 Aug 2026, 17:3423,377first reading

Engagement

47 posts held, back to 30 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 62 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.61%
avg views ÷ 24,526 subscribers
Avg views / post
885
9 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
9
of 47 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 3 September 2026
Posts held47 (30 June 20263 September 2026)
Views total7,966
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 11: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.

Recent posts

3 Sept 2026, 04:31 UTC358 viewsread 3 September 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

2 Sept 2026, 04:46 UTC591 viewsread 2 September 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

1 Sept 2026, 04:32 UTC625 viewsread 1 September 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

31 Aug 2026, 07:50 UTC431 viewsread 31 August 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

30 Aug 2026, 03:58 UTC632 viewsread 30 August 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

29 Aug 2026, 05:32 UTC629 viewsread 29 August 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

28 Aug 2026, 04:17 UTC635 viewsread 28 August 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

27 Aug 2026, 05:47 UTC595 viewsread 27 August 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

27 Aug 2026, 05:00 UTC≈3,470 viewsread 3 September 2026
Photo

💐💐💐开奖了💐💐💐 东莞麦当劳联合南城佳欣 @jx7701 白嫖抽奖活动 开奖了! 本期总参与人数: 675 1- 张无忌 获得:700P白嫖卷 必须报告 谨祝中奖用户大吉大利万事顺意

25 Aug 2026, 04:07 UTC≈1,070 viewsread 26 August 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

24 Aug 2026, 04:30 UTC605 viewsread 24 August 2026

资源分区 大朗松山湖 https://t.me/dgyyyzzz 东城南城 https://t.me/dgkkkzzz 长安常平 https://t.me/dgssslll 石龙寮步 https://t.me/dglllbbb 虎门厚街 https://t.me/dghhhmmm 园州 https://t.me/dgjjjzzz 会所 https://t.me/dghhhsss 黄江塘厦 https://t.me/dgtttrrr 公开榜汇总 https://t.me/XiaoChou_66

23 Aug 2026, 11:38 UTC≈4,150 viewsread 3 September 2026
Photo

🎰 东莞麦当劳联合南城佳欣 @jx7701 白嫖抽奖活动 📮 抽奖条件: 🎫 加入-东城南城 🎫 加入-东莞公开榜置顶有抽奖 @vcaaa 🎫 加入-东莞抽奖发布频道 🎫 加入-东莞公开榜 🎫 加入-东莞小丑群(纯公狗)老师禁入 🎫 加入-佳欣 🎁 奖品内容: 700P白嫖卷 必须报告 × 1 💡 活动说明: 中奖联系 @jx7701 炸号无效 中奖退出频道,中奖无效 优惠卷使用要写报告,转让需老师同意 有效期 1周 聊天进 东莞🐶公群 https://t.me/DG66DS 广州羊村 https://t.me/guangzhouyangyang 佛山美食 https://t.me/foshameishi 聊天积分抽白嫖 欢迎进群活跃聊天 📅 开奖日期:(UTC+8) 2026年08月27日 13时00分00秒

Showing the 12 most recent of 47 posts we hold for @dg9876543210. 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 53 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“东莞公开榜置顶有抽奖 @vcaaa” (@dg9876543210), 24,526 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/dg9876543210.

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.