Which Frequency Bands Do GNSS Satellites Use?

GNSS satellites transmit most navigation signals in L-band, the 1–2 GHz range identified by ESA for satellite navigation [1]. GPS uses L1, L2 and L5; Galileo uses E1, E5 and E6; GLONASS uses channelised G1/G2 and newer CDMA signals; BeiDou uses B1, B2 and B3 signal families. QZSS shares GPS navigation frequencies and also broadcasts L6 augmentation signals. NavIC specifies L1 and L5 signals plus an S-band signal at 2492.028 MHz.

The frequencies below are nominal carrier centres, not antenna passband edges. They describe the principal navigation signals and the QZSS L6 augmentation downlink, not every restricted-service signal or satellite communications link. A constellation’s signal plan does not mean that every satellite transmits every listed signal.

Which Frequency Bands Do GNSS Satellites Use?

Table of Contents

GPS frequency bands

GPS has three navigation carriers: L1 at 1575.42 MHz, L2 at 1227.60 MHz and L5 at 1176.45 MHz. The GPS Standard Positioning Service Performance Standard specifies right-hand circular polarisation (RHCP) for these signals. L1 C/A uses a 1,023-chip code at 1.023 megachips per second (Mcps). The composite L2C sequence has 1,534,500 chips at 1.023 Mcps; its underlying CM and CL codes each run at 0.5115 Mcps. L5 I5 and Q5 each use 10,230-chip primary codes at 10.23 Mcps [2].

L1 C/A and L1C are different signals on the same 1575.42 MHz carrier. GPS.gov describes L1C as designed for interoperability with other navigation systems. It also explains that receiving L1 and L2C together enables ionospheric correction; the benefit comes from measuring two frequencies, not simply tracking more satellites at one frequency [3].

Galileo frequency bands

Galileo uses E1 at 1575.42 MHz, E6 at 1278.75 MHz and the E5 signal group. E5 is centred at 1191.795 MHz; its E5a and E5b components are centred at 1176.45 and 1207.14 MHz. E5a and E5b can be processed independently, so these are not five unrelated bands. The E5a and E5b I/Q ranging codes run at 10.230 Mcps [4].

The Galileo ICD specifies receiver reference bandwidths of 24.552 MHz for E1, 40.920 MHz for E6, 51.150 MHz for the complete E5 signal, and 20.460 MHz each for E5a and E5b. These are reference bandwidths for receiver performance calculations, not interchangeable definitions of occupied spectrum or regulatory allocations [4]. ESA explains that compatible modulation allows GPS and Galileo to share frequencies while avoiding mutual interference. That compatibility does not make a receiver immune to external interference [5].

GLONASS frequency bands

Legacy GLONASS uses frequency-division multiple access (FDMA), with carrier frequency set by channel number k: G1 = 1602.0 + 0.5625k MHz and G2 = 1246.0 + 0.4375k MHz. For the channel interval k = −7 to +6, the carrier centres span 1598.0625–1605.375 MHz for G1 and 1242.9375–1248.625 MHz for G2. These are centre-frequency ranges, not the full widths of the transmitted signals [6].

The newer code-division multiple access (CDMA) signal plan includes L3OC at 1202.025 MHz and, for GLONASS-K2, L1OC at 1600.995 MHz and L2OC at 1248.06 MHz. Availability depends on the satellite and payload generation; these additions do not replace every legacy FDMA signal [7].

BeiDou frequency bands

The principal BeiDou open-service centres are B1I at 1561.098 MHz, B1C at 1575.42 MHz, B2a at 1176.45 MHz, B2b at 1207.14 MHz and B3I at 1268.52 MHz. The Open Service Performance Standard lists bandwidths of 4.092 MHz for B1I, 32.736 MHz for B1C, and 20.46 MHz each for B2a, B2b and B3I [8].

B2a and B2b must not be confused: they are at 1176.45 and 1207.14 MHz respectively. The 1207.14 MHz centre belongs to B2b in this open-service signal list, not to B2a [8].

QZSS and NavIC frequency bands

QZSS navigation signals use L1 at 1575.42 MHz, L2 at 1227.60 MHz and L5 at 1176.45 MHz, as specified in its positioning, navigation and timing interface document [9]. Its L6 augmentation signals use a separate centre at 1278.75 MHz. The L6 specification gives a 42.0 MHz bandwidth for Block II and III; this correction-data downlink should not be confused with the L1/L2/L5 ranging signals [10].

