Nether hub networks: when the 1:8 pays

Verified: Java 26.3 / Bedrock 26.50 · 2026-09-16 · speeds sourced below; conversions identical in both editions · Updated 2026-09-16

The conversion rule — divide by 8, floor, leave Y alone — is covered in the coordinate guide. This page is about what you build on top of the rule: how far apart hub exits go, what the dividend is worth at real travel speeds, and a worked three-base network with every tunnel length computed. Design math, not tool instructions.

What a block of tunnel buys

Every block of Nether tunnel stands in for eight Overworld blocks, so the exchange rate on your digging time is the best in the game. A 1,000-block Overworld commute collapses to 125 Nether blocks. At the documented sprint speed of 5.612 blocks per second, the surface trip runs about 178 seconds — call it three minutes — while the Nether leg sprints in about 22. Lay blue ice in the tunnel and put a boat on it, at the documented 72.73 blocks per second, and those 125 blocks pass in under two seconds. The dividend compounds with distance: a 5,000-block journey is just under 15 minutes on foot up top, under two minutes sprinting the 625-block tunnel, and about nine seconds by ice boat.

Spacing the exits

Hub design is one multiplication: exits along a tunnel serve Overworld points eight times as far apart. Portal exits every 8 blocks of tunnel correspond to surface portals 64 blocks apart — denser than anyone needs. Exits every 125 blocks serve destinations 1,000 apart, which is a comfortable district size for a mature world. The practical rule is to space exits by where your bases actually are rather than on a fixed grid: the 8× compression is forgiving, and the portal linking guide covers the tolerance that makes near-enough portal placement still link correctly — plus the search-range traps when two exits sit too close.

A worked network: three bases, one hub

Say your portals sit at spawn (0, 0) and three bases: A at (1600, −2400), B at (720, 856), C at (−984, 400) — all chosen here to divide cleanly by 8. The Nether-side targets are A′ (200, −300), B′ (90, 107), C′ (−123, 50). From a hub at Nether (0, 0), the straight tunnels run:

About 633 blocks of total tunnel serve three bases whose farthest is a 2,884-block surface trek — and the far base, eight and a half minutes of Overworld sprinting, becomes just over a minute on foot or about five seconds by boat. Dig the legs straight, label the junctions, and the network is done; the coordinate calculator converts each base and the stack calculator prices the blue ice haul in shulkers.

When the trip does not pay

Honest limits on the arithmetic. Under a few hundred surface blocks, two portal transitions plus the walk to the hub can eat the savings — short commutes are often faster overland, especially with the portals' loading pause, which varies by hardware and edition and is deliberately not given a number here. Tunnel legs are straight-line figures; lava seas, bedrock ceilings, and fortress detours add real overhead the first time you dig. Ice-boat speed needs an actual blue-ice road — packed ice runs a documented 40 blocks per second, still a bargain, while a boat on water is 8. And the time figures assume you hold sprint the whole way; nobody does, so treat them as floors, not promises.

Sources

Travel speeds: the Minecraft Wiki's sprinting documentation (minecraft.wiki/w/Sprinting — 5.612 blocks per second sprinting, 4.317 walking) and boat documentation (minecraft.wiki/w/Boat — 72.73 on blue ice, 40 on packed ice, 8 on water), read straight from those two pages. The 1:8 rule and floor behavior: this site's own coordinate documentation and its sources. Every length on this page is arithmetic on top of those figures, not a quotation from anywhere. Verified 2026-09-01; the ratio and speeds here are shared across Java 26.2 and Bedrock's current 26.x line. Every number printed on this page is asserted in the site's test suite.