Telegram RegisterThe public register of Telegram
Telegram profile photo for 利万集团资源频道

Channel

利万集团资源频道

@guedasd

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-1003501785715
TypeChannel
Username@guedasd
Created17 January 2026measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live29 August 2026
Measurements held2
On Telegramt.me/guedasd

Growth

17 August 2026 — 1 subscribers15 August 2026 — 1 subscribers7 August 202615 August 2026
2 measurements spanning 7 days. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 02:011no change
7 Aug 2026, 18:141first reading

Engagement

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

What this channel posts

Links
1

Lifetime counters from Telegram’s own channel header, read 15 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.

Recent posts

17 Jan 2026, 16:54 UTC5 viewsread 15 August 2026

🏠😀😀🌍🌍😀😀😀😀 🤔🤔🤔🤔🤔🐛🐛🐛🐛🐛 精聊🌍ZMPC续租率高达100% 精聊T0电商料子全网最牛续租 要求:最低3月活跃账单15+好友 要求:绑手机号实名 账号无限制 用途:绿色引导 精聊电商转三方 😀ZMPC价格:110-150/天续租价格不变,来号商团队130起稳定续租 👩‍👩‍👦‍👦当日成功上号3个奖励58R 👩‍👩‍👦‍👦当日成功上号5个奖励188R 👩‍👩‍👦‍👦当日成功上号10个奖励288R 🎁累计续租10个奖励388R 🎁累计续租20个奖励888R 🎁累计续租50个奖励iPhone17 ——————————————— 精聊QQ🌍账密续租月起30-35/天 要求: 太阳等级 加好友无异常弹窗 精聊钉钉🌍实名满月30-35/天 精聊电商接粉续租稳定. 大量位置 📢另收📱📱📱🥽小红书微博快手闲鱼等等 各类app软件租号一应俱全 资源项目多多 大量来福利拉满 👉集团上号内部结账群👈 ———————————————

Showing the 3 most recent of 3 posts we hold for @guedasd. 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

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 15 August 2026 — this entry's latest reading, not the date you are reading this.

“利万集团资源频道” (@guedasd), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/guedasd.

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.