Channel
@dgjpzy
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
14subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001905011070 |
|---|---|
| Type | Channel |
| Username | @dgjpzy |
| Created | 19 May 2023 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dgjpzy |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 02:01 | 14 | no change |
| 10 Aug 2026, 17:47 | 14 | first reading |
2 posts held, back to 19 May 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 2 posts for this entry, the most recent from 29 May 2023. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 August 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.
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 2 | 100.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 1 of the 2 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 2 most recent posts we hold, published 19 May 2023 to 29 May 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
编号: #GD4 已验证 【寻欢时间】：2023年5月13日 【寻欢地点】：#东莞 #南城 【信息来源】：论坛、亲身体验 【服务项目】：鸳鸯浴，漫游，胸推，69式，冰火，口活，爱爱，毒龙 【妹妹数量】：1 【环境设备】：自己开房叫过来的 【营业时间】：加上联系 【价格一览】：1000全套 【安全评估】：98 【服务星级】：★★★★★ 【重点推荐】：性格好，不催人 【联系方式】：👉 VIP用户点击可查看联系方式 👈 点击此处 👉 开通会员 👈 【寻欢细节】：朋友介绍的刚坚持不久的清纯妹妹见到妹妹就认出来了超级爱很清纯，好像剥了壳的鸡蛋白白嫩嫩，回放主动帮我脱衣服 还略带挑逗我 搞得血性大发一把，剥光她衣服贼诱人 奶子很白，奶头粉粉的，吸一口还带着淡淡奶香 叫得很清亮，妹子还帮口了一回，然后要求我干她 这必须满足，一顿操作插得很爽，换了几种姿势都很配合 最后上位出货，小妹被干得远远啪啪的，休息了一下又去洗澡，途中…
👍2
Channel created
Showing the 2 most recent of 2 posts we hold for @dgjpzy. 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.
Citation-graph rank — 1,390,482 of 1,621,120entries 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“东莞精品资源 新模式” (@dgjpzy), 14 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/dgjpzy.
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.