Telegram RegisterThe public register of Telegram

Channel

Oracle in China

@OracleinChina

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

288subscribers

+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-1001911720040
TypeChannel
Username@OracleinChina
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 live8 August 2026
Measurements held2
On Telegramt.me/OracleinChina

Growth

2887 Aug 2026, 15:25 — 288 subscribers8 Aug 2026, 08:18 — 288 subscribers7 Aug 2026, 15:258 Aug 2026, 08:18
2 measurements taken within a single day. 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 287–289 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 08:18288no change
7 Aug 2026, 15:25288first reading

Engagement

16 posts held, back to 10 December 2024the 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 16 posts for this entry, the most recent from 21 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
11
Links
11

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

12 May 2025, 01:42 UTC≈2,050 viewsread 8 August 2026

lyca查看手机号: 🇩🇰 丹麦:*105# 🇬🇧 英国/🇮🇪 爱尔兰:*132# 🇵🇹 葡萄牙:*122# 🇳🇱 荷兰:*102# 🇳🇴 挪威:*151#

Signed 𝐙𝐈𝐌𝐊

2 Apr 2025, 00:53 UTC≈2,400 viewsread 8 August 2026
Forwarded from @Qiao_blogPhoto

O2/giffgaff wificalling 记录 epdg.epc.mnc010.mcc234.pub.3gppnetwork.org 87.194.8.8 87.194.88.8 87.194.89.8 87.194.9.8

Signed 𝐙𝐈𝐌𝐊

31 Mar 2025, 14:38 UTC≈1,780 viewsread 8 August 2026

#simyo 封车,注册充值仅限ideal付款,n26或bunq等银行可以支付

Signed 𝐙𝐈𝐌𝐊

24 Mar 2025, 18:33 UTC≈1,860 viewsread 8 August 2026
Photo

#vodafone vodafone uk安全下车 前提一定要是号码已转出,未转出号码的账号,客服只会让你打电话退款,大概率无法退款成功。 转出号码之后,账号无法登陆,直接找网页客服提交号码+姓名+pin之后,要求退款,客服会给你发一条链接,点进去填英国卡的卡号日期cvv即可。 等待3-5个工作日即可到账(并不是什么卡都可以用,实测wise uk不行,monzo和myguava都可以)

Signed 𝐙𝐈𝐌𝐊

23 Mar 2025, 07:49 UTC≈1,330 viewsread 8 August 2026
Forwarded from @eSIMhelp

#Elisa #esimplus 爱沙尼亚保号神卡介绍: 🇪🇪eSIM.gg(乌龟电信)(MVNO) 本家为Elisa(TravelSIM) 同eSIM Plus上游 但不会出现Telia运营商(中国大陆无法使用),也不会出现eSIM Plus余额虚标,费用加倍,保号模糊的问题(使用*146*099#可查询真实余额) 保号: 余额变动/接打电话/使用USSD/使用数据流量/发送短信/即可刷新有效期一年 - 目前充值10%额外赠送 资费详情: - 150+国家/地区漫游 - 10次更换设备次数 - 可以在120+国家/地区免费接听全球电话 - 出站IP 🇪🇪Elisa原生家宽 - 台湾无法漫游(如有需求请见Asia号段) 详细见: https://esim.gg/rates/global 补卡: Asia:无法转移,可同设备联网删除后下载 Global:联网删除(限十次) 十次满了/意外删除/设备遗失损毁等情况联系客

Signed 𝐙𝐈𝐌𝐊

20 Mar 2025, 01:59 UTC≈1,360 viewsread 8 August 2026
Photo

#simyo simyo特有的iban换设备大法(在simyo设置中绑定iban超过1周),支持n26,自动跳转n26转账0.01€,跳转回simyo之后即可下载新esim(我是用了模块hookeuicc直接获取了ac),安装完esim之后记得回app点确认安装的按钮,不然新卡会没信号

Signed 𝐙𝐈𝐌𝐊

8 Mar 2025, 09:38 UTC≈2,950 viewsread 8 August 2026
File

File, posted without a caption

Signed 𝐙𝐈𝐌𝐊

7 Mar 2025, 16:09 UTC≈1,530 viewsread 8 August 2026

#simyo #postman 可sms验证,不再需要原生设备 有需要的小伙伴,建议走我aff,直达链接

Signed 𝐙𝐈𝐌𝐊

1 Mar 2025, 10:29 UTC≈2,090 viewsread 8 August 2026

#vodafone de #vowifi 仅德国等部分地区的ip才能解析出ip,实际上没有其他限制,改hosts即可连上vowifi epdg.epc.mnc002.mcc262.pub.3gppnetwork.org 139.7.117.168 epdg.epc.mnc002.mcc262.pub.3gppnetwork.org 139.7.117.169 epdg.epc.mnc002.mcc262.pub.3gppnetwork.org 139.7.117.170

Signed 𝐙𝐈𝐌𝐊

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

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

“Oracle in China” (@OracleinChina), 288 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/OracleinChina.

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.