CMS iRTES Sporting Regulations - 2026

Changes from Last Version

Version 2.2 includes the following updates and clarifications:

• Replaced the previous Code 60 countdown with a five-second, radio-only Race Control countdown.
• Removed the former stopping, queuing, wave-by, and Queuing Zone procedures. Cars capable of proceeding will remain moving throughout a Code 60.
• Added revised GTP and GT3 field-formation procedures, including the overall GTP leader serving as the pace car and a five-to-seven-second class gap for GT3.
• Clarified pit-lane operation, passing restrictions, the return-to-green procedure, and post-race compliance review.
• Updated the Request to Tow in iRTES procedure to clarify the exception for an automatic iRacing tow caused by a computer, network, or connection failure.

Series Overview

Welcome to iRacing Team Endurance Series (iRTES) 2026. iRTES is loosely modeled after the FIA World Endurance Championship. All rounds will feature 2-3 drivers per team competing in GTP and GT3 across a three-race schedule. All races will use solo qualifying sessions, with race lengths ranging from 3 hours to 6 hours. We are very excited to bring the series back for its 6th season, with a renewed focus on the racing itself. We hope you will join us for what promises to be an exciting season and the beginning of a new chapter for iRTES - one we can build on for many years and seasons to come.

2026 Registration Timeline

The 2026 season will be limited to a total racing grid size of 30 entries: 18 reserved for GT3 and 12 for GTP. If we exceed the entry list, a reserve list will form. For more details on race entry declaration requirements, see Race Registration Requirements.

• April 1st - April 15th: Special Invites
• April 15th - May 10th: Returning entries and CMS community members
• May 11th - Season start: Public entries

All entries will be subject to approval by CMS Admins and may be refused for any reason, without explanation, if deemed appropriate and in the best interest of the community and the series.

Entry Fees and Charters

The season entry fee for 2026 will be $15 USD per car, payable to CMS via PayPal at donate@cmsracing.com. Upon approval of your grid entry, you will be cleared to make payment. If payment is not made within a reasonable time, your entry may be passed over for the next eligible team. Special arrangements can be made for payment if needed.

Additionally, teams who receive Special Invites will be given an opportunity to buy into a permanent charter for iRTES. This means they will be guaranteed a spot in any future seasons. Similar to purchasing a PSL license, that fee will be $100 USD per car, payable at the time of registration. So long as the team maintains good standing in the CMS community, it will automatically be entered and protected on the grid for all future iRTES seasons. Teams will still have to pay the appropriate yearly season entry fee in addition to the charter. The charter fee is a one-time expense and guarantees entry into the series for the long term.

Eligible Cars

GTP/LMDh Class

All currently available non-legacy iRacing cars.

GT3 Class

All currently available non-legacy iRacing cars.

Note: If there are multiple versions from a manufacturer, the most recently released car will be used.

Example: the GT3 McLaren EVO, rather than the older McLaren GT3, is used in iRTES.

Additional Information

All participants must be familiar with CMS General Rules & Regulations (“CMS General Rules”).

Series Schedule

Server Schedule

• Practice: 75 minutes - 1530 GMT
• Mandatory Drivers Meeting: 1630 GMT
• Solo Qualifying: 15 minutes (3 laps) - 1645 GMT
• Race: 3 up to 6 hours - 1700 GMT

Official Practice Sessions

Each race will have one or more corresponding practice sessions designated as official sessions. These will typically take place in the week or days leading up to the event. All members are encouraged to attend whenever possible to gain time with the group and identify any technical issues before race day. The sessions will be announced on our Discord server and in race briefings and will be labeled as “Free Practice” sessions.

Championship Points

GTP & GT3 Classes

Tie Breakers

In the event of tie at the series conclusion, a countback of class finishing positions will be used to break any ties. The first tiebreaker will be the number of first place finishes; if a tie remains, then second place finishes; then third place finishes, etc., until the tie is broken.

Server Settings

• Dynamic Weather (a general weather forecast will be provided in the race briefing for planning purposes)
• Dynamic Track
• 1 Fast Repair

Tire and Fuel Limits

