Telegram RegisterThe public register of Telegram
Telegram profile photo for OLVPS的公告栏 | 官网链接:https://olvps.com

Channel

OLVPS的公告栏 | 官网链接:https://olvps.com

@servert667

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

1,038subscribers

-10 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001126416476
TypeChannel
Username@servert667
Created23 June 2018measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live25 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/servert667

Growth

1,0381,0481,0436 August 2026 — 1,048 subscribers6 August 2026 — 1,048 subscribers9 August 2026 — 1,047 subscribers12 August 2026 — 1,045 subscribers16 August 2026 — 1,044 subscribers18 August 2026 — 1,043 subscribers22 August 2026 — 1,040 subscribers25 August 2026 — 1,038 subscribers6 August 202625 August 2026
8 measurements spanning 19 days, net -10. 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 1,037–1,050 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 04:271,038-2
22 Aug 2026, 09:581,040-3
18 Aug 2026, 23:251,043-1
16 Aug 2026, 02:231,044-1
12 Aug 2026, 08:121,045-2
9 Aug 2026, 18:411,047-1
6 Aug 2026, 12:521,048no change
6 Aug 2026, 02:111,048first reading

Engagement

20 posts held, back to 28 December 2021the 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 20 posts for this entry, the most recent from 3 June 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

3 Jun 2023, 04:45 UTC≈4,960 viewsread 6 August 2026

目前已开始处理退款,请注意原计划原路退回的用户现需要提供 支付宝账户 与 完整对应实名姓名 才可以正常退款,请直接在工单中回复,不要回复邮件内容。 退款最迟将于本月末全部完成,我们将按照提交工单先后顺序进行处理。

17 May 2023, 09:14 UTC≈5,370 viewsread 6 August 2026

关于退款相关内容: 1. 5月份使用支付宝支付的账单,将会通过原路退回(也可选择发送工单,进行工单退款) 2. 账户内存在余额,请发送工单进行退款 3. 账户内存在未结清的aff余额满足提现条件的,请及时提现,并附注收款方式 4. 退款将在6月1日开始进行,此前工单将不会得到回复 5. 关于退款的支付方式,将仅限于支付宝,并需要提供相应实名的完整姓名

17 May 2023, 09:07 UTC≈12,300 viewsread 6 August 2026

由于运营原因,以下产品将于2023年5月31日0时关闭: Khabarovsk VPS 1GB 10IPs Khabarovsk VPS 512MB 5IPs 以下产品组也将一并下架: Leaseweb HK KVM VPS Germany KVM VPS Storage KVM VPS Russia Khabarovsk KVM VPS 请在关闭之前备份您需要的数据以避免数据丢失。我们为此造成的不便和困扰深表歉意。 退款请发送工单,工单中需包含您的支付宝账户和对应的姓名。我们会在产品关闭后尽快处理您的请求。 感谢您的支持和理解。

17 May 2023, 08:52 UTC≈12,300 viewsread 6 August 2026

由于运营原因,以下产品将于2023年5月28日0时关闭: LAX KVM VPS 384MB LAX KVM VPS 768MB LAX KVM VPS 1024MB LAX KVM VPS 2048MB LAX KVM VPS 4096MB 请在关闭之前备份您需要的数据以避免数据丢失。我们为此造成的不便和困扰深表歉意。 退款请发送工单,工单中需包含您的支付宝账户和对应的姓名。我们会在产品关闭后尽快处理您的请求。 感谢您的支持和理解。

15 May 2023, 10:34 UTC≈8,630 viewsread 6 August 2026

由于运营原因,以下产品将于2023年5月24日0时关闭: ZJ KVM VPS 256MB ZJ KVM VPS 512MB ZJG KVM VPS 256MB ZJG KVM VPS 512MB Port Forward 100GB ZaoZhuang Port Froward 100GB(Test) 请在关闭之前备份您需要的数据以避免数据丢失。我们为此造成的不便和困扰深表歉意。 退款请发送工单,工单中需包含您的支付宝账户和对应的姓名。我们会在产品关闭后尽快处理您的请求。 感谢您的支持和理解。

