Telegram RegisterThe public register of Telegram
Telegram profile photo for 北京 大圣探店 佳人榜

Channel

北京 大圣探店 佳人榜

@dstdjr

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

59,589subscribers

+9,171 since we began measuring on 6 October 2026

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

Register entry

Telegram ID-1003256210541
TypeChannel
Username@dstdjr
Description管理员 @jingbeiabot 大圣探店男群 @bjdstdb 大圣探店打卡群 @bjdstdd 大圣探店中小项 @dstdzx 大圣探店佳人榜 @dstdjr 大圣探店佳丽总榜 @bjdsji 大圣探店 报告 @bjdstdz 大圣探店导航 @bj51dh <一键关注·大圣探店群组> t.me/addlist/X8j6Hs8uyBgzNDc0
CreatedBetween 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 October 2026
Last confirmed live20 November 2026
Measurements held33
Confirmed unchanged1 time, most recently 20 November 2026
On Telegramt.me/dstdjr

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (qwen3.6:35b-a3b, prompt version 1) read this channel’s own recent posts on 22 October 2026 and assigned it the closest of 31 fixed categories, at 50% 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 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. 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
@dstdjr/6043 · this entry3 Nov 2026, 17:51 UTC@bjdsja/71383 Nov 2026, 17:51 UTC1.00under a minute
@dstdjr/6111 · this entry5 Nov 2026, 16:26 UTC@bjdsja/72385 Nov 2026, 16:27 UTC1.002 minutes
@dstdjr/6256 · this entry8 Nov 2026, 15:26 UTC@bjdsja/74118 Nov 2026, 15:28 UTC1.002 minutes
@dstdjr/6321 · this entry11 Nov 2026, 04:22 UTC@bjdsja/751711 Nov 2026, 04:24 UTC1.002 minutes
@dstdjr/6338 · this entry11 Nov 2026, 15:56 UTC@bjdsja/755311 Nov 2026, 16:00 UTC1.004 minutes
@dstdjr/6441 · this entry15 Nov 2026, 15:47 UTC@bjdsja/773715 Nov 2026, 15:50 UTC1.002 minutes
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
@bjdsja43 (8/8 hand-verifiable sample passed)1.002 minutesthis entry (42–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. 1 of the 1 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 172 comparable posts for this entry, running 4 October 2026 to 20 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 2 channels, the one whose matching posts we hold earliest is @dstdjr — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 21 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 2 registered channels linked by matching posts. 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

50,41859,58955,003.56 October 2026 — 50,418 subscribers6 October 2026 — 50,418 subscribers10 October 2026 — 51,048 subscribers13 October 2026 — 51,855 subscribers15 October 2026 — 51,994 subscribers15 October 2026 — 52,266 subscribers17 October 2026 — 52,593 subscribers18 October 2026 — 52,874 subscribers19 October 2026 — 53,277 subscribers20 October 2026 — 53,596 subscribers20 October 2026 — 53,922 subscribers22 October 2026 — 54,215 subscribers23 October 2026 — 54,524 subscribers24 October 2026 — 54,699 subscribers25 October 2026 — 54,969 subscribers26 October 2026 — 55,219 subscribers27 October 2026 — 55,394 subscribers28 October 2026 — 55,689 subscribers29 October 2026 — 55,972 subscribers30 October 2026 — 56,192 subscribers31 October 2026 — 56,482 subscribers1 November 2026 — 56,865 subscribers2 November 2026 — 57,142 subscribers3 November 2026 — 57,289 subscribers4 November 2026 — 57,580 subscribers5 November 2026 — 57,851 subscribers6 November 2026 — 58,058 subscribers7 November 2026 — 57,611 subscribers9 November 2026 — 57,747 subscribers11 November 2026 — 58,113 subscribers13 November 2026 — 58,544 subscribers16 November 2026 — 59,196 subscribers20 November 2026 — 59,589 subscribers6 October 202620 November 2026
33 measurements spanning 44 days, net +9,171. 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 49,042–60,965 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
20 Nov 2026, 03:0159,589+393
16 Nov 2026, 23:5459,196+652
13 Nov 2026, 13:5158,544+431
11 Nov 2026, 00:4658,113+366
9 Nov 2026, 06:5857,747+136
7 Nov 2026, 23:5557,611-447
6 Nov 2026, 19:4058,058+207
5 Nov 2026, 20:2857,851+271
4 Nov 2026, 20:0957,580+291
3 Nov 2026, 22:0657,289+147
2 Nov 2026, 21:1757,142+277
1 Nov 2026, 20:3556,865+383
31 Oct 2026, 18:5056,482+290
30 Oct 2026, 16:1756,192+220
29 Oct 2026, 15:1855,972+283
28 Oct 2026, 14:4655,689+295
27 Oct 2026, 13:2755,394+175
26 Oct 2026, 12:0655,219+250
25 Oct 2026, 11:1054,969+270
24 Oct 2026, 09:0454,699first reading

Engagement

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

ERR · 30 days
0.388%
avg views ÷ 59,589 subscribers
Avg views / post
231
139 posts measured
Reaction rate
0.348%
reactions ÷ views · ER floor
Posts in window
139
of 220 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 32 of 139 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 21 November 2026
Posts held220 (4 October 2026 – 21 November 2026)
Views total32,170
Reactions total30
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken21 Nov 2026, 11:58 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
≈1,800
Videos
≈267
Links
≈278

Lifetime counters from Telegram’s own channel header, read 21 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
17m 23s
Average length
10s

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

47 reactions across 42 posts, in 3 distinct kinds. The most used accounts for 93.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4493.6%
👍24.26%
🤩12.13%

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

Measured over the 220 most recent posts we hold, published 4 October 2026 to 21 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: 7 of 139 posts held from the last 30 days (5.04%) 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).

