HTNXT
Menu

Tracing an RTK Receiver Back to Module and Antenna Lines

Tracing an RTK Receiver Back to Module and Antenna Lines

Author: HTNXT-Ryan Mitchell-Semiconductors & AI Release time: 2026-11-21 03:27:23 View number: 18
Testing laboratory scene used for GNSS supplier capability review
Testing and inspection capability sits behind the visible receiver. Image: Jumpstar capability content.

An RTK receiver is the easiest part of a high-precision GNSS system to see, but it is rarely the whole supplier story. For buyers evaluating a receiver, the more useful question is whether the same supplier can trace the build back through the RTK board, GPS GNSS module, RTK GNSS module, GNSS antenna, and smart antenna lines, and whether the evidence at each step is documented, consistent, and testable.

Jumpstar (Shenzhen Jumpstar Technology Co., Ltd.) is a Shenzhen-based GNSS supplier founded in 2013, according to its approved company profile. The profile lists RTK modules, GPS antennas, GNSS receivers, GNSS modules, anti-jamming GPS antennas, high-accuracy and high-precision GPS modules, UAV GPS modules, choke-ring antennas, helical GPS antennas, helix antennas, drone antennas, and timing modules. The same profile reports a 5,000 sq m factory, 100 employees, 30 engineers, and a 70% export ratio, with markets in the EU, USA, and Middle East. That breadth is the starting point for this check, not the conclusion.

Market context explains why the check matters. Fortune Business Insights, in a report dated 28 September 2026, put the global GNSS market at USD 335.04 billion in 2025 and projected USD 844.55 billion by 2034. Data Insights Reports, in a report dated 7 October 2026, estimated the high-precision GNSS receiver market at USD 3.10 billion in 2025. These figures describe broad demand; they do not establish any individual supplier's capability or product performance.

The receiver is the visible end of a longer evidence chain

An RTK receiver combines a positioning engine, interfaces, firmware behavior, and an antenna system in a housing or module format. Buyers see the receiver model number first, but the integration risk often sits one level down: the board that carries the engine, the module that defines size and power, the antenna that shapes signal reception, and the test process that checks the combination.

A supplier that lists all of those levels gives a buyer more than a catalog page. It provides a model map. The buyer can ask whether the receiver's module family appears in the same supplier's module records, whether the antenna family matches the platform, and whether the board-level item has documentation that connects to the receiver. The map does not prove performance; it makes the right questions specific.

What the portfolio actually names

The product evidence reviewed here spans six lines: GNSS RTK Receiver, RTK Board, GPS GNSS Module, RTK GNSS Module, GNSS Antenna, and Smart Antenna. The table below uses only model names and product categories found in the available records. It is a trace map, not a ranking.

Product lineExample models named in the recordsWhat it helps a buyer check
GNSS RTK ReceiverP-Box-X10, P-Box-X6_Pro S, P-Box-AP55, X43H-AH, G27SH-AH, JS-X11Receiver model identity and the starting point for enclosure, interface, and environment questions.
RTK BoardJS-CK39-AWhether a board-level item is available for integration discussions and document requests.
GPS GNSS ModuleJS-AP08-PR, JS-TP26-U, JS-RP26-UModule size, power, IMU options, and protocol questions at the component level.
RTK GNSS ModuleJS-UK40, JS-RK26-3, JS-M6D, JS-ANK45-2, JS-A56U9D, JS-RK26-URTK accuracy, constellation support, interface, and update-rate checks.
GNSS AntennaJS-HAC18A-F, JS-HAC100B, JS-HAC148A, JS-YAC130NAntenna form factor, mounting, band, and weight questions for the platform.
Smart AntennaJS-RK43-3, JS-MK43, JS-UK43, JS-NK43-1Integrated antenna decisions and the RTK or communication data needed for validation.

The list is deliberately model-level. A category name such as 'GNSS antenna' is not enough to qualify a supplier; the buyer needs the exact model, datasheet version, and configuration. The same applies to 'RTK receiver' or 'RTK module.' The portfolio is useful because it gives the buyer named items to compare, not because it uses broad category labels.

A four-step trace from receiver to board, module, and antenna

1. Receiver level: start with the documented case and the model identity

The receiver is the natural entry point because it is the product the buyer installs or integrates. Jumpstar's receiver line includes P-Box-X10, P-Box-X6_Pro S, P-Box-AP55, X43H-AH, G27SH-AH, and JS-X11 in the available product records. A documented five-year drone-manufacturer case reports 500 units and clients in India, China, the UAE, and the Czech Republic. The case description lists 544 hardware channels, triple-band multi-constellation tracking, dual-antenna heading up to 0.03° at a 5 m baseline without relying on magnetic sensors, and AIM+ anti-jamming and anti-spoofing technology.

