KSAT’s Lunar Network Turns Moon Communications Into a Ground Game
KSAT is expanding its lunar communications network with additional ground-station capacity, a timely reminder that Artemis, CLPS, and commercial Moon missions n
The next bottleneck in the Moon economy may be on Earth. KSAT, the Norwegian ground-network operator formally known as Kongsberg Satellite Services, is expanding lunar communications capacity as NASA, commercial lander providers, and international missions prepare for a busier run of Moon operations. The update is not as dramatic as a launch or landing, but it sits on the same critical path. A lander can touch down safely and a rover can survive the night, yet the business still fails if operators cannot move commands, telemetry, images, timing data, and fault reports through reliable Earth-Moon links. AI-generated image Ground stations are becoming part of the lunar infrastructure stack, not just back-office support. The Moon Still Needs Earth Cislunar infrastructure is often described from the spacecraft outward: launch vehicles, landers, relays, rovers, habitats, power systems, and navigation beacons. KSAT's update points in the opposite direction. The Moon economy also needs ground networks on Earth with enough coverage, scheduling discipline, and signal performance to support missions that are farther away and less forgiving than low Earth orbit customers. That is a practical business story. A commercial lunar mission has several moments when communications capacity becomes mission-critical. The spacecraft needs support after launch, through trans-lunar cruise, during trajectory corrections, at lunar orbit insertion or direct descent, through landing, and during early surface commissioning. A single missed contact can force operators to conserve power, delay payload work, or troubleshoot with stale data. NASA has its own Deep Space Network, and it remains the backbone for the agency's highest-priority deep-space missions. The problem is demand. Artemis, Mars spacecraft, outer-planet probes, astrophysics observatories, and commercial Moon missions all want antenna time. Commercial networks such as KSAT's can absorb part of that growth, especially for missions that need routine operations support rather than exclusive DSN-class coverage. The timing matters because lunar traffic is becoming less hypothetical. NASA's CLPS deliveries, Moon Base payloads, commercial rovers, private landers, international science missions, and planned relay systems all depend on data moving through a chain that reaches Earth. If the ground side is thin, the rest of the architecture gets brittle. 3 Main Earth regions needed for global coverage 384k Approximate kilometers to the Moon 24/7 Coverage goal for active mission phases CLPS Commercial lunar delivery demand driver Why this is newsworthy KSAT's lunar-network expansion shows that the Moon economy is moving beyond spacecraft announcements. The market now needs service providers that can sell dependable communications windows, handovers, and mission support from Earth. What A Lunar Ground Network Has To Do A lunar ground network starts with antennas, but the service is more than metal dishes. Operators need frequency support, scheduling software, low-noise receivers, weather-aware site diversity, cybersecurity controls, customer interfaces, recording, monitoring, and people who can support anomalies when a mission is in a critical phase. The station has to be available when the spacecraft is visible, and another station has to be ready when Earth rotates out of view. That geography is why global networks matter. A site in the Americas cannot provide continuous access by itself. Missions need handovers to Europe, Africa, Asia, Australia, or polar regions depending on geometry and licensing. For lunar missions, the Moon's position in the sky also changes the contact pattern. A network with multiple well-placed sites gives operators more ways to protect coverage during landing, commissioning, and surface work. Data rates are another constraint. A small spacecraft may only need modest command and telemetry support during cruise, then want higher-rate downlinks after collecting imagery or payload data. A rover may send routine health packets most of the time, then require more bandwidth for traverses, hazard images, or instrument campaigns. A lander may need low-latency operational data during descent and higher volume later for science return. AI-generated image Global site diversity is what turns antennas into a service a lunar mission can schedule around. Mission phase Communications need Commercial value Trans-lunar cruise Commanding, ranging, telemetry, trajectory updates Routine paid contact windows Lunar arrival High-priority tracking and fault visibility Premium support during risk-heavy operations Surface commissioning Health data, payload activation, imagery Fast proof that payloads survived landing Science campaign Bulk data return and periodic commanding Recurring service revenue across mission life Why KSAT Is Positioned For This Market KSAT is not a lunar startup in the usual sense. It is an established ground-station operator with a long record serving Earth observation, small satellites, government missions, and deep-space customers. That matters because lunar communications is an operations business. The companies that win will not only have antennas. They will have booking systems, service-level habits, operational staff, regulatory experience, and customer trust. The company's lunar network work fits a broader shift in space services. Low Earth orbit customers helped normalize ground station as a service. Instead of building a custom ground segment for every mission, operators can buy access to existing sites. The Moon is harder because the path loss is larger, the contact geometry is different, and critical events are less forgiving. The same service model can still apply if the network is built for the range and operational stakes. For NASA and commercial lander providers, the appeal is redundancy. A CLPS mission may use NASA assets, a commercial network, partner stations, or a mix. Extra ground capacity does not remove the need for deep-space-grade planning, but it gives mission operators more options when weather, antenna maintenance, schedule conflicts, or anomalies threaten the plan. For investors and suppliers, the signal is that lunar infrastructure demand is starting to spread into less visible categories. The most obvious revenue goes to launch and lander companies. The durable revenue may also go to firms that handle power, communications, navigation, software, mission operations, and surface logistics. Ground stations sit squarely in that second group. What To Watch Next • Named customers: Which CLPS, rover, relay, or science missions buy lunar-network capacity? • Service classes: Does the market split into routine telemetry, premium critical-event support, and high-rate science downlink? • Interoperability: How do commercial ground networks plug into NASA's LunaNet and relay planning? • Geographic buildout: Which new sites close coverage gaps for landing and surface operations? The Relay Question Ground stations are only one side of the lunar communications chain. Surface assets near the lunar south pole will often face blocked lines of sight, especially inside or near shadowed terrain. Relays in lunar orbit can help bridge that gap. The ground network still matters because relay satellites need Earth links for command, health, routing, and data return. That creates a layered market. A rover may connect to a local lander, a relay orbiter, or a direct-to-Earth terminal depending on location and mission design. The relay may send data to a commercial ground station, a government site, or a partner facility. Mission control may sit in Houston, Tokyo, Turin, Denver, or a commercial operations room. The user experience should feel simple, but the chain underneath is complex. LunaNet, NASA's lunar communications and navigation framework, is relevant here because it tries to define common services for a crowded Moon. A commercial ground network does not have to be LunaNet by itself. It becomes m