20 Aug 2023, 15:05 UTC≈4,070 viewsread 13 August 2026
联通电信移动【附属卡】接码150-200 联系人 @lanyue819 对接群: https://t.me/+ACUczmhP8FcxMzIx
Channel
揽月集团项目圈
@Lanyue8889
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
379subscribers
+0 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001765884410 |
|---|---|
| Type | Channel |
| Username | @Lanyue8889 |
| Created | Between 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/Lanyue8889 |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 12:46 | 379 | no change |
| 13 Aug 2026, 20:46 | 379 | first reading |
Engagement
20 posts held, back to 12 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 20 posts for this entry, the most recent from 20 August 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 43s
- Average length
- 43s
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
21 Jul 2023, 10:42 UTC≈8,410 viewsread 13 August 2026
项目介绍：揽月 卡接回u 小额代收 点位30%，常规料，来卡商，不空放 单笔1000-3w， 押金500ｕ起 上押贴卡秒射不堵车 来卡商 精聊点位23 料多不罚站 做单联系人：@lanyue819 频道: @lanyue8889
8 Jul 2023, 15:57 UTC≈6,940 viewsread 13 August 2026
支拉机房 速来高通数据 团队来 手工带记录来，大量收质量团 介绍机房团队来拿茶水
8 Jul 2023, 04:00 UTC≈5,930 viewsread 13 August 2026
收千人以上项目群有的来私我
5 Jul 2023, 12:47 UTC≈5,720 viewsread 13 August 2026
新项目速度上车吃肉 微推，高通数据100过80 https://t.me/+8-rmsbv613U0NGZl
5 Jul 2023, 09:38 UTC≈5,580 viewsread 13 August 2026
😃对接看置顶 揽月集团对接 全网累计上压1wu 😃支拉a线收质量机房 😃附属卡短信口拉满轻轻松松 😃租q100咸鱼淘宝筹备 😃快递代发筹备中 😃有妹妹资源的看过来 😃合作联系 出盘互换盘联系 😃揽月专属表情包 😉要求看对接群置顶😉 所有规则均点上方蓝色字体即可 实力毋庸置疑，随时上压拉担保！ 😢有任何项目合作的可以来谈 @lanyue819 @lanyue819bot
5 Jul 2023, 08:50 UTC≈3,750 viewsread 13 August 2026
来个质量机房 1-2w数据 质量好放量
5 Jul 2023, 08:36 UTC≈3,420 viewsread 13 August 2026
红娘 高通数据100过30左右 200起步 对接群 https://t.me/+8-rmsbv613U0NGZl
2 Jul 2023, 09:43 UTC≈3,340 viewsread 13 August 2026
谈合作联系 @lanyue819 互换盘，出盘的联系
2 Jul 2023, 02:32 UTC≈3,270 viewsread 13 August 2026
支拉c线来手工团，带记录来 支d线来机房 脚本
29 Jun 2023, 09:59 UTC≈3,600 viewsread 13 August 2026
项目名称：揽月远程短信口 项目介绍：短信口 新项目 短信口比手机口安全一百倍吊打手机口 主打的就是简单，上完以后可以玩手机互不影响，新型方法不死卡 一卡拉几个小时没问题 价格：150一小时，量大可谈价 联系人： @xiaoze666 @lanyue819 频道: https://t.me/+ACUczmhP8FcxMzIx
21 Jun 2023, 09:26 UTC≈4,360 viewsread 13 August 2026
招色播 色聊 1v1裸聊 举牌 漏点举牌 线下约炮等等的私聊我 等等只要女生详情私聊 @lanyue819
Showing the 12 most recent of 20 posts we hold for @Lanyue8889. 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 — 704,137 of 1,481,306entries 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.
Mentions
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.
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.
“揽月集团项目圈” (@Lanyue8889), 379 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/Lanyue8889.
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.