Team events and endurance races · Help

Some iRacing races let several people share one car: the Daytona 24, the Bathurst 12 Hour, Suzuka 1000km, the Global Endurance Tour, the Nürburgring Endurance Championship and the rest of the endurance calendar. These work differently from an ordinary race, so they are shown differently on irstats.

The entry is the competitor

In a normal race, each line on the results table is a driver. In a team event, each line is an entry — one car, under the name it raced under — and the drivers who shared it are listed underneath.

That is not a display choice, it is how the results work. A team event scores the car, so everyone who drove it finished in the same position. If your entry came home fourth, every driver in it finished fourth, whether they ran two hours or twenty minutes.

Your own numbers, the car's result

Under each entry you will find every driver who took the wheel, with the laps they personally completed. Their individual figures are their own:

Laps you drove, not the car's total
Incidents you picked up
Best and average lap from your stints
iRating change, which iRacing works out per driver

Only the finishing position is shared, because only the car has one.

Each driver's name links to their profile, so you can follow anyone in the field straight from the results.

Running solo

An endurance race does not require a team. Many entries are a single driver going the whole distance alone, and in the shorter endurance rounds solo entries are often more than half the field.

A solo entry is marked Solo on the results table. It is a full result in every sense — the lap count, the incidents and the rating change are all one person's, and nothing about it is shared.

Team names

An entry shows the name it carried on the day. Teams rename themselves, merge and rebrand, so a result from two years ago keeps the name that actually appeared on the timing screen rather than being quietly rewritten to whatever the team is called now. Team pages show the current name.

Which races appear

Team events are official iRacing sessions and are treated like any other official race. They show up on a driver's page alongside their solo racing, and on the race page for the session itself.

Team results are listed in their own section on a driver profile rather than being mixed into career totals such as starts and wins. A shared result belongs to several people at once, and rolling it into one person's win count would overstate it. Solo endurance runs are recorded with the same distinction so the difference stays visible.

Privacy

Drivers listed inside an entry follow exactly the same name rules as anywhere else on irstats. Members covered by regional privacy protection appear abbreviated unless they have chosen to be public, and anyone who has asked to be removed stays removed. See Names and privacy.

Team pages

Every iRacing team that has raced an event has its own page: its record, the drivers who have driven for it, the series it runs and how its season has gone. Browse or search them all from Teams in the top navigation.

Teams are identified by their iRacing team id, never by name. Two teams with near-identical names are two different teams, and a team that renames itself keeps the same page.

What the Teams list counts

The list ranks teams by entries, and one entry is one car in one race however many drivers shared it: a Daytona 24 entry with five drivers is a single entry, and its class win is a single win. That is the same way the team's own page counts, so the two always agree. Drivers is how many different people have raced for the team, and Last raced is its most recent event. Wins are counted in class.

The list is rebuilt through the day rather than the moment a race finishes, so a team's newest result can take a few hours to move it up the order. A team's own page is always up to the minute.

Finding a team that wants drivers

Teams can mark themselves as recruiting on iRacing, and irstats shows that where you are looking for a seat:

On the Teams page, recruiting teams carry a Recruiting badge, and the banner at the top says how many there are. Following it narrows the page to recruiting teams only, ranked the same way, across every team on record rather than the ones already listed. It works alongside search, so you can look for recruiting teams whose name you half remember, and the filtered view has its own link you can share or bookmark.
On a team's own page, a recruiting team says so at the top. If the team has added a website or Discord link, the banner takes you straight there; otherwise it points you at the owner's profile.

Recruiting is the team's own setting on iRacing, so treat it as an invitation to get in touch rather than a promise of a free seat. A team without the badge has not necessarily said no — it may simply never have set the option. Your iRacing setting is the source of truth: change it there and the badge here follows it.

Claiming your team page

If iRacing lists you as a team's owner, you can claim its page and write what appears on it.

Sign in with iRacing.
Open your team's page. If you are its owner, a Your team panel appears at the bottom.
Choose Claim this team.

The claim is verified against iRacing's own record of who owns the team, so there is nothing to review and no way to claim a team that is not yours. Once claimed you can add a short description and a link — your site, your Discord, wherever you want people to go. The link must be a web address (https://…); if your team is recruiting, that is where the banner on your page sends drivers.

The endurance calendar

Endurance in the top bar, or irstats.com/endurance, lists the endurance and special events themselves, newest first, with how many cars entered, how many drivers shared them and how strong the field was. It is the quickest way into a race you watched or drove without knowing its session id.

The home page carries a short version of the same list, and it leads with the special events — the once-a-year races like the Daytona 24, the Spa 24 and the 1000km — rather than the series that run every week. You get the two that ran most recently, named with the circuit they run at, and for each of their last three runnings the winner of every class, fastest class first. Where a race had more classes than fit, the count of the rest sits at the end of the last line. Pick a running for its full results, the event name for its schedule and standings, or Full calendar for everything on record.

The page opens with a card for every endurance series — the same grid the series index uses — showing how many times each one has been run, its typical strength of field and field size, and when it last ran. Pick a card for that series' schedule and standings.

Below the cards is every running on record, newest first, a page at a time; use the numbered pages at the bottom to go further back. A race that ran across several splits appears once, as its top split — the one iRacing puts the fastest field in.

Standings for a team series

A team series is scored on the entry — the car — not on the individual drivers who share it. So on a team series page the standings are team standings: one row per team, with its points, starts, wins, poles and laps led, and the team name linking to its profile. Teams do not carry an iRating, so that column shows laps led instead.

For the same reason, the winner of each race in Recent races is the winning team, not one of its drivers.

In Discord

If your server has the irstats bot, team events are there too:

/team looks up any iRacing team by name and shows its endurance record, its best result and the drivers who have raced for it.
/driver includes a team and endurance section in the detail thread under the reply, listing the driver's entries and the teams they have driven for.

Positions in both are the in-class result, for the same reason they are on the site.

Driver profiles — what else is on a driver page
Team championships — league team scoring, which is a separate feature for league organisers