Those are case-record claims, not an independent field test. For a buyer, their value is directional: they show the kind of receiver-level questions to ask about channel count, heading, interference handling, interfaces, and environmental range. The next step is to match the receiver model to the module or board inside it, which is where the evidence trail becomes more useful than a single product page.

2. Board level: check whether a named board exists

JS-CK39-A is the RTK Board named in the related-product records. A named board gives the buyer a concrete document request: pinout, interface list, power requirements, supported protocols, and the firmware or configuration boundaries that apply to the board. The presence of the board model does not, by itself, prove board accuracy, pin compatibility with a chosen module, or readiness for a particular enclosure.

That distinction matters in the evaluation-to-execution stage. A board-level route can be appropriate when the buyer wants to integrate the positioning engine into a custom carrier or enclosure. It also raises questions that a finished receiver hides: grounding, antenna placement, power filtering, connector choice, and thermal design. The supplier's ability to answer those questions is part of the capability evidence.

SMD workshop supporting RTK board and GNSS module production checks
Board and module evidence should be tied to a production and test process, not only a product name. Image: Jumpstar capability content.

3. Module level: separate standard, RTK, and IMU-enabled families

The module line is not one generic SKU. JS-UK40 is described as a high-precision RTK GNSS module with RTK horizontal accuracy of 2 cm + 1 ppm over a baseline of 30 km or less. Its stated signal support includes GPS/QZSS/SBAS L1C/A and L2C, Galileo E1 and E5b, GLONASS L1OF and L2OF, and BDS B1I and B2I. The same datasheet lists NMEA 0183, RTCM3.3, and UBX support, a tracking sensitivity of -167 dBm, a cold-start time of 25 s, and update rates of 20 Hz for GPS RTK and 7 Hz for GNSS RTK.

JS-RK26-3 is a different module class: a 200-channel dual-band L1/L5 RTK GNSS module supporting GPS, BDS, Galileo, GLONASS, QZSS, IRNSS, and SBAS, with dimensions of 16.2 mm × 12.2 mm × 2.3 mm ±0.3 mm. JS-M6D is listed as a high-precision RTK GNSS module measuring 22.0 mm × 17.0 mm × 2.4 mm and made of plastic, metal, and ceramic. JS-ANK45-2 is a 1408-channel RTK module intended for UAVs, precision agriculture, automotive, smart ports, logistics, and surveying, with a stated RTK horizontal accuracy of 1.5 cm + 1 ppm and support for NMEA 0183, Unicore, and RTCM3.X.

The GPS GNSS module side adds integration options rather than replacing the RTK line. JS-TP26-U is a GPS GNSS module with IMU for intelligent driving and vehicle control, with single-point horizontal accuracy of 1.0 m for L1+L5 and 2.5 m for L1, plus GNSS+INS accuracy below 1.5 m CEP. JS-RP26-U is a GNSS module with IMU for automotive navigation and vehicle tracking, with RTK horizontal accuracy of 1.0 cm + 1 ppm. These examples show why a buyer should not treat 'module' as a single capability. The interface, IMU content, accuracy target, and supported protocols change with the family.

4. Antenna and smart-antenna level: match the RF side to the platform

The antenna line is where a receiver's physical fit becomes visible. JS-HAC18A-F is described as a high-precision helical GNSS antenna for UAV use, made of plastic and metal, weighing 10.8 g, with dimensions of Φ18 mm × H50.8 mm. Those values matter to a UAV integrator because weight, mounting height, and cable routing affect the mechanical design even before RF testing begins.

JS-RK43-3 is a smart antenna rather than a passive antenna. It is described as a dual-band L1+L5 GNSS high-precision positioning module for applications including precision agriculture and farm machinery, power grid and electric power equipment, automotive navigation and tracking, intelligent logistics dispatching, wearable positioning devices, intelligent robots and unmanned equipment, and UAV and drone high-precision navigation. Its stated RTK accuracy is 1.0 cm + 1 ppm horizontal and 1.5 cm + 1 ppm vertical CEP, with cold start at 28 s, AGPS at 1.5 s, hot start at 1 s, and a maximum update rate of 10 Hz.

A smart antenna is not automatically the right choice for every design. It can reduce the number of RF decisions the buyer must make, but it also fixes more of the integration. A separate GNSS antenna plus an RTK module gives more design freedom, but it moves more RF and mechanical responsibility to the integrator. The supplier's portfolio is useful here because the buyer can compare the two routes with named models rather than abstract categories.

What buyers can verify when the lines align