The series may, in some cases on a race-by-race basis, include tire and fuel limitations. Specifically, teams may be allocated only a certain number of tire sets for the race, or the fuel tank may be set to less than 100%. This will be communicated in advance in the pre-race briefing for planning purposes. There will be no other BoP adjustments in the series, such as weight or power changes, unless the admins determine that an adjustment is necessary after observing a significant impact on the quality of events.

Starts

All events will use a rolling start. The GTP pole sitter will hold the GTP field at the track’s posted pacing speed until the pole sitter begins acceleration in the acceleration zone, or the green lights/flag are displayed, whichever occurs first.

The GT3 pole sitter will hold the GT3 field at the track’s posted pacing speed until the pole sitter begins acceleration in the acceleration zone or the green lights/flag are displayed, whichever occurs first.

All drivers must maintain position until the start, with no “laying back” or other attempts to game or jump the start. No tire warming or weaving is allowed; however, dragging the brakes is deemed acceptable. The designated acceleration zone will be released in each event brief. The point at which passing can commence during a race start will also be noted in the briefing.

Orange Zone

Safety Cars and Code 60

Instead of a traditional full-course yellow, iRTES uses a Code 60 procedure to slow the field, neutralize the course, and allow Race Control to manage unsafe conditions.

1. Initial Code 60 Call

When a Code 60 is called, Race Control will announce over the radio:

The countdown will be given over the radio only. It will not be displayed on screen because a visual message may not remain synchronized with the Race Control countdown.

As soon as the countdown begins, all drivers must immediately lift off the accelerator and begin slowing in a safe and controlled manner. By the end of the five-second countdown, every car must be traveling at the designated Code 60 speed with the pit speed limiter engaged.

Unless Race Control announces otherwise, the designated Code 60 speed will be the pit-lane speed configured for that track.

2. Pit Lane

The pits will remain open throughout the Code 60 unless an incident is blocking or interfering with pit entry or pit exit. Any pit-lane closure will be announced by Race Control.

Teams may elect to pit during a Code 60, but they may lose positions as a result of taking service.

Cars rejoining from pit lane must yield to cars already on track and may merge only when a safe gap is available. A car exiting pit lane may not force an on-track car to slow, change line, or yield.

3. Passing During Code 60

Except for the Race Control-directed field-formation procedures described below, passing is not permitted for cars remaining on track during a Code 60.

When a car ahead enters pit lane, cars remaining on track may continue forward and close the gap to the next applicable car in line. Passing a damaged, stationary, or clearly disabled car is permitted only when necessary to proceed safely.

4. Forming the GTP Field

Once Race Control confirms that all cars are safely on the limiter, GTP cars positioned behind the overall GTP leader may be instructed to carefully leave the limiter and pass GT3 traffic ahead of them.

Those GTP cars will form behind the overall GTP leader while maintaining their exact GTP order. GTP cars may not pass one another during this process.

The overall GTP leader will serve as the pace car throughout the Code 60 and will maintain the pace directed by Race Control.

5. Forming the GT3 Field

Once the GTP field is organized, Race Control will instruct the GT3 cars to safely leave the limiter and catch the rear of the GTP field.

The first GT3 car in the restart line must maintain a gap of approximately five to seven seconds behind the final GTP car.

GT3 cars must maintain their existing GT3 order while catching the field and may not pass one another.

There will be no class sorting, wave-bys, or repositioning based on class standings. Relative order within each class will remain unchanged unless a car elects to pit.

6. Return to Green

Once the field is organized, Race Control will return the race to green the next time the field approaches the defined race-start or acceleration zone.

The restart will follow the same procedure used at the beginning of the event. The overall GTP leader will control the GTP restart, and the first GT3 car in the restart line will control the GT3 restart while maintaining a gap of approximately five to seven seconds behind the final GTP car.

The first GT3 car in the restart line may not be the current GT3 class leader. No driver may accelerate early, lay back, jump the restart, or begin passing before permitted under the event's published start procedure and Race Control instructions.

Additional Code 60 Rules

Drivers are not permitted to serve penalties during a Code 60 period.

Race Control may also announce “CAUTION SECTOR (1, 2, or 3) - SLOW OR DAMAGED CAR OFF PACE.” Drivers must respond appropriately to any sector caution and follow all Race Control instructions.

