Telegram RegisterThe public register of Telegram
Telegram profile photo for GD苹果辅助货源网

Channel

GD苹果辅助货源网

@gdwebymy

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

199subscribers

-7 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-1001663689740
TypeChannel
Username@gdwebymy
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live9 October 2026
Measurements held6
Confirmed unchanged1 time, most recently 9 October 2026
On Telegramt.me/gdwebymy

Topic

Software piracy — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 51% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

199206202.57 August 2026 — 206 subscribers8 August 2026 — 206 subscribers7 September 2026 — 205 subscribers15 September 2026 — 203 subscribers29 September 2026 — 201 subscribers9 October 2026 — 199 subscribers7 August 20269 October 2026
6 measurements spanning 64 days, net -7. 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 198–207 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Oct 2026, 22:42199-2
29 Sept 2026, 18:37201-2
15 Sept 2026, 10:16203-2
7 Sept 2026, 11:57205-1
8 Aug 2026, 11:16206no change
7 Aug 2026, 10:27206first reading

Engagement

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

Reaction mix

1 reaction across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1100.0%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 1 of the 9 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 9 most recent posts we hold, published 3 January 2025 to 4 March 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Mar 2025, 10:58 UTC198 viewsread 8 August 2026
Forwarded from @gdxgame

✍️有没有想挣钱的 满16岁 能开闲鱼店铺就可以来 小本 一般一天一包荷花不是问题 运气好一天上百! 售卖本源游戏!我提供,并且送你软件源解锁码永久卡!证书也是低价拿,加盟费180(半年),包回本的 ✈️需要联系我:@GDweb_ios

12 Jan 2025, 07:28 UTC141 viewsread 8 August 2026
Forwarded from @gdxgame

😎😎😎😎😎😎😎😎 🤩招募光遇ios 代理 😄一级代理:180永久 无限出卡 😃二级代理:140永久 500余额 😄三级代理:90永久 200余额 😀😀😀有意联系我:@GDweb_ios 🔄随时更新

6 Jan 2025, 06:30 UTC153 viewsread 8 August 2026
Forwarded from @gdxgameFile

🎁GD和平单绘制【流浪地球】 🎮单绘制稳定奔放! 👻巨魔安装生效,免费公益版本 🔴禁止倒卖 ➡️可专属定制私人端口!200一位!

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

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“GD苹果辅助货源网” (@gdwebymy), 199 subscribers as measured 9 October 2026. Telegram Register, tgregister.com/channel/gdwebymy.

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.