21 Nov 2026, 07:05 UTC123 views0 reactionsread 21 November 2026
Photo

😀 #朝阳区 十里河 😉 伊一 😀 800 ✈ @cyiyi95 👋 ✅ 联系请备注 大圣探店 🏷 御姐 鸳鸯浴、水中箫、情趣诱惑、丝袜诱惑、指划、漫游、胸推、舌吻、69、吸蛋蛋、口爆、可上门 😀 主动热情、待哥哥如男朋友、性格温柔、三点粉一线天、皮肤白皙、包裹感十足、小穴紧、水多多、擅长口,可全国空降、可SM、可陪酒、可车震、可野外 群众观点 真实探店 ▶️ @bjqzgd 🔔 课后联系 @jingbeiabot 可进 ✅ 内部群 一键关注·大圣探店群组 😬 @bj51dh

21 Nov 2026, 06:23 UTC156 viewsread 21 November 2026
Video

😀 #全北京 🏷 店家 新开海选私密实体店—实力力荐! ‹ 😃😃 😀😃 📱📱 📱📱 › 😠📱😶‍🌫️😡😡📱📱2️⃣0️⃣😖 服务流程: 🍀深喉😒69+ 🌹舔耳😒鸳鸯浴 玫瑰浴 ☘️口爆😒调教 😒 🌸可摸可亲😒激情舔鲍 制服丝袜~ ❤️{ 各种剧本 } - 🐨新增情景剧本SPA 🐨 🚬🚬🔠🔠🔠📱📱📱📱📱 💜可订制剧本满足您的各种需求💜 ❤️秘书勾引老板❤️老师勾引学生 ❤️年少的白月光❤️ 小姨子勾引姐夫 ❤️ 嫂子勾引兄弟❤️ 儿媳妇勾引公公 更多剧本等你来解锁 主题房,制定角色,制定服装,满足你的所有幻想 专业创作剧本团队不定时更新!!! 🥰客服经理 @lishadaoshi 🌐双向预约 @lishadaoshibot 😁频道介绍 @kkbbccddss 💵 全北京 如有推销办卡立即举报返现500 群众观点 真实探店 ▶️ @bjqzgd 🔔 课后联系 @jingbeiabot 可进 ✅ 内部群

21 Nov 2026, 06:08 UTC141 viewsread 21 November 2026
Photo

😀 #三河市 燕郊 😉 燕郊鸳鸯阁 😀 400 ✈ @zlj12 👋 ✅ 联系请备注 大圣探店 🏷 店家 😀 群众观点 真实探店 ▶️ @bjqzgd 🔔 课后联系 @jingbeiabot 可进 ✅ 内部群 一键关注·大圣探店群组 😬 @bj51dh

20 Nov 2026, 16:00 UTC168 viewsread 21 November 2026
Forwarded from @bjdsjaPhoto

群众观点 真实探店 ▶️ @bjqzgd ▶️ 投稿请联系

20 Nov 2026, 12:55 UTC408 views1 reactionsread 21 November 2026
Photo

😀 #朝阳区 建国路 😉 沐锦 😀 1200 ✈ @shimujin 👋 ✅ 联系请备注 大圣探店 🏷 嫩妹 口交、舌吻、鸳鸯浴 😀 B紧,服务态度系嫩妹!水多!可培育|可调情|可口|可指划 可制服诱惑|可舌吻(口臭不接) 群众观点 真实探店 ▶️ @bjqzgd 🔔 课后联系 @jingbeiabot 可进 ✅ 内部群 一键关注·大圣探店群组 😬 @bj51dh

❤1

20 Nov 2026, 05:43 UTC397 viewsread 20 November 2026
Photo

