Skip to content

Italy

Italian regularity events use three kinds of timing. Each has its own section on this page:

  • Prove di media (PM): average-speed tests with cumulative timing. Includes Regolarita Classica and Rally di Regolarita 50/60.
  • Prove cronometrate (PC): very short timed sections between pressure tubes, scored to 1/100 s.
  • CO and liaisons: time controls timed to the minute, on the road between tests.

Not yet checked by a competitor

This page comes from the written rules. It has not been read by an Italian competitor yet. The event's own regulations (RPG) always come first. It is also open whether a phone app can usefully assist with PCs at all.

Prove di media (PM)

Prove di media (PM) are the average-speed tests of Italian regularity events. They are timed from the start of the test, so you never press a TC inside the test.

How this format times you

In a PM the ideal time is cumulative: the target at any point is the start time plus the distance from the start divided by the imposed average. A mistake early in the test stays in the result at the next check. It is not forgiven.

  • Regolarita Classica. Each PM has an average speed and a number of checks on the time-distance table (TDT). There are at least 5 secret checks, none in the first 500 m. Checks are timed to the second and rounded. Penalty: 1 point per second, early or late, capped at 300.
  • Rally di Regolarita 50/60. The rules state the cumulative measure outright: from the Start to intermediate point A, from the Start to point B, and so on. There are at least 3 secret checks (4 if the PM is over 10 km), doubled if GPS timing is used, none in the first 1 km or in towns. Timing is to 1/10 s, rounded. Penalty: 1 point per 1/10 s. Early is uncapped, late is capped at 300. More than 20 % over the average from the start to any check costs 1000, then exclusion.
  • Change of average. A "cambio media" is allowed inside a PM, at a clear roadside feature that matches a roadbook diagram.
  • ALTA and BASSA. Rally di Regolarita 50/60 has two averages, chosen per car at entry. They differ by at most 3 km/h (class 50) or 5 km/h (class 60). The clerk of the course may lower them by circular.
  • Start. A standing start on a traffic light at a scheduled time. In Classica the standing start is optional, and the green light is then the official start time.
  • Roadbook distances are indicative in Rally di Regolarita 50/60. Your trip and the organiser's measure will not agree exactly.
  • 1000 Miglia. The event's own rules differ: at most 5 checks, GPS timing truncated to the second, a flying start from a "zero spazio" line 40 to 100 m after a yellow post, and a points table where early loses points faster than late. Use the event's regulations, not this page, to decide how to start.

In the app this is the simplest case: one start, no TC, and the ideal time runs on from the start. See Time controls and re-bases for the model.

Stage setup

Build the stage from the TDT. The full steps are in Turning the roadbook into a stage. For a PM:

  1. Open the stage sheet from Regularity | TSD and set Stage type to Regularity.
  2. Set Start signal to Time and enter the traffic light time. The default is the next full minute. Use Line only if the event has a flying start and you can draw the line where the zero point is.
  3. Add one section for each average. A change of average (cambio media) starts a new section. In each row enter any two of Distance, Speed and Time, and the app fills in the third. If the TDT gives total distances, you can enter Total distance instead.
  4. Leave Auto-switch sections by distance on (Options). The app then moves to the next section by itself when the stage trip reaches the section end.
  5. Name the stage after the test, for example "PM 1 Passo Rolle", and save it.
  6. For ALTA and BASSA, save two stages with the same sections and different speeds. Load the right one before the start.

Set the Rally Time to the official clock and calibrate the app before the event. Both matter much more here than in a re-base format. See Rally time and the start and Calibrating.

Button recipe

  1. At the start. Load the stage and press Start. The Ideal Time shows the start time, then a 30 second countdown.
  2. During the test. Read the Ideal Time: + is late (SPEED UP), - is early (SLOW DOWN). See Driving a test.
  3. At a landmark where the average changes (a section boundary). Press Sync (the button shows the distance, for example "Sync 3.20 km") when you are level with the landmark. It snaps the stage trip to the section boundary. If you are less than 15 % into the section it snaps back to the section start, otherwise forward to the section end. It does not restart the Ideal Time. Its number can move, because the distance changes.
  4. At any other landmark with a distance in the roadbook. Do not press Sync: it only knows the section boundaries, and past the first 15 % of a section it jumps the trip to the section end. Compare the trip with the roadbook and correct it. The - and + buttons in the bottom toolbar change the trip by 10 m on a tap, and in repeating steps of 100 m while you hold. They change every trip and do not restart the Ideal Time. Its number can move, because the distance changes.
  5. At the end. Press Finish when you cross the finish. If the stage has a Time or Line finish it finishes by itself.