Compliance and Review

There will be no stopping on track, queuing, wave-bys, or additional sorting of the field during a Code 60.

Teams found to be speeding, passing improperly, failing to follow Race Control instructions, or otherwise violating the Code 60 procedure may be subject to a post-race Incident Review Request initiated by Race Control, the administration team, or another competitor. Timing data, telemetry, replay evidence, and Race Control communications may be reviewed when determining compliance.

Request to Tow in iRTES

In iRTES for 2026, we will further simulate real-world racing. To that end, if one or more cars are involved in an accident and are not able to safely return to the pits in a controlled manner while remaining off the preferred racing line, they may need to tow. This is a normal feature that we are all aware of in iRacing. However, for iRTES, towing will only be allowed when approved by Race Control.

Race Control & Communications

Race Control instructions, communications, penalties, and the pre-race briefing will be conducted using iRacing voice and text chat, utilizing the @RACECONTROL channel. In-race voice communications, as well as text macros, should be kept to a minimum during the race. Abusive and/or profane speech or language in iRacing voice and text chat, or in Discord voice or text channels, may lead to probation, suspension, or a ban from the league.

Blue Flags

In accordance with the CMS General Rules, blue flags are advisory in nature. It is the responsibility of all drivers and teams participating in iRTES to read and comply with the CMS General Rules regarding blue flags. Please see CMS General Rules & Regulations for details.

Team Rules

To be eligible to race, a team's drivers must be registered to that team within iRacing. All drivers must be approved members of the iRTES Endurance league on iRacing. Teams may register up to four drivers per entry. Points cannot be carried over from an existing entry to a new entry. If an entry changes to a different car mid-season, all previous points will be forfeited.

Class and Driver Requirements

• All drivers must hold a Class C license with a minimum 4.0 Safety Rating to compete in iRTES.
• Drivers in the GTP class must have a minimum iRating of 1800 before the start of the season.
• Drivers in the GT3 class do not have an iRating minimum, but all entries remain subject to approval by CMS Admins for gridding.

Numbers and Templates

Official templates will be provided with number plates and windshield banners for all cars in iRTES. They are mandatory. If a team runs without the required templates, it will receive a DSQ in the event. Templates will be shared on Discord, and a download link will be provided to give everyone ample time to paint prior to the season start. Teams will be required to upload their paints to a CMS Admins share, and we also encourage all teams to use the Trading Paints iRacing application.

• GTP cars will have the ability to reserve a car number between 2 and 99 at registration.
• GT3 cars will have the ability to reserve a car number between 100 and 199 at registration.

Race Registration Requirements

For each race, we want to field a full grid of 30 cars. Therefore, team managers will be required to inform the CMS Admin team one week prior to each race whether they will attend the event. This will allow us to offer reserve entries the opportunity to grid with plenty of time to prepare. If a team does not communicate with us or does not demonstrate confidence in its ability to field its car, CMS may move that team to reserve status and promote another team at its discretion.

Qualifying Driver

The driver who qualifies the car must start the race.

Drive Times

All teams must adhere to iRacing ‘Fair Share’ requirements. Teams must use at least two, but no more than three drivers per event.

Incident Count

After the accumulation of 25 incident points, offending teams will automatically receive a drive through penalty from iRacing Race Control. After 40 incidents, teams will be disqualified from the event by iRacing Race Control.

Red Flag Conditions

If the race must be stopped for any reason (e.g., mass disconnects, etc.) the following procedures shall apply at the discretion of Race Control.

Less Than 50% of Race Duration Completed

If less than half of the scheduled duration has been covered, Race Control will announce that the race will be restarted. A new race server will be started, and the race will begin anew. At the discretion of Race Control, the length of the race may be decreased. A race that completes more than 25%, but less than 50% of the scheduled duration will award half-points.

More Than 50% of Race Duration Completed

If more than half of the scheduled duration has been covered, Race Control will direct the remaining cars to drive back to the pits and line up at the pit lane exit in order entered. As drivers rejoin the session, Race Control will initiate a SC period and give further instructions.

