Channel
@Hello_1024
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
12,443subscribers
+4 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001482339148 |
|---|---|
| Type | Channel |
| Username | @Hello_1024 |
| Description | 这是一个分享VPS资讯以及Linux学习频道。 |
| Created | Between 1 April 2019 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/Hello_1024 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 22:27 | 12,443 | -1 |
| 11 Aug 2026, 20:12 | 12,444 | +2 |
| 9 Aug 2026, 15:21 | 12,442 | +1 |
| 8 Aug 2026, 14:30 | 12,441 | -3 |
| 7 Aug 2026, 14:50 | 12,444 | +2 |
| 6 Aug 2026, 12:41 | 12,442 | +3 |
| 6 Aug 2026, 04:07 | 12,439 | first reading |
19 posts held, back to 11 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 16 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 29 July 2026 |
|---|---|
| Posts held | 19 (11 June 2026 – 29 July 2026) |
| Views total | 28,880 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 03:24 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
ZgoCloud补货洛杉矶三网优化线路，双ISP家宽IP，带宽百兆，支持3天内流量不超过10G全额退款： 双 ISP IP 实例特殊性，IP 有可能送中，会尽量拉回定位；中国大陆三网回程优化 9929&cmin2，去程接入 NTT，因此去程无法优化。不支持以上理由申请退款。 电信、联通9929 + 移动CMIN2 1 Core AMD 1 GB DDR4 RAM 10G NVMe SSD 1 IPV4 500G/Month/100Mbps $58 USD / Year 购买：https://clients.zgovps.com/?cmd=cart&action=add&affid=153&id=146 2 Cores AMD 2 GB DDR4 RAM 20G NVMe SSD 1 IPV4 1T/Month/100Mbps $108 USD / Year 购买：https://clients.zgovps.com/?c…
ZgoCloud新上德国三网9929线路机型，上游netlab，支持3天内流量不超过10G全额退款： 线路：三网回程9929，更适合北方用户 1 Core AMD 1 GB DDR4 RAM 10G NVMe SSD 1 IPV4 1T/Month/200Mbps $45 USD / Year 购买：https://clients.zgovps.com/?cmd=cart&action=add&affid=153&id=160 2 Cores AMD 2 GB DDR4 RAM 20G NVMe SSD 1 IPV4 2T/Month/200Mbps $88 USD / Year 购买：https://clients.zgovps.com/?cmd=cart&action=add&affid=153&id=161 德国9929详细评测：https://1024.day/d/4054
DMIT HKG EBv2 产品线停止服务，也就是香港CMI产品线 - 2026 年 8 月 10 日正式停产并停止服务 - 按剩余时间退回账户或原支付网关(超6个月只能到账户) - 提供20%以上的折扣码用来购买DMIT的其它服务 留意DMIT服务邮件
giffgaff卡国内大面积封号，疑似不允许长期漫游的原因，你的号还好吗？
搬瓦工机场JMS新增vless协议与Clash订阅 由知名VPS服务商搬瓦工推出的 “机场” Just My Socks 近期宣布，新增支持 Mihomo / Clash.Meta YAML 订阅链接。 此外，JMS 机场还对 s801 节点推出了重大更新：已将其切换至 vless/reality 协议。其余五个节点依然保持Shadowsocks/VMess协议，公告中未提及是否会更换协议。 5.2%优惠码： JMS9272283 购买：https://justmysocks.net/members/aff.php?aff=26977&gid=1
Speedtest逐步换上新界面了，找不见单线程，可以访问：https://single.speedtest.net/ 顺便还能看到老界面。
ZgoCloud补货新洛杉矶三网精品线路机，上游netlab，机器总体还是不错的，支持3天内流量不超过10G全额退款： 线路：CN2 + 9929 + CMIN2 1 Core AMD 1 GB DDR4 RAM 10G NVMe SSD 1 IPV4 500G/Month/200Mbps $52 USD / Year 购买：https://clients.zgovps.com/?cmd=cart&action=add&affid=153&id=134 2 Cores AMD 2 GB DDR4 RAM 20G NVMe SSD 1 IPV4 1T/Month/200Mbps $96 USD / Year 购买：https://clients.zgovps.com/?cmd=cart&action=add&affid=153&id=136 详细评测： https://1024.day/d/3774
DMIT 洛杉矶Pro和EB套餐补货了 洛杉矶Pro套餐，三网CN2GIA： 1C / 2G / 20G SSD / 1T 流量每月 / 10.9刀每月 https://www.dmit.io/aff.php?aff=1538&pid=253 —- 洛杉矶EB套餐，9929 + CMIN2 1C / 2G / 20G SSD / 1.5T 流量每月 / 10.9刀每月 https://www.dmit.io/aff.php?aff=1538&pid=259 更多套餐请见： https://1024.day/d/3916
KVM Januscape 漏洞：虚拟机可逃逸宿主机，潜伏 16 年 安全研究人员公开了 Januscape（CVE-2026-53359）漏洞，这是首个能同时在 Intel 与 AMD 平台上触发的 KVM/x86 虚拟机逃逸漏洞。该漏洞源于 shadow MMU 模拟中的 use-after-free 缺陷，客户机仅通过内部操作即可破坏宿主机内核的 shadow page，直接威胁公有云等多租户 KVM 宿主机的隔离边界。 该漏洞影响范围横跨 2010 年至 2026 年 6 月，在 Linux 内核中潜伏约 16 年，曾被用作 Google kvmCTF 的 0-day 攻击。其 PoC 代码已发布，可在客户机内触发宿主机内核 panic。此外，在 RHEL 等发行版中，本地普通用户还可利用该缺陷提权至 root。 https://github.com/V4bel/Januscape 不少商家正在维护、修复这个漏洞…
DMIT 现已支持在产品控制面板的“计费”选项卡内自助提交退款申请，提交后将由客服进行审核，审核完成后自动完成退款，不再需要提交工单。
ZgoCloud补货新洛杉矶三网精品线路机，上游netlab，机器总体还是不错的，支持3天内流量不超过10G全额退款： 线路：CN2 + 9929 + CMIN2 1 Core AMD 1 GB DDR4 RAM 10G NVMe SSD 1 IPV4 500G/Month/200Mbps $52 USD / Year 购买：https://clients.zgovps.com/?cmd=cart&action=add&affid=153&id=134 2 Cores AMD 2 GB DDR4 RAM 20G NVMe SSD 1 IPV4 1T/Month/200Mbps $96 USD / Year 购买：https://clients.zgovps.com/?cmd=cart&action=add&affid=153&id=136 详细评测： https://1024.day/d/3774
DMIT深夜补货亚太地区机器，有需要的可以看看 日本三网CN2GIA： 1C / 1G / 20G SSD / 500G / $21.9每月 https://www.dmit.io/aff.php?aff=1538&pid=138 —- 香港三网CN2GIA： 1C / 1G / 20G SSD / 500G / $39.9每月 https://www.dmit.io/aff.php?aff=1538&pid=265 更多补货套餐如下： https://1024.day/d/3916
Showing the 12 most recent of 19 posts we hold for @Hello_1024. 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 — 682,424 of 1,160,990entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“1024社区 | 1024.day” (@Hello_1024), 12,443 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/Hello_1024.
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.