Telegram RegisterThe public register of Telegram
Telegram profile photo for 上帝世界

Channel

上帝世界

@godworldcom1

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

327subscribers

+38 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-1003940393632
TypeChannel
Username@godworldcom1
CreatedBetween 1 April 2026 and 8 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live3 October 2026
Measurements held7
Confirmed unchanged1 time, most recently 3 October 2026
On Telegramt.me/godworldcom1

Topic

Other / unclassifiable — 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 22 September 2026 and assigned it the closest of 31 fixed categories, at 66% 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

2893273087 August 2026 — 289 subscribers8 August 2026 — 289 subscribers15 August 2026 — 301 subscribers24 August 2026 — 316 subscribers1 September 2026 — 314 subscribers17 September 2026 — 324 subscribers3 October 2026 — 327 subscribers7 August 20263 October 2026
7 measurements spanning 56 days, net +38. 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 283–333 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Oct 2026, 07:00327+3
17 Sept 2026, 11:58324+10
1 Sept 2026, 00:48314-2
24 Aug 2026, 01:12316+15
15 Aug 2026, 09:54301+12
8 Aug 2026, 08:18289no change
7 Aug 2026, 19:13289first reading

Engagement

14 posts held, back to 8 June 2026 — 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 14 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

32 reactions across 12 posts, in 3 distinct kinds. The most used accounts for 84.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤮2784.4%
👎39.38%
❤26.25%

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 12 of the 14 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 32 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 14 most recent posts we hold, published 8 June 2026 to 5 August 2026, 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

1 Aug 2026, 15:53 UTC435 views1 reactionsread 8 August 2026

如果购买后觉得节点不好用且流量使用不超过5GB,上帝世界支持在购买后的24个小时内全额退款

🤮1

29 Jul 2026, 12:29 UTC595 views1 reactionsread 8 August 2026

📢 限时优惠活动通知 由于当前节点流量余量较多,为感谢大家的支持,同时提高资源利用率,我们现推出限时 7折优惠活动。 🎁 优惠码:上帝70% 使用优惠码后,可享受套餐 7 折优惠。 活动期间欢迎大家按需购买,感谢各位用户一直以来的支持与信任。 我们将持续优化线路质量,为大家提供更稳定、更快速的网络体验。

🤮1

28 Jul 2026, 10:27 UTC214 views2 reactionsread 8 August 2026
Forwarded from @ffqchannelFile

#上帝世界 #vless #用户投稿 📊 主观评分 稳定 ★☆☆☆☆ 速度 ★★★☆☆ 延迟 ★★★★☆ 性价比 ★★☆☆☆ (以上评分仅供参考) 😀机场自介: 电信cn2gia,联通9929,移动CMIN2 😀 链接导航 开业:2026.4 官网:点击进入 频道:https://t.me/godworldcom1 群组:https://t.me/godworldcom 套餐:https://t.me/ffqimages/210 2026年4月30日更新 论坛:https://www.ffqla.net/thread-929-1-1.html 😀主观点评 晚高峰测试,这次除了移动速度都不错,之前三网一直很差,建议观望一段时间能够长期稳定这个质量再购买 😀翻翻墙提醒您 任何机场都有跑路可能,建议仅月付,以降低风险。(本消息不针对任何机场)

🤮2

22 Jul 2026, 15:23 UTC478 views1 reactionsread 8 August 2026

📢 节点协议升级通知 为了进一步提升网络稳定性、连接速度以及抗干扰能力,我们将对部分节点进行协议升级。 本次调整内容: 🔄 原 QUIC 协议节点 → VLESS 协议节点 升级后: - ✅ 连接稳定性进一步提升 - ✅ 延迟表现优化 - ✅ 兼容性更好,支持更多客户端 - ✅ 高峰期连接体验有所改善 请各位用户注意: 1. 本次升级无需重新购买套餐,原有流量和到期时间不受影响; 2. 请在客户端内重新更新订阅,获取最新节点配置; 3. 如果更新订阅后仍显示旧节点,请尝试删除旧订阅后重新添加; 4. 部分客户端可能需要重启后才能正常连接。 推荐使用最新版客户端: - Windows:v2rayN / Flclash - Android:sing-box / Flclash - iOS:Shadowrocket / Stash 感谢大家一直以来的支持,我们会持续优化线路质量,为大家提供更稳定、更快速的网络体验。…

🤮1

19 Jul 2026, 14:51 UTC458 views1 reactionsread 8 August 2026

明天所有节点进行维护, 节点维护完毕,请大家更新订阅

🤮1

Showing the 12 most recent of 14 posts we hold for @godworldcom1. 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.

Mentions

Named by 2 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.

Named by

Channels on the register whose posts name this channel's handle.

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

“上帝世界” (@godworldcom1), 327 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/godworldcom1.

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.