Telegram RegisterThe public register of Telegram
Telegram profile photo for 金鼎24h自助搬砖跑F通道

Channel

金鼎24h自助搬砖跑F通道

@luluxizi

On this record: Growth · Engagement · Posts · Citations · Cite this entry

6,444subscribers

-60 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001912845808
TypeChannel
Username@luluxizi
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live11 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/luluxizi

Growth

6,4446,5046,4747 August 2026 — 6,504 subscribers7 August 2026 — 6,500 subscribers10 August 2026 — 6,487 subscribers14 August 2026 — 6,460 subscribers17 August 2026 — 6,456 subscribers21 August 2026 — 6,472 subscribers24 August 2026 — 6,460 subscribers27 August 2026 — 6,472 subscribers31 August 2026 — 6,459 subscribers2 September 2026 — 6,463 subscribers7 September 2026 — 6,459 subscribers11 September 2026 — 6,444 subscribers7 August 202611 September 2026
12 measurements spanning 35 days, net -60. 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 6,435–6,513 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 12:566,444-15
7 Sept 2026, 01:186,459-4
2 Sept 2026, 18:476,463+4
31 Aug 2026, 03:436,459-13
27 Aug 2026, 21:046,472+12
24 Aug 2026, 15:356,460-12
21 Aug 2026, 00:426,472+16
17 Aug 2026, 15:366,456-4
14 Aug 2026, 09:386,460-27
10 Aug 2026, 19:416,487-13
7 Aug 2026, 23:176,500-4
7 Aug 2026, 12:176,504first reading

Engagement

18 posts held, back to 4 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pages of 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 18 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Aug 2026, 17:50 UTC≈1,020 viewsread 12 August 2026

24小时 自动个人操作 完成,不需要押金,一单一回、安全无忧✅

2 Aug 2026, 17:49 UTC≈1,010 viewsread 12 August 2026
Photo

🩲📱💪8.3新客反馈🖕🧪 真正的贫穷,不是口袋空空,是眼界狭隘、不敢行动,眼睁睁看着机会溜走。 ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 点击此处查看操作教学(视频教学 点击此处查看操作教学(视频教学 ✅24小时自助接单平台 https://1.jdkjpay8888.top/ 客服😎: @lulutop0

17 Jul 2026, 19:50 UTC≈1,860 viewsread 12 August 2026

直接自己操作 下单就行 宝子们 24小时自助下单 秒下发 稳定运营3年之久 安全稳定 一个微信一天接1w左右 利润2000+ 长期稳定 可靠

8 Jul 2026, 06:29 UTC≈2,280 viewsread 12 August 2026

维护更新好了宝子们 新来的兄弟看一下置顶教学直接自己操作即可

7 Jul 2026, 14:34 UTC≈2,290 viewsread 12 August 2026

系统更新宝子们 进不去系统网站 不要着急 如果有订单问题 可以截图支付记录 或者订单详情 联系前台接待 为您处理 客服😎: @lulutop0

27 Jun 2026, 22:20 UTC≈2,890 viewsread 12 August 2026

库存补满☑库存补满☑库存补满☑重要的事情说三遍!搞钱的行动起来别再观望📣

10 May 2026, 14:39 UTC≈6,970 viewsread 12 August 2026

宝子们看一下置顶教学,直接自己下单即可!全网独家通道,新注册的wx号直接开干!量管包,钱管赚够!

10 May 2026, 14:38 UTC≈6,810 viewsread 12 August 2026
Photo

😫😏😖5.1新客户反馈 喜欢这种直爽的兄弟 默默自己半个小时做了😀😀多 24小时跑分开户,通道直开, 诚信、 稳定、老品牌! 量足,料干净,点位高,赚钱选金鼎,发财致富的第一步!全网招车队,代理,团队,散户! ⚡️⚡️⚡️⚡️⚡️⚡️⚡️⚡️ 点击此处查看操作教学(视频教学 点击此处查看操作教学(视频教学 ✅24小时自助接单平台 https://1.jdkjpay8888.top/ 客服😎: @lulutop0

7 Apr 2026, 14:12 UTC≈9,460 viewsread 12 August 2026

项目24小时可操作 ,新来的兄弟看一下置顶教学直接自己操作即可 不需要去问客服怎么做 之类的,如有订单问题以及不理解的直接咨询客服请直接表达问题🫡🫡

19 Mar 2026, 13:18 UTC≈10,400 viewsread 12 August 2026
Photo

新客反馈😫😏😖 项目简单来说就是 代收博彩充值的钱 是2道料 赌徒充值之后 这边又经过一次转化成为微信小程序红包.间接到账,将风险降到最低 全网独家通道 没有按头风险 基本0风险 单个wx号一天收1w金额左右 稳定不死号 还有 这边都是小额料 ,做到稳定靠谱 收益可观 风险最低 长期稳定 已经稳定运营3年多 信誉可靠 ----------------------------------- 点击此处查看操作教学(视频教学 ✅24小时自助接单平台 https://1.jdkjpay8888.top/ 客服😎: @lulutop0

Showing the 12 most recent of 18 posts we hold for @luluxizi. 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 4 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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“金鼎24h自助搬砖跑F通道” (@luluxizi), 6,444 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/luluxizi.

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.