Pitfalls

  • Never press a TC button inside a PM. Next Section + Restart, Sync + Restart, the TC button and a long press on the Ideal Time all record a TC. A TC restarts the ideal time from the moment you pressed it, so a lateness of 20 s is wiped out of the display, while the organiser's cumulative clock still counts it. Plain Next Section and plain Sync are safe.
  • Sync only at a section boundary, and at the landmark, not before it. Sync snaps to the nearest end of the section you are in. At a 2 km landmark inside a 5 km section it would put the trip at 5 km. If you press it 200 m before the boundary you lose 200 m of trip.
  • Wrong table. If you have loaded BASSA when your entry is ALTA, every offset is wrong. Check the speed in the first section before the start.
  • Early costs more than late in Rally di Regolarita 50/60. An early error is uncapped. The app shows early and late the same way and has no setting for this. When you are unsure, being slightly late is the safer side.
  • The last metres. The Finish button takes the time you press it. If the finish is a flying finish with a timing line before the roadbook finish, finish by Line or accept that the app's finish time is the crew's reference only.

How well the app fits

Good, with these limits:

  • The app shows tenths of a second under one minute. It has no setting for rounding or truncation. The organiser's rounding (to the nearest second in Classica, to 1/10 s in Rally di Regolarita 50/60, truncation at the 1000 Miglia) is not reproduced.
  • The app cannot know where the secret checks are. It tells you how far off you are now, which is the point of cumulative timing.
  • It cannot warn about the 20 % overspeed rule.
  • Quick switching between two average tables on the day means loading another saved stage. It works at a stop, not in a test.
  • A flying start from a "zero spazio" line (1000 Miglia) needs a Line start. A GPS line is only as exact as your drawing of it and the phone's fixes.

Legality note

Read the regulations of your event before you bring the phone. In the sources used for this page, the ACI rules for Classica and Rally di Regolarita 50/60 say that the organiser's calibration measurement may not be GPS and that GPS timing is allowed for the organiser's checks. They say nothing on what crews may use. That is left to each event's supplementary regulations, which can differ. Do not assume that a phone app is allowed. This app is a crew aid. It is not official timing.

Sources

Article numbers in brackets.

  • Regolarita Classica, Norme Generali 2026 [8.3, 8.15, 8.16, 8.18b, 8.20]: PDF
  • Rally di Regolarita, Norme Generali 2026 [1.4, 8.3, 8.7, 8.16, 8.17, 8.20]: PDF
  • 1000 Miglia 2026 RPG [10.4, 12, Allegati 7/8]: PDF

Prove cronometrate (PC)

Prove cronometrate are short timed sections between two pressure tubes, scored to 1/100 of a second. They are the part of an Italian regularity event that a phone can help with least.

A pacing aid only

The app records a TC at the moment you press, so it is only as accurate as your thumb. A press is never as accurate as a tube, and the display shows tenths of a second, not hundredths. The phone cannot score a PC to 1/100 s, and a short PC is too short for phone GPS. Use the app to practise your pace and to keep a rough count of the chain. Do not expect it to tell you your PC penalty.

How this format times you

  • What you are given. An imposed time for each PC, often with the distance. The time-distance table (TDT) shows it. You must hit that time between the start tube and the finish tube.
  • Size. A PC is at least 40 m and at least 7 s. PCs up to 150 m must average no more than 28 km/h.
  • Detection. A pressure tube fires when the front wheel crosses it. A second channel logs the rear axle. The 1000 Miglia times with a pressure tube to the hundredth.
  • Start. A free "flying" start over the tube. The crew crosses the start tube when it chooses, within about 5 s of the marshal's "via libera". Stopping between the yellow and the beige zone signs costs 100 penalties, so the start is in effect rolling.
  • Chained PCs. The time at the finish tube of a PC is the start time of the next PC. Each PC is timed from the car's actual crossing of the previous tube. An error does not carry over.
  • Penalty. 1 point per 1/100 s, early or late the same, capped at 300 per PC, with no tolerance. The total is multiplied by an age coefficient based on the car's build year. That does not change the ideal time.

So every tube is a re-base. In the app that is a TC at each tube. See Time controls and re-bases.

Stage setup

  1. Set Stage type to Regularity.
  2. Set Start signal to Tap. You tap the start as you cross the start tube. Line is possible if you draw a line across the tube, but the line is only as exact as the phone's fixes and your drawing.
  3. Add one section for each PC. Enter the Distance and the Time from the TDT, for example 100 m and 10 s. The app works out the speed. The target of a PC is a time, not a speed.
  4. Open Options and switch Auto-switch sections by distance off. A PC is short and phone GPS at one fix per second cannot place the tube. You switch sections yourself, and each switch sets the stage trip to the tube's distance.
  5. Save the stage, for example "PC 1-3 Passo Giau".

Button recipe

  1. Start tube. Press Start in the stage sheet. The stage is then waiting for the tap. Tap the Ideal Time as the front wheels cross the start tube.
  2. Each tube. Press Next Section + Restart as the front wheels cross the tube. It records a TC at the tube's distance (the end of the section) and moves to the next PC. The Ideal Time restarts at the moment of your press, plus the Restart time, which is 0 here.
  3. Last tube. On the last PC the button reads Finish. Press it at the finish tube. It stores no TC. The finish stands in as the last one.
  4. During a PC. The Ideal Time tells you how far ahead or behind the target time you are. Use it to pace, not to score.

