Testing the 55 USD Hong Kong plan I won earlier in the Neburst group lottery. 
This 55 USD price is actually based on the original 69.9 USD quarterly price plus a limited 20% lottery coupon. Bandwidth is only 500Mbps; if DC switching is implemented later, it should be fairly interesting to play with.
Contents
1. Configuration
2. Node Quality
3. Mainland Three-Network Outbound Route Tests
4. Mainland Three-Network TCP Ping
5. Evening Peak Direct Single-Thread Speed Tests
6. International Connectivity
7. Summary
1. Configuration
| Plan | 🇭🇰 Neburst S3N-1C1G-Special |
|---|---|
| Location | China, Hong Kong |
| CPU | 1 x AMD EPYC 7Y43 vCores |
| RAM | 1GB |
| Disk | 20GB |
| Traffic | 500GB(out) |
| Bandwidth | 500Mbps |
| Route | Telecom 163PP/Unicom10099/Mobile CMIN2 |
| Network | 1 x IPv4, 1 x /64 IPv6 |
| Price | Quarterly USD$55.92 |
Update: Unicom has been changed to 9929 return, but the test data is still 10099<->4837.
Provider website: https://neburst.com
Looking Glass: https://neburst.com/looking-glass
🔗 Quick Links
| YABS | Node Quality | Mixed Benchmark | nws.sh | Streaming Unlock |
|---|---|---|---|---|
| [Link] | [Link | [Link] | [Link] | [Link] |
It is also a member of the Sakura family.
| IPv4 | IPv6 |
|---|---|
2. Node Quality
bash <(curl -sL https://run.NodeQuality.com)
💻 Basic Information
Basic System Information:
---------------------------------
Uptime : 0 days, 0 hours, 33 minutes
Processor : AMD EPYC 7Y43 48-Core Processor
CPU cores : 1 @ 2549.998 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 929.7 MiB
Swap : 976.5 MiB
Disk : 21.0 GiB
Distro : Debian GNU/Linux 12 (bookworm)
Kernel : 6.12.57+deb13-cloud-amd64
VM Type : STANDARD PC (Q35 + ICH9, 2009)
IPv4/IPv6 : ✔ Online / ✔ Online
IPv6 Network Information:
---------------------------------
ISP : Neburst LLC
ASN : Unknown
Host : Neburst LLC
Location : Fountain, Colorado (CO)
Country : United States
fio Disk Speed Tests (Mixed R/W 50/50) (Partition -):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 281.76 MB/s (70.4k) | 2.12 GB/s (33.2k)
Write | 282.51 MB/s (70.6k) | 2.14 GB/s (33.4k)
Total | 564.28 MB/s (141.0k) | 4.27 GB/s (66.7k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 2.28 GB/s (4.4k) | 2.29 GB/s (2.2k)
Write | 2.40 GB/s (4.7k) | 2.45 GB/s (2.3k)
Total | 4.69 GB/s (9.1k) | 4.75 GB/s (4.6k)
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 1205
Multi Core | 1096
Full Test | https://browser.geekbench.com/v5/cpu/23987942
SysBench CPU Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
1 Thread Test (Single Core) Score: 3855 Scores
SysBench Memory Test (Fast Mode, 1-Pass @ 5sec)
---------------------------------
Single-Thread Read Test: 45311.25 MB/s
Single-Thread Write Test: 26116.87 MB/s
🎬IP Quality
| IPv4 | IPv6 |
|---|---|
🌐 Network Quality
| IPv4 | IPv6 |
|---|---|
📍Return Routes
Return: China Telecom 163PP, China Unicom 10099->4837, China Mobile CMIN2.
| IPv4 | IPv6 |
|---|---|
3. Mainland Three-Network Outbound Route Tests (itdog.cn, 2025-12-21)
Outbound: China Telecom 163, China Unicom 4837->10099, China Mobile CMI.
| Location | China Telecom | China Unicom | China Mobile |
|---|---|---|---|
| Beijing | |||
| Shanghai | |||
| Guangzhou |
4. mainland ChinaThree-Network TCP Ping(itdog.cn, 2025-12-21 20:00)
| China Telecom | China Unicom | China Mobile |
|---|---|---|
5. Evening Peak Direct Single-Thread Speed Tests (2025-12-21 21:00-23:00)
Very stable. Single-thread speeds on all three networks basically reach 470Mbps+ at best, and latency is also excellent.
The speed-test charts also include data from comparable 1G-port models. 
*Click the test record links to view speed-test screenshots, including several popular models as references.
Telecom
| Node | Average Speed | Maximum Speed | Latency RTT | HTTP Latency |
|---|---|---|---|---|
| ShenzhenTelecom@1Gbps | 469.23Mbps | 475.42Mbps | 12ms | 54ms |
| GuangdongTelecom@1Gbps | 468.33Mbps | 471.56Mbps | 11ms | 194ms |
| Eastern Guangdong Telecom@1Gbps | 451.73Mbps | 473.89Mbps | 25ms | 111ms |
| GuangxiTelecom@1Gbps | 267.20Mbps | 470.66Mbps | 28ms | 394ms |
| HainanTelecom@1Gbps | 455.51Mbps | 470.72Mbps | 21ms | 76ms |
| ShanghaiTelecom@1Gbps | 257.01Mbps | 472.50Mbps | 35ms | 111ms |
| Xi'an Telecom@2Gbps | 449.58Mbps | 473.40Mbps | 50ms | 187ms |
| Xi'an Telecom@1Gbps | 64.80Mbps | 265.90Mbps | 69ms | 255ms |
Unicom
| Node | Average Speed | Maximum Speed | Latency RTT | HTTP Latency |
|---|---|---|---|---|
| GuangdongUnicom@2.5Gbps | 472.03Mbps | 480.52Mbps | 17ms | 60ms |
| ChangshaMobile@1Gbps | 400.32Mbps | 456.62Mbps | 23ms | 98ms |
| ShanghaiUnicom@1Gbps | 460.97Mbps | 472.69Mbps | 39ms | 127ms |
| ShaoxingUnicom@1Gbps | 421.41Mbps | 472.28Mbps | 41ms | 131ms |
| LiaoningUnicom@1Gbps | 260.55Mbps | 414.31Mbps | 60ms | 481ms |
| ShanxiUnicom@1Gbps | 281.52Mbps | 444.70Mbps | 58ms | 173ms |
Mobile
| Node | Average Speed | Maximum Speed | Latency RTT | HTTP Latency |
|---|---|---|---|---|
| Guangzhou Mobile@1Gbps | 417.91Mbps | 469.24Mbps | 20ms | 98ms |
| Guangxi Mobile@1Gbps | 436.94Mbps | 476.18Mbps | 31ms | 106ms |
| Shanghai Mobile@1Gbps | 248.91Mbps | 470.08Mbps | 39ms | 134ms |
| Lishui Mobile@2Gbps | 459.35Mbps | 472.05Mbps | 42ms | 147ms |
| Jiangsu Mobile@1Gbps | 462.41Mbps | 477.20Mbps | 42ms | 438ms |
| Sichuan Mobile@1Gbps | 450.79Mbps | 471.98Mbps | 62ms | 188ms |
| Hebei Mobile@1Gbps | 453.81Mbps | 476.17Mbps | 52ms | 177ms |
| Shanxi Mobile@1Gbps | 370.73Mbps | 470.09Mbps | 56ms | 183ms |
6. International Connectivity
Within Hong Kong it basically saturates 500Mbps both ways, and performance to Japan and Singapore is also good.
Web Latency
bash <(wget -qO- https://raw.githubusercontent.com/danger-dream/network-latency-tester/main/latency.sh)
To TG DC5 it goes through sg.gs and to TG DC4 it goes through Vodafone; both routes are connected by Telegram, so in theory speeds should be faster.
| 🇭🇰 Neburst -> 🇸🇬 TG DC5 | 🇭🇰 Neburst -> 🇳🇱 TG DC4 |
|---|---|
International TCP Latency Test(itdog.cn)
| IPv4 - TCP | IPv6 - ICMPv6 |
|---|---|
Speed Test - iPerf3 TCP IPv4 Single-Thread (single 10-second run, 2025-12-21)
Test Tool: iPerf3
| Region | Node | Average/Max Upload (Mbps) | Average/Max Download (Mbps) | Latency (ms) |
|---|---|---|---|---|
| 🇭🇰 Hong Kong | DMIT T1 | 479 / 493 | 550 / 923 | 0.65 |
| 🇭🇰 Hong Kong | RFCHOST JINX | 479 / 491 | 550 / 1009 | 0.67 |
| 🇭🇰 Hong Kong | RFCHOST CTC | 479 / 488 | 550 / 1008 | 0.55 |
| 🇭🇰 Hong Kong | Nube | 479 / 491 | 548 / 1007 | 0.70 |
| 🇭🇰 Hong Kong | GreenCloud DC1 | 479 / 494 | 550 / 1008 | 0.69 |
| 🇭🇰 Hong Kong | GreenCloud DC2 | 480 / 496 | 549 / 1002 | 1.67 |
| 🇭🇰 Hong Kong | HostHatch | 479 / 488 | 550 / 967 | 0.72 |
| 🇭🇰 Hong Kong | YxVM VOL | 479 / 494 | 550 / 1009 | 0.70 |
| 🇭🇰 Hong Kong | FxTransit | 479 / 487 | 550 / 1009 | 0.81 |
| 🇭🇰 Hong Kong | Hytron | 479 / 495 | 548 / 994 | 0.77 |
| 🇭🇰 Hong Kong | Halo STD | 479 / 490 | 540 / 1009 | 1.58 |
| 🇭🇰 Hong Kong | Halo Lite | 479 / 493 | 550 / 1005 | 1.52 |
| 🇭🇰 Hong Kong | BAGE HKS | 479 / 487 | 549 / 1008 | 0.53 |
| 🇭🇰 Hong Kong | BAGE HKL | 479 / 490 | 549 / 1008 | 0.64 |
| 🇭🇰 Hong Kong | ClawCloud | 480 / 493 | 550 / 999 | 2.98 |
| 🇭🇰 Hong Kong | Servps | 479 / 491 | 550 / 1008 | 1.20 |
| 🇭🇰 Hong Kong | Boil HKT | 479 / 500 | 547 / 914 | 2.80 |
| 🇭🇰 Hong Kong | Kaze HKBN | 479 / 503 | 548 / 992 | 3.26 |
| 🇹🇼 Taipei | Misaka | 484 / 531 | 543 / 968 | 18.34 |
| 🇹🇼 Taichung | HiNet | 479 / 539 | 542 / 779 | 26.22 |
| 🇯🇵 Tokyo | DMIT T1 | 476 / 540 | 532 / 706 | 50.36 |
| 🇯🇵 Tokyo | BAGE JP | 482 / 540 | 529 / 731 | 45.09 |
| 🇯🇵 Tokyo | BAGE JPS | 484 / 549 | 527 / 768 | 45.76 |
| 🇯🇵 Tokyo | Nube | 481 / 539 | 531 / 729 | 53.78 |
| 🇯🇵 Tokyo | GreenCloud SB | 475 / 541 | 531 / 733 | 50.74 |
| 🇯🇵 Tokyo | GreenCloud IIJ | 251 / 526 | 519 / 969 | 51.37 |
| 🇯🇵 Tokyo | DDPS CDN77 | 484 / 551 | 532 / 735 | 47.68 |
| 🇯🇵 Tokyo | RFCHOST T1 | 482 / 540 | 534 / 796 | 45.20 |
| 🇯🇵 Tokyo | YxVM VOL | 481 / 540 | 535 / 792 | 45.65 |
| 🇯🇵 Tokyo | NNC STD | 481 / 542 | 535 / 800 | 45.04 |
| 🇯🇵 Tokyo | FxTransit | 485 / 561 | 534 / 797 | 45.57 |
| 🇯🇵 Tokyo | SkylineConnect | 477 / 540 | 530 / 738 | 50.22 |
| 🇰🇷 Seoul | HostHatch | 475 / 542 | 528 / 743 | 60.61 |
| 🇸🇬 Singapore | RFCHOST T1 | 483 / 537 | 538 / 887 | 30.30 |
| 🇸🇬 Singapore | BAGE SG | 482 / 529 | 539 / 887 | 30.01 |
| 🇸🇬 Singapore | BAGE SGS | 481 / 534 | 540 / 896 | 30.66 |
| 🇸🇬 Singapore | GreenCloud DC1 | 485 / 585 | 540 / 898 | 33.05 |
| 🇸🇬 Singapore | GreenCloud DC2 | 481 / 541 | 520 / 805 | 38.93 |
| 🇸🇬 Singapore | Nube | 483 / 545 | 539 / 893 | 31.12 |
| 🇸🇬 Singapore | SkylineConnect | 483 / 563 | 537 / 878 | 37.52 |
| 🇸🇬 Singapore | IDC.Care | 482 / 540 | 536 / 718 | 36.11 |
| 🇻🇳 Hanoi | GreenCloud | 482 / 542 | 545 / 949 | 22.08 |
| 🇻🇳 Ho Chi Minh City | GreenCloud | 0 / 0 | 533 / 720 | 48.34 |
| 🇮🇳 Mumbai | HostDZire | 397 / 454 | 387 / 459 | 85.70 |
| 🇦🇺 Sydney | GreenCloud | 419 / 540 | 476 / 683 | 143.09 |
| 🇺🇸 Los Angeles | DMIT T1 | 419 / 540 | 464 / 732 | 143.42 |
| 🇺🇸 Los Angeles | GreenCloud | 412 / 540 | 481 / 697 | 143.55 |
| 🇺🇸 Los Angeles | AlphaVPS | 421 / 540 | 481 / 693 | 143.67 |
| 🇺🇸 Los Angeles | HostDZire | 366 / 541 | 445 / 781 | 226.38 |
| 🇺🇸 Los Angeles | BAGE LA1 | 419 / 539 | 485 / 713 | 143.68 |
| 🇺🇸 Los Angeles | BAGE LA2 | 423 / 538 | 477 / 776 | 150.10 |
| 🇺🇸 Los Angeles | RFCHOST T1 | 414 / 536 | 147 / 278 | 149.59 |
| 🇺🇸 San Jose | HostDZire | 412 / 539 | 473 / 751 | 154.51 |
| 🇺🇸 San Jose | GreenCloud | 412 / 539 | 479 / 782 | 151.54 |
| 🇺🇸 San Jose | Nube | 404 / 539 | 480 / 733 | 155.45 |
| 🇺🇸 Las Vegas | BuyVM | 419 / 543 | 477 / 709 | 146.04 |
| 🇺🇸 Seattle | Misaka | 428 / 541 | 490 / 933 | 129.84 |
| 🇺🇸 Seattle | AlphaVPS | 242 / 440 | 450 / 790 | 198.84 |
| 🇺🇸 Ogden | GreenCloud | 412 / 539 | 476 / 781 | 149.70 |
| 🇺🇸 Salt Lake City | BAGE | 419 / 540 | 476 / 808 | 148.72 |
| 🇺🇸 Dallas | AlphaVPS | 396 / 540 | 470 / 858 | 169.21 |
| 🇺🇸 Jacksonville | GreenCloud | 368 / 539 | 443 / 707 | 208.79 |
| 🇺🇸 Chicago | GreenCloud DC1 | 389 / 541 | 462 / 930 | 177.60 |
| 🇺🇸 Chicago | GreenCloud DC2 | 352 / 538 | 457 / 964 | 221.81 |
| 🇺🇸 Ashburn | GreenCloud | 375 / 539 | 439 / 751 | 205.83 |
| 🇺🇸 Washington | HostDZire | 346 / 543 | 450 / 756 | 208.42 |
| 🇺🇸 New York | AlphaVPS | 389 / 540 | 445 / 811 | 192.52 |
| 🇷🇺 Moscow | Misaka | 88 / 230 | 120 / 139 | 163.94 |
| 🇩🇪 Frankfurt | BAGE | 366 / 541 | 435 / 792 | 225.26 |
| 🇩🇪 Frankfurt | GreenCloud | 420 / 541 | 281 / 445 | 170.46 |
| 🇩🇪 Frankfurt | BERO | 366 / 539 | 434 / 775 | 290.44 |
| 🇩🇪 Nuremberg | Netcup | 213 / 353 | 185 / 233 | 152.04 |
| 🇩🇪 Nuremberg | AlphaVPS | 394 / 538 | 463 / 671 | 147.79 |
| 🇳🇱 Amsterdam | GreenCloud | 354 / 537 | 433 / 727 | 244.69 |
| 🇨🇭 Zurich | Aluy | 367 / 538 | 63 / 143 | 241.47 |
| 🇧🇬 Sofia | AlphaVPS | 397 / 484 | 463 / 825 | 162.54 |
| 🇸🇪 Stockholm | HostHatch | 161 / 261 | 112 / 164 | 207.84 |
| 🇬🇧 London | AlphaVPS | 367 / 540 | 437 / 793 | 221.24 |
| 🇬🇧 Coventry | BAGE | 316 / 538 | 403 / 588 | 223.57 |
| 🇬🇧 Coventry | GreenCloud | 366 / 539 | 447 / 791 | 225.60 |
7. Summary
A well-rounded machine with no real weak point. Aside from the smaller bandwidth making speed-test screenshots less impressive, it is more than enough for personal use; the three networks are balanced, performance is stable, and international connectivity is excellent.
8. About the Tests
The machines used in this test were purchased at my own expense; results may be time-sensitive.
Kernel parameters of the test machines (/etc/sysctl.conf) are as follows.
fs.file-max = 6815744
net.ipv4.tcp_no_metrics_save=1
net.ipv4.tcp_ecn=0
net.ipv4.tcp_frto=0
net.ipv4.tcp_mtu_probing=0
net.ipv4.tcp_rfc1337=0
net.ipv4.tcp_sack=1
net.ipv4.tcp_fack=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_adv_win_scale=1
net.ipv4.tcp_moderate_rcvbuf=1
net.core.rmem_max=33554432
net.core.wmem_max=33554432
net.ipv4.tcp_rmem=4096 87380 33554432
net.ipv4.tcp_wmem=4096 16384 33554432
net.ipv4.udp_rmem_min=8192
net.ipv4.udp_wmem_min=8192
net.ipv4.ip_forward=1
net.ipv4.conf.all.route_localnet=1
net.ipv4.conf.all.forwarding=1
net.ipv4.conf.default.forwarding=1
net.core.default_qdisc=fq
net.ipv4.tcp_congestion_control=bbr
net.ipv6.conf.all.forwarding=1
net.ipv6.conf.default.forwarding=1
9. Acknowledgements
Thanks to "Impart Speed Test“(@Kyoma ) for providing the mainland Chinapublic-interest speed test service