3 May 2023, 08:07 UTC≈8,270 viewsread 6 August 2026

#周年活动 迟来的周年活动,感谢大家多年的支持 1. 首月免费VPS Leaseweb HK VPS Memory 1GB 1*E5 Virtual Core Disk 8GB Bandwidth 1.25TB/Uplink port 1 Gbps 1*IPV4 & 1*IPV6 订购链接:https://olvps.com/cart.php?a=add&pid=87 优惠码: 5C21Y9QYBP *需持有本站产品用户 2. Leaseweb HK VPS 7折永久优惠: 优惠码: 4BSF7ESF1G 订购链接:https://olvps.com/index.php/store/leaseweb-hk-kvm-vps *流量单向计费 3. Russia Khabarovsk KVM VPS 8折永久优惠: 优惠码: 6RD7XK9QKC 订购链接:https://olvps.com/index.php/store/

3 May 2023, 07:54 UTCviews —

Channel name was changed to «OLVPS的公告栏 | 官网链接:https://olvps.com»

5 Apr 2023, 15:51 UTC≈3,060 viewsread 6 August 2026

俄罗斯伯力节点目前已恢复正常,宕机补偿已下发,所有受到影响的客户将收到7天的使用天数。

20 Mar 2023, 17:24 UTC≈3,430 viewsread 6 August 2026

补偿已下发,所有受影响用户将收到21天的延期

6 Mar 2023, 14:53 UTC≈3,770 viewsread 6 August 2026

#维护通知 我们需要弃用原有大硬盘节点的SolusVM架构,转移至Proxmox VE。我们将会转移你的VPS数据,如果你不需要转移,可发送工单要求直接不迁移数据重新开通。 受影响节点:hz80t 维护时间: 2023/3/8 0:00 ~ 未定 可能会受到的影响: 1. 你的IPV6将会被改变 2. 我们将在迁移的时候关闭你的VPS,进行迁移数据。 (注意:你的数据有一定概率丢失,我们只能尽量保留所有数据,如有重要数据,请提前备份。) 我们将在迁移完成后,根据每台VPS宕机的平均时间进行补偿

31 Dec 2022, 16:00 UTC≈3,620 viewsread 6 August 2026

#新年快樂~ 循环8折优惠 UW49I9U8ZW 可购买: Gcore Khabarovsk KVM VPS https://olvps.com/cart.php?gid=10 Leaseweb HK KVM VPS https://olvps.com/cart.php?gid=16 循环8折优惠 8P8QL2FR4L 可購買: United States Los Angeles KVM VPS https://olvps.com/cart.php?gid=25 Germany KVM VPS https://olvps.com/cart.php?gid=23 Storage KVM VPS https://olvps.com/cart.php?gid=17 Germany KVM VPS 384MB 1*AMD 5950X Virtual Core(30%CPU基准) Memory 384MB Disk 5GB NVMe

31 Dec 2022, 08:02 UTC≈4,940 viewsread 6 August 2026

#元旦快乐 感谢大家多年以来的支持,我们为大家提供了一些礼品与优惠。 SSH Port Forward Flexible 端口:3 流量:50GB 节点数量:1 5元每月起 https://olvps.com/cart.php?a=add&pid=119 HRB423LRV8 减免5元优惠券 10个 Leaseweb HK KVM VPS 1GB Memory 1GB 1*E5 Virtual Core Disk 8GB Bandwidth 1.25TB/Uplink port 1 Gbps 1*IPV4 & 1*IPV6 https://olvps.com/cart.php?a=add&pid=87 3QRH32G5UC 减免40元优惠券 10个 可用于购买 2GB套餐 Germany KVM VPS 384MB 1*AMD 5950X Virtual Core(30%CPU基准) Memory 384MB Di

Showing the 12 most recent of 20 posts we hold for @servert667. 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 — 491,861 of 1,603,893entries 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 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.

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

“OLVPS的公告栏 | 官网链接:https://olvps.com” (@servert667), 1,038 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/servert667.

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.