NavIC’s L1 interface document specifies L1 at 1575.42 MHz, L5 at 1176.45 MHz and S-band at 2492.028 MHz. Its frequency-band table gives 1563.42–1587.42 MHz for L1, 1164.45–1188.45 MHz for L5, and 2483.5–2500 MHz for S-band. These correspond to bandwidths of 24, 24 and 16.5 MHz respectively. A receiver intended for NavIC S-band therefore needs coverage outside L-band; support for NavIC L1 or L5 alone does not imply S-band support [11].

Which GNSS signals share the same frequency?

Selected shared nominal carrier centres; matching frequencies do not mean identical signal formats.
Centre frequency	Signals sharing the centre	What to check
1575.42 MHz	GPS L1, Galileo E1, BeiDou B1C, QZSS L1 and NavIC L1	Receiver support for each signal, not just an “L1” label [2][4][8][9][11]
1176.45 MHz	GPS L5, Galileo E5a, BeiDou B2a, QZSS L5 and NavIC L5	Required bandwidth and supported signal processing [2][4][8][9][11]
1207.14 MHz	Galileo E5b and BeiDou B2b	Support for the respective signal formats [4][8]
1227.60 MHz	GPS L2 and QZSS L2	L2C support in the receiver [2][9]
1278.75 MHz	Galileo E6 and QZSS L6	Different service formats and bandwidth specifications [4][10]

A worked frequency-plan check

Consider a receiver required to track GPS L1/L5 and Galileo E1/E5a. Comparing their ICDs reduces four signal names to two carrier centres: 1575.42 and 1176.45 MHz. This is a useful first check when preparing an antenna specification, but it does not reduce the receiver’s need to process four distinct signals [2][4].

Using Galileo’s receiver reference bandwidths as the design assumption, E1 spans 1575.42 ± 12.276 MHz, or 1563.144–1587.696 MHz. E5a spans 1176.45 ± 10.230 MHz, or 1166.220–1186.680 MHz. These calculated intervals are a reference-bandwidth check, not a complete antenna acceptance specification: they do not establish gain, matching, axial ratio or performance at the band edges [4].

Now add legacy GLONASS G1. At k = −7, the centre is 1602.0 − 7 × 0.5625 = 1598.0625 MHz, already above the E1 reference interval. Thus, coverage specified only for that E1 interval would not cover even the lowest G1 carrier in the selected channel range. At k = +6, G1 reaches 1605.375 MHz; the signal bandwidth must be allowed for beyond the carrier centres [6].

What multiple frequencies can and cannot improve

Dual-frequency measurements enable ionospheric correction. GPS.gov also describes the wider L5 signal design as improving jam resistance and providing redundancy when combined with L1. These are design benefits, not a guarantee that a three-band receiver keeps working through any interference or achieves a particular accuracy. The source describes sub-metre performance through three-frequency techniques as a possibility, not an automatic result [3].

For equipment selection, distinguish multi-constellation from multi-frequency. GPS L1 and Galileo E1 give access to two constellations at one nominal centre. GPS L1 and L5 provide two frequencies within one constellation. A receiver’s specification must identify both the systems and the signals it can actually track [3][4].

Which bands must the antenna and RF chain cover?

Start with the required signals, then specify bandwidth around each centre. Do not assume that every installation needs every GNSS band or one continuous passband from L5 to G1. Adding GPS L2, BeiDou B1I/B3I, Galileo E6, QZSS L6 or NavIC S-band changes the frequency plan. Matching a carrier list is only the first step; antenna polarisation and the receiver’s signal support must also match.

For GPS’s RHCP signals, an ideal linearly polarised antenna has a polarisation mismatch loss of approximately 3 dB, equivalent to receiving half the power available with a matched circular polarisation. This is the ideal polarisation loss, not the total loss of an installed antenna and cable system [12].

For a specialised ground-station feed, review antenna feeder networks and tracking antenna platforms against the actual frequency plan rather than assuming that a product-family label establishes GNSS compatibility. Where the design uses waveguide hardware, check the operating range and interfaces of waveguide-to-coaxial adapters and orthomode transducers separately. Their presence in a catalogue is not evidence that a particular assembly supports the required GNSS bands.

Planning a multi-band ground-station feed around these GNSS bands?

Send the operating bands, polarization, and interface requirements for an engineering review.

Send Your Frequency Plan