Pitfalls

  • Your thumb is the timer. If you press 0.3 s after the tube, that is 30 penalty points the app does not see. The next PC is then timed from your press, not from the tube.
  • Do not use plain Next Section. It does not record a TC, so the next PC is timed from the start and your error carries over. That is the opposite of how a chained PC works.
  • Keep a hand free. The press must happen as you cross a tube. Pressing at the wrong moment shifts the next PC's target by the same amount.
  • Short PCs. A 40 m PC at 7 s is about 20 km/h. At that size phone GPS noise is larger than the whole section, so the trip distance cannot confirm that you reached the tube.

How well the app fits

Poorly, and this page says so. The app can:

  • show a target time per PC and your pace against it;
  • re-base at every tube with one button.

The app cannot:

  • time to 1/100 s: a press is only as exact as your thumb, and the display shows tenths;
  • detect the tube by itself;
  • use the rear-axle channel, tube-to-tube chaining at the true crossing or the age coefficient.

Use it to rehearse a PC chain before the event, for instance with Demo mode, and as a rough pace gauge on the day. The rules are clear, but how useful a phone is for PCs is doubtful.

Legality note

Read the event's supplementary regulations on devices. The 1000 Miglia and the ACI texts used here set out how the organiser times PCs. They contain no statement on a crew's phone. Do not assume it is allowed.

Sources

Whether the app can score well here is doubtful. Article numbers in brackets.

  • Regolarita Classica, Norme Generali 2026 [8.15, 8.18b, 8.20, 8.21, 1.4]: PDF
  • Regolarita Auto Moderne 2026 [11.8, 11.11]: PDF
  • 1000 Miglia 2026 RPG [1.30, 10.3]: PDF

Open item. Is this format feasible for a phone app at all? Very short PCs are within GPS noise, and no competitor has yet said whether a phone is useful for PCs.

CO and liaisons

A CO (controllo orario) is an Italian time control. You must arrive inside a one-minute window. This section shows how to count down to a CO with the time card.

How this format times you

  • The window is the whole minute. A slot of 14:01 is clean from 14:01:00 to 14:01:59 [Classica 8.14].
  • Nothing is made up later. Lateness or earliness at a CO must not be recovered at the next CO. Each CO is a new start for the next liaison, so the schedule re-bases at every CO.
  • Penalty. 100 points per minute early or late, with late capped at 300 [Classica 8.20]. In Rally di Regolarita, early costs 200 per minute.
  • Between COs you drive on public roads at the legal speed. The time card gives the time for each CO.

Setup

  1. Open Liaison from the drawer, in the Regularity | TSD group.
  2. Tap Last TC, Allowed Time, Next TC or Time to TC to open the Time controls sheet.
  3. Choose Time card and enter each CO of the day. See Liaisons for the full steps.
  4. For a CO printed as a clock time, use Fixed time. For a CO printed as an allowed time since the previous one, use Allowed Time. An Allowed Time control is calculated from the previous control's scheduled time, not from when you arrived. That matches the rule above: your earliness or lateness does not move the next CO.
  5. Set the Rally Time to the official clock first. See Rally time and the start.

Button recipe

  1. Drive towards the CO. Time to TC counts down in whole seconds, rounded up, so it reads 00:00 at the moment the CO is due.
  2. For a CO entered as a whole minute, the due time is that minute at :00 (14:01 means 14:01:00). Aim to cross the line when the countdown is between 00:00 and -00:59. That is the clean window.
  3. A countdown that is still above zero means you are early. Wait somewhere safe, off the road, until it reaches 00:00.
  4. After the CO the time card moves to the next control by itself.

Pitfalls

  • The time card is not saved. The times you enter are kept only while the app is running. If the app restarts, you must enter them again. Keep the paper time card at hand.
  • Mixing up the window. The countdown reaches 00:00 at the start of the minute, and the clean window is the 59 seconds after it. Arriving at 14:00:57 for a 14:01 CO is a minute early, not clean.
  • Delayed stage. If the organiser changes a time, edit that control and change it to a Fixed time.
  • Early arrival. Wait. It costs as much as being late.

How well the app fits

Good. Liaison mode does the one thing this format needs: a countdown to a time, in seconds, off the official clock. It cannot know the organiser's own clock, so check the Rally Time. Quick TC and Next Section act on a running stage and do not change the liaison time card.

Legality note

The device rules in the sources used here do not name a countdown on a phone. Read the event's supplementary regulations. This is a crew aid, not official timing.

Sources

Article numbers in brackets.

  • Regolarita Classica, Norme Generali 2026 [8.14, 8.20]: PDF
  • Rally di Regolarita, Norme Generali 2026 (early 200 per minute) [8.20]: PDF
  • App behaviour: Liaisons and the time card.