Telegram RegisterThe public register of Telegram
Telegram profile photo for 日结1000-2000绿色🔝微信小程序暴力刷米💰

Channel

日结1000-2000绿色🔝微信小程序暴力刷米💰

@Lpzftd

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

614subscribers

-56 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-1001988259333
TypeChannel
Username@Lpzftd
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live24 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/Lpzftd

Growth

6146706427 August 2026 — 670 subscribers8 August 2026 — 670 subscribers8 August 2026 — 669 subscribers16 August 2026 — 639 subscribers24 August 2026 — 614 subscribers7 August 202624 August 2026
5 measurements spanning 17 days, net -56. 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 606–678 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 13:05614-25
16 Aug 2026, 03:18639-30
8 Aug 2026, 10:51669-1
8 Aug 2026, 02:33670no change
7 Aug 2026, 16:52670first reading

Engagement

12 posts held, back to 2 June 2025the 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 12 posts for this entry, the most recent from 10 January 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Jan 2026, 02:22 UTC473 viewsread 8 August 2026

══╮╭═══════╮ ╭╯叮~𝟐𝟎𝟐𝟔新年好运正在派送💌 ╰⊙═⊙╯╰═⊙═⊙═══⊙╯ 𝟮𝟬𝟮𝟱 𝑩𝒚𝒆 𝑩𝒚𝒆|𝟮𝟬𝟮𝟔 𝑯𝒊 ✨ 和旧日子握个手,和新一年拥个抱, ┌▸🐎𝗛𝗮𝗽𝗽𝘆↝ ²⁰²⁶/₁.₁ 🎉 ╔元╗🏮 元旦启岁 商禧添新 ╚旦╝🧧 事业兴旺 岁岁赢收 🧧马踏祥云福满门 🎆春风得意展宏图 🧨今日元旦 🧧 新年快乐🏮 └▸开心²⁰²⁶ 健康²⁰²⁶ 有钱²⁰²⁶ 又闲²⁰²⁶ 平安²⁰²⁶ 好运²⁰²⁶ 顺利²⁰²⁶ 暴富²⁰²⁶ 祝你 祝我 祝我们都赢在新的一年

28 Dec 2025, 09:13 UTC499 viewsread 8 August 2026

网络进不去 关闭VPN 每天小赚一点 联系客服 @dajin777888

28 Nov 2025, 06:43 UTC≈1,320 viewsread 8 August 2026

上班可以摸摸鱼了 小赚一点 遇到问题可以 联系客服 @dajin777888

19 Nov 2025, 09:11 UTC≈1,690 viewsread 8 August 2026

遇见提现问题 联系客服 @dajin777888 手把手教你如何提现。

19 Nov 2025, 04:41 UTC717 viewsread 8 August 2026
Photo

😊问一万次都不如尝试一次 ⚡️当你在犹豫不决的时候 ⚡️别人已经行动了 ⚡️项目不是天天有 ⚡️兄弟们赶紧扫码去撸 ⚡️赚到钱了 回来给我百分之20分红 新人稳赚输了全额包赔进入平台,按照图中的技巧来撸,在1.5倍左右点击逃跑,不要贪心,每天即可稳赚3000-5000➕ 👆不懂🉐看置顶操作视频👆

20 Aug 2025, 13:46 UTC≈1,540 viewsread 8 August 2026
Photo

来飞机图的啥,不就图的搞两个钱 快速翻身吗?得要有格局;唯一频道 11月带飞 零风险带你暴力搞钱💰上岸扫码干就完了😁😁 ✅扫码打不开的点击下方官方链接🔗 http://dl9icwm.pw/index/dapp/dapp?uu=55107

8 Jul 2025, 10:05 UTC≈2,560 viewsread 8 August 2026
Photo

微信扫码进入平台,按照图中的技巧来撸,在1.5倍左右点击逃跑,不要贪心,每天即可稳赚3000-5000➕ 👆不懂🉐看置顶操作视频👆 ⚠️微信扫码进入需关闭VPN⚠️充值以及扫码页面打不开的情况,需要关闭vpn (梯子)即可!不知道自己是不是新用户可以发ID给客服查询😻 有任何问题联系客服处理➡️

2 Jun 2025, 13:25 UTC≈3,780 viewsread 8 August 2026
Photo

📣近期反馈记录 📣 兄弟们按照频道里的技巧撸。提现秒到账微信的,一个微信每天稳撸1000-2000,不要贪心

Showing the 12 most recent of 12 posts we hold for @Lpzftd. 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 — 994,829 of 1,628,524entries 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 24 August 2026 — this entry's latest reading, not the date you are reading this.

“日结1000-2000绿色🔝微信小程序暴力刷米💰” (@Lpzftd), 614 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/Lpzftd.

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.