15 May 2026, 12:14 UTC3 viewsread 14 August 2026
Photo
👍位置: #南城 🤩妃名: #素素 - - - - - - - - - - - - - - - - - - - 🔠P:500 🔠两节课1000 💝特色: #69 #舌吻 #性感 ✍️联系: @susu1523 ⌨️个人频道: https://t.me/susu168865 ⚙️双向: @Dudu15865_bot 📞（东莞新选妃）📞 ✍️选妃出击报告 💌报告上传选妃 ❤️（我要上榜）
Channel
源数据
@dj5464
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
1subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003742427213 |
|---|---|
| Type | Channel |
| Username | @dj5464 |
| Created | Between 1 February 2026 and 15 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 14 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/dj5464 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 18:48 | 1 | no change |
| 7 Aug 2026, 19:19 | 1 | first reading |
Engagement
6 posts held, back to 15 May 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 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 6 posts for this entry, the most recent from 15 May 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- 226
- Videos
- 43
- Links
- 48
Lifetime counters from Telegram’s own channel header, read 14 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.
- Video runtime
- 8s
- Average length
- 8s
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.
Recent posts
15 May 2026, 11:24 UTC2 viewsread 14 August 2026
常平 屁屁 通用优惠券100🎫 PP优惠券200🎫 （限时3天） 老师: @AOX009
15 May 2026, 10:38 UTC2 viewsread 14 August 2026
Photo
位置: #大朗 妃名: #小不点 20岁 厂妹首次下海 身高155cm 体重80斤 小巧可爱 听话能配合 🉑️调教 服务 🈚️套吹箫 舌吻 6⃣️9⃣️ 丝袜制服 亲咪咪 舔蛋蛋 各种姿势 激情爱爱 课费 p400/40分钟 ❤️pp800/80分钟 不外不夜 自备现金 🈲️低素质 庄机 磕药 变态 大鸡鸡 个人频道 https://t.me/xbd1886 私信 @xbd68888 双向 @xiaobudian0bot
15 May 2026, 09:53 UTC1 viewsread 14 August 2026
Photo
妃名: #美慧 位置: #南城 年龄: 06年 体重: 70KG 身高: 167 胸围: 真实F 服务项目: 🉑69 🉑🐍稳 🉑洗澡 🈶制服 🈶JK 🈶制服诱惑 🈶丝袜 🈶高跟鞋👠 激情爱爱 优点🫰🫰🫰 上粉下粉。皮肤细白。嫩。开心果。乖巧懂事。不催不事。配合度百分百。身材丰满喜欢大胸的无脑冲。懂规矩。养课神奇。情商高。娇滴滴。笑盈盈。你学校时的初恋女友。 🈲酒课 🈲猥琐男 🈲粗暴男 🉑夜，有豪华工作室 停车方便 600p40分钟 1200pp80分钟 约课联系 @FF88796 双向机器人 @FF88769bot 个人频道: https://t.me/FF10887
15 May 2026, 09:20 UTC1 viewsread 14 August 2026
Photo
👍位置: #大朗 🤩妃名: #茜茜 - - - - - - - - - - - - - - - - - - - 🔠P:500 🔠两节课1000 💝特色: #黑丝 #性感 #69 ✍️联系: @qianya63 ⌨️个人频道: https://t.me/qianya68 ⚙️双向: @qianya364_bot 📞（东莞新选妃）📞 ✍️选妃出击报告 💌报告上传选妃 ❤️（我要上榜）
15 May 2026, 09:04 UTC1 viewsread 14 August 2026
Photo
👍位置: #大朗 🤩妃名: #小悠 - - - - - - - - - - - - - - - - - - - 🔠P:600 🔠两节课1200 💝特色: #黑丝 #性感 #粉嫩 ✍️联系: @xiaoyou20059 ⌨️个人频道: https://t.me/xiaoyou8889991 ⚙️双向: @xiaoyou2999bot 📞（东莞新选妃）📞 ✍️选妃出击报告 💌报告上传选妃 ❤️（我要上榜）
Showing the 6 most recent of 6 posts we hold for @dj5464. 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
Citation-graph rank — 937,103 of 1,478,351entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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
Names
Channels on the register whose handles appear in this channel's posts.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“源数据” (@dj5464), 1 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/dj5464.
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.