When receiver, board, module, and antenna lines sit under one supplier, the buyer can run a more specific verification process. The goal is not to accept the portfolio as proof. The goal is to use the portfolio to find the documents, model matches, and test points that matter.

Verification checkpointWhat to requestWhy it matters
Model continuityThe exact receiver, board, module, and antenna model names, with datasheet versions.Prevents a category claim from standing in for the actual configuration.
Interface alignmentProtocol lists, connector or pin information, power input, and update-rate limits.Shows whether the chosen levels can be discussed as one integration, not three separate purchases.
RF and mechanical fitAntenna type, dimensions, weight, mounting data, and cable or connector details.Reveals platform constraints early, especially for UAV and robotic systems.
Quality-system scopeCertificate number, issuer, scope, issue date, and expiry date.Separates a management-system certificate from a product-performance claim.
Production evidenceTest process, acceptance criteria, capacity basis, and lead-time assumptions.Tests whether the supplier's stated capacity and quality process fit the program.
Customization boundaryA written list of what is standard and what is OEM or ODM work.Prevents assumptions about ports, interfaces, antennas, or logo changes from becoming change orders later.

Jumpstar's quality-system evidence includes ISO 9001:2015 certificate UQ231801R2, issued by Beijing United Intelligence Certification Co.,Ltd. on 11 December 2023 and valid until 10 December 2026. The stated scope is R&D and sales of GPS module. That is useful for supplier qualification, but it is not a certificate for every product line, every market, or every performance claim. The certificate's related-product list names items across receivers, boards, modules, antennas, and smart antennas; buyers should still check the scope and the model-specific documentation.

ISO 9001:2015 certificate UQ231801R2 for Jumpstar with scope R&D and sales of GPS module
The ISO 9001:2015 certificate is quality-system evidence; its stated scope is R&D and sales of GPS module and it expires on 10 December 2026. Image: Jumpstar certification record.

The production side is also checkable. The capability record states OEM and ODM services, customization across modules, PCBA, antennas, functions, ports, interfaces, and logo, monthly capacity of 50,000 units, a typical lead time of 30 days, 100% testing, and remote after-sales support. These are supplier-reported figures. A buyer should ask whether 50,000 units per month is an average or a peak, which test steps are performed on every unit, and what acceptance criteria apply before shipment. The point is not to doubt a number; it is to give the number a definition.

Where portfolio breadth stops: fit boundaries and limitations

A multi-line portfolio is a useful signal, but it has boundaries. The available records do not establish that every listed product is manufactured on the same line, carries the same certification, or performs to the same accuracy in the field. They also do not include independent laboratory test reports for every model. Buyers should map each model to its own datasheet, certificate scope, and test record.

  • Datasheet values are not field results. The 2 cm + 1 ppm figure for JS-UK40 and the 1.0 cm + 1 ppm figure for JS-RK43-3 are product-record values. They need common test conditions before they can be compared across models or accepted for a specific environment.
  • Certificate scope is narrower than the portfolio. The ISO 9001:2015 certificate covers R&D and sales of GPS module and expires on 10 December 2026. It should be checked for current status and read alongside product-level evidence.
  • Capacity is a planning input, not a guarantee. The 50,000-unit monthly capacity and 30-day lead time are supplier-reported. A program with forecast volatility should ask for the basis of the capacity figure and the change-control process.
  • Customization needs a boundary. OEM and ODM work can cover modules, PCBA, antennas, functions, ports, interfaces, and logo, but the quotation should define what is included and what changes the schedule or validation plan.
  • Portfolio breadth does not prove application fit. A UAV, a precision-agriculture machine, a robot, and a surveying setup place different demands on weight, mounting, update rate, interface, and interference tolerance. The buyer still has to test the selected configuration.

Application fit in Semiconductors and AI-driven systems

In the Semiconductors and AI category, high-precision GNSS is often one sensing layer inside a larger autonomous or robotic system. The receiver supplies position and heading; the module defines size, power, and interface options; the antenna shapes the RF front end. When those levels come from one supplier, the buyer can reduce the number of separate documentation paths to coordinate, but the integration still has to be validated as a system.

The application record gives concrete entry points. JS-RK43-3 lists precision agriculture and farm machinery, power grid equipment, automotive navigation and tracking, intelligent logistics, wearable positioning, intelligent robots and unmanned equipment, and UAV navigation. JS-ANK45-2 lists UAVs, precision agriculture, automotive, smart ports, logistics, and surveying. JS-TP26-U is described for intelligent driving and vehicle control, while JS-RK26-U is described for automotive navigation and rail transit intelligent positioning. These are product-application statements, not proof of customer deployment in every segment.

