AppCorpus
Market US

iRegatta Pro

by Zifigo

iPhone · iPad

Active Last checked 31 Jul 2026

Quick verdict

What it is
Store information collected; independent summary not yet available.
At a glance
  • $19.99
  • In-app purchases

Categories and search queries

Official categories

AppCorpus categories

Key functions

Function Availability Access Scope Evidence
In-app purchases Yes Limited free Store published

Screens

App Store

11 store screenshots

iRegatta Pro ipad screenshot 1
iRegatta Pro ipad screenshot 2
iRegatta Pro ipad screenshot 3
iRegatta Pro ipad screenshot 4

Pricing & paywalls

App Store

  • Price: $19.99
  • In-app purchases

Ratings & reviews

App Store

4.1 8 ratings · App Store

  1. 3/5Potential

    This app has incredible Potential as a cheap way to have a full race data package however, it could use some guidance as to how to integrate it. I would like to see a variety of hardware setups and the developer giving some advice on how to apply the Potential of this app.

    Nickname neil · 31 Jul 2026

Privacy & accessibility

App Store

Privacy

  • Data Not Collected Developer declared

Accessibility

No accessibility labels collected yet.

Versions

App Store

  • 4.50.9

    Tap the "Time to Line" readout in the start view to make it change into "Burn/Gain".

  • 4.51.0

    - Bug fix for transmitted waypoints in RMB sentence. - Tap on AIS targets in the map or the AIS radar, to set as Waypoint or navigation target.

  • 4.51.1

    Bug fix for the DSC sentence

  • 4.51.2

    More bug fixes for RMB sentences

  • 4.51.3

    -New setting to start navigation at race start. -MOB automatically starts navigation to MOB position. -Next leg bearing, length and TWA are now available as readout in race view.

  • 4.51.4

    A third race view has been added. Swipe up and down on the readouts in the race view, to changes between your selected readouts.

  • 4.52.0

    Bug fixing and changes to the CSV track export. From now on, the track export will have all data in ISO units, that means speeds (SOG, STW, AWS and TWS) in meters/second and all depth data in meters.

  • 4.53.0

    The app has been updated to iOS 16

  • 4.53.1

    Bug fix for the transmittes RMB sentence

  • 4.53.4

    Changes to Odometer calculations when receiving GPS data from NMEA.

  • 4.54.0

    You can now rotate your Buoy1, Buoy2 and Buoy3 around the position of the starting vessel. If the race committee changes the geometry of the racecourse due to wind shift, but maintains the distance to the marks, this is an easy way to rotate the entire course. You can rotate by entering a new course to Buoy1 or by entering by how many degrees you want to rotate the course.

  • 4.54.1

    Bug fix for route selection

  • 4.54.2

    If you don't get GPS data via NMEA input, COG and SOG from the internal GPS will now show up in the NMEA view.

  • 4.54.3

    A new setting has been added, where you can chose which NMEA0183 version of the RMB sentence should be used, if sending NMEA target.

  • 4.60.0

    Code cleanup and compilation for iOS/iPadOS 18 Files are alphabetic sorted and classified in import/export view. Signal flags overview added to the help view. Bug fix for 'Next Leg TWA' in Race View

  • 4.60.1

    The former force touch menu options in the watch app has been added as regular buttons

  • 4.60.2

    - New Swap feature in the start view, to swap positions for boat end and pin end. - New simple trim feature in the track view, where you can trim the start or the end of a track.

  • 4.60.3

    Bug fix for long tap in the Navionics maps

  • 4.60.4

    Bug fix for the AIS list view

  • 4.61.0

    Updated for iOS/iPadOS 26

  • 4.61.1

    Some errors in the layout, especially on iPad Minis fixed.

  • 4.61.2

    Bug fix for file import when shared from other apps

  • 4.61.3

    Bug fix for viewing large track files.

  • 4.62.0

    Bug fix for track export and NMEA view headers

  • 4.62.1 · 13 Jul 2026

    Accuracy for NMEA GPS data fixed and a new setting for User Equivalent Range Error is added. NMEA Accuracy is calculated as HDOP (Horizontal Dilution of Precision) from the GGA NMEA0183 sentence multiplied by the User Equivalent Range Error. For a standard consumer GPS receiver 5 would be the correct number. But newer units could be more accurate and require a value of ex. 3.

Alternatives

Availability by market

Data quality & evidence

Page completeness
Live store listing
Last verified
31 Jul 2026
Sources
App Store

Report a correction