If Race Control determines the race cannot be restarted (e.g., insufficient remaining time or laps), the race finishing order will be determined using the last ‘good’ lap before the manifestation of the circumstance(s) necessitating the race stoppage. Full points will be awarded.

Penalties

Penalties can be applied in one of two ways:

1. iRacing automated Race Control penalties (including but not limited to slow-downs, black flags, incident limits, etc.)
2. Post Race Incident Review Submissions from Teams or Admins ruled on by independent steward team

Any penalties arising from stewards’ post-race decisions will be applied to the race results. Therefore, results are not final until all open investigations are closed. For the last race of the seasson, any normal penalties that would otherwise have been assigned for the next race will be converted to time penalties, and the results will be adjusted accordingly. Note that for the 2026 season 6 all iRTES penalties will be converted to time per these series regulations due to the shorter nature of the season and limited resources in race control.

These league-wide rules can be found at CMS General Rules & Regulations.

Reporting of Incidents

At the conclusion of the event, competitors may submit an incident through the normal CMS IRR process. Teams will have between 12 and 60 hours from the time the official race replay is posted to submit an Incident Report to the CMS Race Review Team at CMS Incident Review Request.

All incident decisions, whether in-race or post-race are final.

Sample Penalty Matrix

Penalties assigned will follow the table below as a general guideline.

Any incident not listed in the table above will be subject to a penalty at the discretion of the stewards. Additionally, at the discretion of the stewards, any penalty may be enhanced or reduced as deemed necessary based on the circumstances of the incident.

CMS Sporting Conduct

Notes on the Golden Rule (GR)

Observing the Golden Rule is entirely up to the drivers, and there is no guarantee it will result in a reduced penalty amount (if an IRR is filed). However, stewards may exercise leniency in reducing a penalty if:

• It is performed immediately at the scene of contact.
• It is done in a safe manner and without impeding other drivers on track.
• Damage to the other driver is minimal, and he or she did not suffer position loss or heavy damage.

Prizes and Awards

We are very excited to share the prize package for the 6th season of the iRacing Team Endurance Series (iRTES). The awards listed below are intended to recognize performance, consistency, endurance, and sportsmanship across the 2026 season.

1. Series Champion Personalized Decanter Sets - Personalized trophy whiskey/bourbon decanter sets will be awarded to the Team Manager and to any driver who competes in all three points-paying events for the highest-finishing GTP team and the highest-finishing GT3 team. These awards are planned to be customized with the driver or team name, along with iRTES/CMS branding for 2026. Free shipping will be provided to recipients in the United States. For international teams, a substitute award may be used due to shipping or tariff restrictions, and/or CMS staff may work with the Team Manager in the appropriate region to arrange a comparable prize.
2. Monster 50+ Awards - The Monster 50+ Award is a driver award for participants aged 50 and older. Eligible drivers may register for this prize in a designated area of the Discord server. One winner in GTP and one winner in GT3 will receive a Monster Trophy, with free shipping provided within the United States. A substitute award may be used for international drivers due to shipping restrictions. In the event of a tie, the tiebreaker will be the final championship standing of the team for which the driver competed. Drivers must participate in a minimum of two events to be considered for this award.
3. Clean Team Awards - CMS will award a $50 cash prize to one GTP team and one GT3 team that compete in all three races and record the fewest incidents over the season as counted by the iRacing system. In the event of a tie, the final championship position will be used as the tiebreaker. This is a team award and will be paid to the Team Manager, who may distribute it to other team members at his or her discretion.
4. Iron Man Driver Medals - CMS will provide Iron Man medals to drivers who compete in all three events and complete the most laps in the series. These special medals are intended to recognize the endurance and commitment shown by drivers throughout the season. A substitute award may be used for international drivers due to shipping restrictions.
5. Sportsmanship and Leadership Recognition - Two drivers will receive special recognition and a certificate, as selected by the iRTES Admins at the conclusion of the season. These awards are intended to honor drivers who demonstrate a high degree of sportsmanship, integrity, racecraft, and participation throughout the series. This is a subjective but highly regarded award intended to recognize the type of leadership and community representation that is especially valued within CMS.