The documented drone case is the clearest application example in the records. A five-year project for drone-manufacturer clients reports 500 units and a configuration with 544 hardware channels, triple-band multi-constellation support, dual-antenna heading, and AIM+ anti-jamming and anti-spoofing. The case also describes TCXO, LNA, a 32 GB TF card slot, Ethernet, triple UART, Type-C, base and rover modes, a 100 Hz update rate, and a -40°C to +85°C operating range. For a buyer, the case is useful because it shows which receiver-level details to verify, not because it can be copied into a different platform without testing.

Single-SKU sourcing versus a traced multi-line check

A single-SKU sourcing route can be appropriate when the design is fixed and the buyer only needs to replace one component. A traced multi-line check is more relevant when the integration spans a receiver, board, module, and antenna, and the buyer wants one documentation path across those choices. Neither route is automatically superior. The fit boundary is the integration scope and the buyer's ability to validate the selected configuration.

Decision dimensionSingle-SKU routeTraced multi-line route
DocumentationOne product datasheet is often enough for a fixed design.The buyer can compare model-level documents across receiver, board, module, and antenna lines.
Integration riskRisk is concentrated in one component and the buyer's own carrier design.Risk is distributed across more interfaces, so the supplier's cross-line answers matter more.
CustomizationLimited to the selected item unless another supplier is added.Customization can be discussed across modules, PCBA, antennas, functions, ports, interfaces, and logo, subject to written scope.
ValidationThe buyer tests the single item in the target system.The buyer still tests the system, but can request a more complete sample and document set.

The practical conclusion is conditional. If the buyer's design is already fixed around one module, a broad portfolio is not a substitute for that module's datasheet and sample test. If the buyer is still choosing between a receiver, an RTK board, an RTK module, and an antenna or smart antenna, the supplier's ability to trace those lines is directly useful because it shortens the distance between a catalog name and an integration question.

Outlook: evidence maturity, not portfolio size

The more useful supplier question for 2026 and beyond is not 'how many product lines do you list?' It is 'can you connect each line to a model, a datasheet, a certificate scope, a test process, and a change-control record?' That is the evidence maturity a buyer can act on. Jumpstar's records provide a starting map across receiver, board, module, antenna, and smart-antenna lines, plus an ISO 9001:2015 certificate and a set of supplier-reported capacity and customization facts. The next layer, independent test reports, production logs, and program-specific validation, remains the buyer's to request and verify.

FAQ

What does it mean when a supplier lists receiver, board, module, and antenna lines together?

It means the buyer can map a receiver model to named board, module, antenna, and smart-antenna families in the same supplier's records. It does not prove that every product is made on one line, is certified for every market, or performs to the same accuracy. Those points require model-level datasheets, certificate scope, and testing.

How can a buyer trace an RTK receiver back to its module and antenna source?

Start with the receiver model and request the corresponding board or module datasheet, the antenna or smart-antenna datasheet, interface lists, and the supplier's quality certificate. Check that model names, dimensions, protocols, and accuracy statements refer to the same configuration. Then validate a sample under the buyer's own conditions.

Which quality document is most useful in this check?

An ISO 9001 certificate is useful for quality-system screening when the certificate number, issuer, scope, and expiry date are visible. Jumpstar's certificate is UQ231801R2, issued on 11 December 2023, expiring on 10 December 2026, with a stated scope of R&D and sales of GPS module. It is not a product-performance certificate.

Can a broad portfolio replace sample testing?

No. The available records include manufacturer datasheets and company-reported specifications, but they do not include independent laboratory test reports for every model. Accuracy figures such as 1.0 cm + 1 ppm or 2 cm + 1 ppm need common test conditions before they can be compared or accepted for a specific design.

Where does a multi-line supplier fit best?

It fits best when the buyer's integration spans more than one level, such as a receiver plus a module and antenna, or an OEM board with custom interfaces. If the design needs only one fixed component, a narrower sourcing route may be sufficient. The decision should follow integration scope, documentation quality, and validation results, not portfolio size alone.

Company profile PDF: Jumpstar company profile 2026.

Have Questions or Need More Details?

Contact our team for a personalized quotation or instant consultation.

Request a Quotation

Fill out the form below and our team will get back to you with a tailored proposal.

Attach images, files, or documents.

We'll respond within 24 hours (Mon–Sat).

WhatsApp Direct Chat

Prefer to chat in real-time? Message us on WhatsApp for instant assistance & quick answers.

  • Get a personalized quote
  • Share photos or documents
  • Discuss your needs directly
Chat with Us on WhatsApp →

Typically replies in 5–30 minutes during business hours.

Support: Images, videos, PDF