Telegram RegisterThe public register of Telegram
Telegram profile photo for VMRack补货极速通知

Channel

VMRack补货极速通知

@VMRackVPS

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

330subscribers

+4 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-1003552743344
TypeChannel
Username@VMRackVPS
CreatedBetween 1 December 2025 and 27 April 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live10 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 10 November 2026
On Telegramt.me/VMRackVPS

Topic

Technology — 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 49% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@vmrack_server/5427 Apr 2026, 07:22 UTC@VMRackVPS/110 · this entry27 Apr 2026, 07:22 UTC1.00under a minute
@vmrack_server/557 May 2026, 08:44 UTC@VMRackVPS/121 · this entry7 May 2026, 09:04 UTC1.0020 minutes
@vmrack_server/5722 Jun 2026, 01:43 UTC@VMRackVPS/123 · this entry22 Jun 2026, 05:19 UTC1.003.6 hours
@vmrack_server/5823 Jun 2026, 01:56 UTC@VMRackVPS/124 · this entry23 Jun 2026, 01:58 UTC1.002 minutes
@vmrack_server/629 Jul 2026, 07:26 UTC@VMRackVPS/125 · this entry9 Jul 2026, 07:51 UTC1.0025 minutes
@vmrack_server/6510 Jul 2026, 10:39 UTC@VMRackVPS/126 · this entry10 Jul 2026, 11:27 UTC1.0047 minutes
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@vmrack_server6 (6/6 hand-verifiable sample passed)1.0023 minutes@vmrack_server (6–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 6 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 19 comparable posts for this entry, running 27 April 2026 to 4 August 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @vmrack_server. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_copy, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

3263303287 August 2026 — 326 subscribers8 August 2026 — 326 subscribers16 August 2026 — 327 subscribers24 August 2026 — 328 subscribers30 August 2026 — 327 subscribers18 September 2026 — 330 subscribers3 October 2026 — 328 subscribers13 October 2026 — 330 subscribers20 October 2026 — 327 subscribers26 October 2026 — 329 subscribers10 November 2026 — 330 subscribers7 August 202610 November 2026
11 measurements spanning 95 days, net +4. 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 325–331 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Nov 2026, 07:05330+1
26 Oct 2026, 15:01329+2
20 Oct 2026, 06:18327-3
13 Oct 2026, 18:38330+2
3 Oct 2026, 19:57328-2
18 Sept 2026, 05:59330+3
30 Aug 2026, 18:02327-1
24 Aug 2026, 09:48328+1
16 Aug 2026, 18:57327+1
8 Aug 2026, 07:19326no change
7 Aug 2026, 18:02326first reading

Engagement

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

Reaction mix

36 reactions across 5 posts, in 5 distinct kinds. The most used accounts for 63.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👎2363.9%
💩719.4%
🤡411.1%
❤12.78%
🔥12.78%

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

Measured over the 20 most recent posts we hold, published 27 April 2026 to 4 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

4 Aug 2026, 09:06 UTC150 viewsread 8 August 2026

VMRack三网精品补货 - L3.VPS.DC2.2C2G.Base • CPU:2 核 • 内存:2 GB • 硬盘:20 GB • 带宽:500 Mbps • 流量:1 TB • 线路:三网精品 (CN2/9929/CMIN2) 💰 价格:$9.99/月 购买链接: https://www.vmrack.net/zh-CN/deploy-new-instance/vps-activation-deals?id=2052274755754471424&ref_code=5jCK6TRfM27

10 Jul 2026, 11:27 UTC356 viewsread 8 August 2026

📢 网络升级完成说明 尊敬的用户: 经过技术团队持续排查、优化及验证,近期网络升级过程中出现的网络丢包问题已完成处理。目前机房网络已恢复稳定运行,我们将持续监控网络状态,确保服务稳定可靠。 本次升级的背景 近期,为进一步提升平台网络质量、稳定性及安全防护能力,我们对机房网络进行了全面升级,包括: 新增核心交换设备,提升网络承载能力; 新增防火墙设备,增强网络安全及 DDoS 防护能力; 优化网络架构及路由策略,为后续业务扩展提供更可靠的基础设施支撑。 本次升级的目标始终是为了提供更稳定、更高性能的网络环境。 问题原因及处理过程 在网络升级过程中,部分用户出现了网络丢包等情况。 技术团队第一时间介入排查,并最终确认问题根因位于防火墙底层模块。在设备厂商提供技术支持后,我们完成了修复方案验证,并顺利完成防火墙内核升级及相关配置优化。 目前,相关问题已完成处理,网络已恢复正常运行。 升级成果 本次升级完成后,平台已完成核心网络设备及网…

9 Jul 2026, 07:51 UTC292 viewsread 8 August 2026

📢 网络设备上架维护通知 尊敬的用户: 为进一步优化机房网络质量,持续完善网络架构,新一批网络设备现已到达机房。技术团队计划于维护窗口内完成设备上架及相关网络调整工作。 🕒 维护时间 2026 年 7 月 10 日 05:00(北京时间) ⏱️ 预计维护时长 约 1-2 小时 ⚠️ 业务影响 维护期间,网络可能出现短暂波动、延迟增加或少量丢包等情况,个别业务可能受到短暂影响。技术团队将尽最大努力缩短维护时间,并降低对用户业务的影响。 🔧 本次维护内容 上架新一批核心网络设备 优化网络架构及路由策略 对近期网络问题进行进一步排查与优化 持续提升网络稳定性、可靠性及整体性能 近期我们已收到部分用户反馈网络丢包等问题,并已确认相关现象。目前技术团队将结合本次设备上架及网络优化,对相关问题进行进一步验证和持续优化。我们将根据后续运行情况持续跟进,并及时同步处理进展。 对于维护期间可能带来的不便,我们深表歉意,感谢您的理解与支持。如您在维…

23 Jun 2026, 01:58 UTC411 views1 reactionsread 8 August 2026

📢 网络升级维护进展通知 尊敬的用户: 在本次网络升级维护过程中,我们发现部分网络服务未能按照预期完成切换,导致部分用户业务仍受到影响。 目前技术团队正在紧急排查并处理相关问题,全力推进网络恢复工作。 ⚠️ 当前状态 * 网络升级工作仍在进行中 * 部分 VPS、独立服务器及相关网络服务可能存在访问异常 * 技术团队已全面介入处理 🔧 故障说明 本次故障发生于网络升级切换过程中,属于计划维护期间出现的异常情况。我们正在逐项排查网络设备、路由及相关配置,确保网络恢复后能够稳定运行。 ⏳ 恢复时间 目前仍在紧急处理中,我们将在获得明确进展后第一时间向大家同步最新情况。 对于本次维护及故障给您带来的不便,我们深表歉意。感谢您的理解与耐心等待。 VMRACK 技术团队

🔥1

22 Jun 2026, 05:19 UTC374 viewsread 8 August 2026

📢 网络升级维护通知 尊敬的用户: 为进一步提升机房网络稳定性、可靠性及安全防护能力,近期我们已完成新一批核心网络设备部署,并对整体网络架构进行了优化升级。 为完成新设备上线及网络架构切换,平台计划进行网络升级维护,具体安排如下: 🕒 维护时间 2026年6月23日 05:00(北京时间) ⏱️ 维护窗口 预计持续约 2 小时 ⚠️ 业务影响 网络切换过程中预计将出现 约 5 分钟的网络中断,届时 VPS、独立服务器及相关网络服务可能暂时无法访问。切换完成后服务将自动恢复,无需用户进行额外操作。 🔧 本次升级内容 新增核心网络设备并正式投入运行 优化机房网络架构与路由策略 提升网络稳定性与整体性能 增强网络扩展能力,为后续资源扩容提供支撑 进一步提升机房 DDoS 防御能力,为用户业务提供更强的安全保障 📈 升级完成后 本次升级将进一步提高网络可靠性、抗攻击能力及未来扩展能力,为用户提供更加稳定、安全的网络环境。 我们将尽最大努…

7 May 2026, 09:04 UTC731 views1 reactionsread 8 August 2026

【公告】新一批计算节点已完成部署|新规格套餐现已正式上线 尊敬的用户: 感谢大家一直以来对 VMRack 的支持与信任。 此前由于部分计算节点资源(尤其内存)持续趋紧,平台已启动新一批计算节点部署计划。目前,相关节点已完成部署与测试,并已正式投入使用。 现有套餐说明 目前现有套餐仍可正常使用,已购买用户不会受到任何影响。 由于部分旧节点资源余量有限,相关套餐后续将根据资源释放情况进行动态补充上架,整体库存将逐步减少。 后续功能计划 随着新计算节点正式上线,平台后续也将持续推进更多网络与资源功能,包括: 多 IP 绑定功能 IPv6 网络支持 内网 NAT 网络功能 网络与带宽持续优化 进一步提升资源灵活性与业务部署能力,为用户提供更加完善的云基础设施服务体验。 感谢各位用户一直以来的理解与支持。 VMRack 团队

❤1

7 May 2026, 08:22 UTC591 views23 reactionsread 8 August 2026

🔥 【重磅补货】L3 精品优化线路 🏢 商家: VMRack 📦 套餐: L3.VPS.1C2G.Base ⚙️ 配置: 1 vCPU | 2GB | 20GB NVMe | 500Mbps | 1000GB/月 🌍 线路: 三网精品各自优化 (CN2 GIA + 9929 + CMIN2) 💰 价格: $49.00/年 ✅ 状态: 🔴 已售罄

👎23

27 Apr 2026, 07:22 UTC797 views0 reactionsread 8 August 2026

【公告】新一批计算节点即将上线|现有套餐库存说明 尊敬的用户: 感谢大家一直以来对 VMRack 的支持与信任。 为保障平台资源的持续供给与整体稳定性,新一批计算节点已完成部署准备,相关资源将于近期陆续上线。 一、关于本次节点上线 随着平台用户规模增长,现有部分计算节点资源(尤其内存)逐步趋紧。为确保服务稳定性,我们已引入新一批计算节点,用于补充后续资源供给。 本批节点将在近期逐步投入使用,并承载后续新增资源的主要供给。 二、现有套餐库存说明 当前在售套餐基于早期节点部署,在当时资源环境下具备较高性价比。随着资源持续消耗,相关节点可用容量已较为有限。 为优先保障已开通用户的稳定使用: 现有套餐不会立即下架 后续将根据资源释放情况进行动态补充上架 三、新规格套餐说明 基于本次新增计算节点,平台将同步上线新规格套餐。 由于今年整体硬件成本有所上涨,新节点对应套餐将在当前成本基础上进行设计,因此在价格与配置…

27 Apr 2026, 04:38 UTC616 views0 reactionsread 8 August 2026

🎉 VPS 库存监控 🏢 商家: VMRack 📦 套餐: L1.VPS.2C4G.Base ⚙️ 配置: 2 vCPU | 4GB | 60GB NVMe | 5Gbps | 4000GB/月 🌍 线路: 美国原生IP (Cogent、Arelion 国际网络) 💰 价格: $46.00/年 ✅ 状态: 🔴 已售罄

27 Apr 2026, 04:08 UTC577 views4 reactionsread 8 August 2026

🎉 VPS 库存监控 🏢 商家: VMRack 📦 套餐: L1.VPS.2C4G.Base ⚙️ 配置: 2 vCPU | 4GB | 60GB NVMe | 5Gbps | 4000GB/月 🌍 线路: 美国原生IP (Cogent、Arelion 国际网络) 💰 价格: $46.00/年 ✅ 状态: 🔴 已售罄

🤡4

27 Apr 2026, 03:37 UTC530 viewsread 8 August 2026

🎉 VPS 库存监控 🏢 商家: VMRack 📦 套餐: L1.VPS.2C4G.Base ⚙️ 配置: 2 vCPU | 4GB | 60GB NVMe | 5Gbps | 4000GB/月 🌍 线路: 美国原生IP (Cogent、Arelion 国际网络) 💰 价格: $46.00/年 ✅ 状态: 🔴 已售罄

27 Apr 2026, 03:07 UTC516 viewsread 8 August 2026

🎉 VPS 库存监控 🏢 商家: VMRack 📦 套餐: L1.VPS.2C4G.Base ⚙️ 配置: 2 vCPU | 4GB | 60GB NVMe | 5Gbps | 4000GB/月 🌍 线路: 美国原生IP (Cogent、Arelion 国际网络) 💰 价格: $46.00/年 ✅ 状态: 🔴 已售罄

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

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 1 registered channel — 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 10 November 2026 — this entry's latest reading, not the date you are reading this.

“VMRack补货极速通知” (@VMRackVPS), 330 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/VMRackVPS.

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.