😀 #朝阳区 三元桥 😉 十七 😀 1500 ✈ @shiqixH123 👋 @shiqiLV520bot ✅ 联系请备注 大圣探店 🏷 大长腿 鸳鸯浴、水中箫、调情、指划、舌吻、口交、69、丝袜诱惑、制服诱惑 😀 来自厦门的妹妹,笔直筷子腿 群众观点 真实探店 ▶️ @bjqzgd 🔔 课后联系 @jingbeiabot 可进 ✅ 内部群 一键关注·大圣探店群组 😬 @bj51dh

19 Nov 2026, 16:00 UTC172 viewsread 20 November 2026
Forwarded from @bjdsjaPhoto

群众观点 真实探店 ▶️ @bjqzgd ▶️ 投稿请联系

19 Nov 2026, 10:29 UTC543 viewsread 20 November 2026
Photo

😀 #朝阳区 京铁瑞园 😉 芸宝 😀 1200 ✈ @yunbaobaoya 👋 @yunbaobaoya_bot ✅ 联系请备注 大圣探店 🏷 嫩妹 鸳鸯浴、调情、指划、舌吻、口交、69、制服诱惑、可外出 😀 服务态度系嫩妹、水多、清纯可爱超级甜妹、情绪价值直接拉满 群众观点 真实探店 ▶️ @bjqzgd 🔔 课后联系 @jingbeiabot 可进 ✅ 内部群 一键关注·大圣探店群组 😬 @bj51dh

19 Nov 2026, 08:36 UTC448 viewsread 20 November 2026
Photo

😀 #朝阳区 双井/地铁站附近 😉 拾一 😀 600 ✈ @shiyi6966 👋 @shiyi6965bot ✅ 联系请备注 大圣探店 🏡:报大圣探店优惠 100 限额 2人/天 需要写反馈 🏷 中小项 SPA、指划、舌滑、丝足、胸推、臀推、口交、69 😀 微胖天花板、服务热情、性格温顺、有要求尽力满足 群众观点 真实探店 ▶️ @bjqzgd 🔔 课后联系 @jingbeiabot 可进 ✅ 内部群 一键关注·大圣探店群组 😬 @bj51dh

19 Nov 2026, 08:35 UTC283 viewsread 19 November 2026
Photo

😀😀摸摸唱KTV-死摸死亲 🔰❎🛗💠⚜️🔱🚭❎✅🈳🚭❇️ 如果你觉得摸摸唱只是喝酒 + 摸一摸😫😫😫😫 🥰那你就真的只体验到了冰山一角。😀😀😀😀 摸,只是最基础的互动。氛围到位,互动才是重点🥰 x各种互动游戏,欢乐不断,包厢里想怎么玩就😫怎么玩,气氛直接拉满! 🥰兄弟聚会、生日小酌、下班放松,来这里图的就是一个开心、尽兴、放松。🥰 来一次,你就知道为什😫么这么多兄弟反复来玩! 提前订房,少排队,早点来选择😫😫 😍😍😍😍😍 😃15011272029 ✈️ @KTV1309 双向请联系机器人🤖:@Beijing9966_bot(也是本人回复) 频道链接📱 :https://t.me/az2134555 QQ:3140222936 #摸摸唱 #单刷 #北京游戏场 #北京荤场 #北京商k #游戏场

18 Nov 2026, 16:00 UTC37 views1 reactionsread 18 November 2026
Forwarded from @bjdsjaPhoto

群众观点 真实探店 ▶️ @bjqzgd ▶️ 投稿请联系

❤1

18 Nov 2026, 14:51 UTC194 views1 reactionsread 18 November 2026
Photo

😀 #朝阳区 广渠路/赛洛城 😉 栗子 😀 1000 ✈ @lizidehao 👋 ✅ 联系请备注 大圣探店 🏷 御姐 鸳鸯浴、指划、调情、舌吻、口交、69、丝袜诱惑、制服诱惑 😀 个人自聊、照片和视频都是本人,以前是美容师,会按摩放松,刚入行水多又紧,性感妩媚、风情万种、所有姿势都积极配合,课室干净整洁、有一次性浴巾、床单、专用私处护理液 群众观点 真实探店 ▶️ @bjqzgd 🔔 课后联系 @jingbeiabot 可进 ✅ 内部群 一键关注·大圣探店群组 😬 @bj51dh

❤1

Showing the 12 most recent of 220 posts we hold for @dstdjr. 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 6 posts on @dstdjr 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
7 October 2026
Most recent seen missing
5 November 2026
Median time before seen missing
27 hours
Seen missing in the last 30 days
2

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

“北京 大圣探店 佳人榜” (@dstdjr), 59,589 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/dstdjr.

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.