Home/GNSS Receiver

TOKNAV PRODUCTS

GNSS & RTK receivers for field, network and integration work

Compare RTK rovers, local base-rover systems, CORS reference receivers and GNSS/INS devices in a single, clear product path.

TOKNAV T50Pro GNSS receiver

PRODUCT BROCHURE

GNSS Receiver Product Brochure

Explore the 22-page TOKNAV GNSS receiver range, including RTK rovers, reference stations and GNSS/INS product paths.

English · PDF · 22 pages

Download PDF ↗

SELECT BY APPLICATION

Choose by correction workflow and project role

A receiver is only one part of a working positioning system. Start with the way correction data is supplied and the task the hardware must perform, then compare the products within the right series.

01

Mobile survey or GIS workUse a rover configuration when network correction is available or when a portable receiver is the primary field tool.

02

Local base and rover workflowReview a base-station capable receiver and data radio plan when correction is generated on site.

03

CORS, monitoring or integrationUse infrastructure or GNSS/INS equipment when the receiver is part of a reference network, automation system or OEM installation.

RTK RECEIVER SELECTION

Choose the RTK receiver around the correction workflow

An RTK receiver decision starts with the field task: surveying, stakeout, control, mapping or machine guidance. Then confirm how corrections will be received, who will operate the equipment and what must be delivered at the end of each shift.

For a local base-rover workflow, plan the base location, radio link and control checks. For a CORS or VRS workflow, confirm service coverage, credentials, mobile connectivity and the project coordinate system before field deployment.

Practical planning checks

  • Define the survey or guidance task and its deliverable.
  • Choose base-rover or CORS/VRS corrections for the operating area.
  • Confirm field data collection, control checks and office handover.

Related products and guides

Request an RTK receiver configuration

GNSS RECEIVER FAQ

Plan the receiver around the project workflow

Use the project task, correction method and data workflow to compare rover, base-station and CORS receiver paths before requesting a configuration.

How do I choose a GNSS receiver for surveying and mapping?

Begin with the application, required working method, local data-link conditions and the role of the receiver in the project. The relevant product page and a configuration discussion can then narrow the model choice.

What is the difference between an RTK rover and a GNSS base-station receiver?

The intended role in the measurement workflow is different. TOKNAV lists RTK receiver and CORS or base-station product paths separately so that project teams can review the appropriate configuration before ordering.

Can TOKNAV GNSS receiver products be considered for CORS projects?

The GNSS receiver range includes CORS and GNSS base-station product paths. Confirm the required communication, correction-service and infrastructure configuration with TOKNAV for the specific project.

Does GNSS receiver configuration vary by country or market?

It can. Data links, radio use, cellular coverage, software, accessories and local regulations can affect a configuration. Include the destination country in an enquiry before purchase or deployment.

What should I include in a GNSS receiver quotation request?

Include the country, application, project conditions, required receiver role, preferred data link and any existing controller or software environment. This supports a more useful first discussion.

RTK receivers

Portable GNSS RTK receivers for surveying, stakeout, mapping and field data collection.

CORS & reference stations

Receivers for reference-station deployment, CORS networks and persistent correction workflows.

GNSS/INS integration

Positioning and orientation receivers for unmanned systems, machine control and embedded integration.

Need a rover, base-rover or CORS configuration?

Start with the correction source and field workflow, then confirm receiver, antenna, controller or software, radio or network link and accessory requirements together.

Request a configuration

SUPPORT RESOURCES

Move from comparison to a project-ready choice

Use the category structure to compare the role of each product, then open its model page and send the project context for a focused recommendation.

PROJECT INQUIRY

Tell us what you need to position

Share the application, field environment, destination market and planned quantity. The TOKNAV team can then recommend the relevant product path and complete system configuration.

Use the existing secure inquiry form to start the discussion.

Send an inquiry