VINTAGE MULTICLASS
Apex Online Racing
League Information
General Information:
- League structure: Multiclass season with GT4 and select GT3 Vintage cars (no car younger than 2017)
- Race format: 4 races of 90 minutes. Race no. 1 will have a starting grid based on your best laps on our hot lap server. Races 2, 3 and 4 are going to use reverse starting grids based on the championship standings. Tyre changes are going to be optional
- Regions: Assetto Corsa Competizione leagues currently only have European starting times. Drivers from all around the world are allowed to take part in the leagues, as long as their connection is suitable enough towards Europe.
- Assists: All tiers will have the maximum stability control setting to zero and auto-steer disabled. Other than the ones mentioned here, all assists are allowed to be used.
- Day/time: League events for all tiers will take place on Tuesday nights from 7:30pm (UK time).
Your best lap on the Vintage Multiclass Hotlap server decides on your starting positon for race 1, as described in season rules.
Beware: Please set your hotlap in the same car you are going to use for the season. If you set it in any other car, you will be starting from the back in race 1.
If you are yet undecided on which car you will choose, please use server ApexOnline.Racing #96 | ACC Vintage Multiclass - Rolling FP - Oulton Park | Sponsored by SimSok.com | #AORRP for practicing and choosing a car.
Hotlap Server password: Apex
Hotlap Server name:
- ApexOnline.Racing #95 | ACC Vintage Multiclass - Quali Hotlaps - Oulton Park | Sponsored by SimSok.com | #AORVMQ
# | Driver | Car | Best Run | Best Lap | Gap to #1 | Best Avg | Avg Gap | Valid |
---|---|---|---|---|---|---|---|---|
1 | Simon Beeg | 01:33.522 | 01:33.522 | 01:33.522 | 00.000 | |||
2 | Rytis Kazlauskas | 01:33.882 | 01:33.882 | 00.360 | 01:33.882 | 00.000 | ||
3 | Robin Moe | 01:34.037 | 01:34.037 | 00.515 | 01:34.037 | 00.000 | ||
4 | João Manso [RPMS] | 01:34.065 | 01:34.065 | 00.543 | 01:34.065 | 00.000 | ||
5 | Stefano Zanobini | 01:34.112 | 01:34.112 | 00.590 | 01:34.112 | 00.000 | ||
6 | Eike Planer | 01:34.420 | 01:34.420 | 00.898 | 01:34.420 | 00.000 | ||
7 | Nathaniel Shirley | 01:34.530 | 01:34.530 | 01.008 | 01:34.530 | 00.000 | ||
8 | Jonathan Clifford | 01:34.585 | 01:34.585 | 01.063 | 01:34.585 | 00.000 | ||
9 | Thomas Allendorf | 01:34.590 | 01:34.590 | 01.068 | 01:34.590 | 00.000 | ||
10 | Daniel Crinson | 01:34.595 | 01:34.595 | 01.073 | 01:34.595 | 00.000 | ||
11 | Sam Mawdsley | 01:34.700 | 01:34.700 | 01.178 | 01:34.700 | 00.000 | ||
12 | Alexa Gates | 01:34.702 | 01:34.702 | 01.180 | 01:34.702 | 00.000 | ||
13 | Daniel Lopez | 01:34.787 | 01:34.787 | 01.265 | 01:34.787 | 00.000 | ||
14 | Declan Brogan | 01:34.865 | 01:34.865 | 01.343 | 01:34.865 | 00.000 | ||
15 | arne korv | 01:35.155 | 01:35.155 | 01.633 | 01:35.155 | 00.000 | ||
16 | Catalin Iliescu | 01:35.527 | 01:35.527 | 02.005 | 01:35.527 | 00.000 | ||
17 | Ryan Rees | 01:35.555 | 01:35.555 | 02.033 | 01:35.555 | 00.000 | ||
18 | Xander van Dijk | 01:35.635 | 01:35.635 | 02.113 | 01:35.635 | 00.000 | ||
19 | Jonas De Meyer | 01:35.655 | 01:35.655 | 02.133 | 01:35.655 | 00.000 | ||
20 | Thomas Jack | 01:35.877 | 01:35.877 | 02.355 | 01:35.877 | 00.000 | ||
21 | Maurice Miller | 01:35.915 | 01:35.915 | 02.393 | 01:35.915 | 00.000 | ||
22 | Penelope Dobbins | 01:35.915 | 01:35.915 | 02.393 | 01:35.915 | 00.000 | ||
23 | Kalimazoo | 01:36.032 | 01:36.032 | 02.510 | 01:36.032 | 00.000 | ||
24 | JP Mc Kinley | 01:36.177 | 01:36.177 | 02.655 | 01:36.177 | 00.000 | ||
25 | Samuel Christiansen | 01:36.252 | 01:36.252 | 02.730 | 01:36.252 | 00.000 | ||
26 | Nojus Sabas | 01:36.350 | 01:36.350 | 02.828 | 01:36.350 | 00.000 | ||
27 | StevieB Beeswax Racing | 01:36.365 | 01:36.365 | 02.843 | 01:36.365 | 00.000 | ||
28 | Chris Bradbury | 01:36.485 | 01:36.485 | 02.963 | 01:36.485 | 00.000 | ||
29 | Mert Sevinc | 01:36.765 | 01:36.765 | 03.243 | 01:36.765 | 00.000 | ||
30 | Marton Cynolter | 01:36.970 | 01:36.970 | 03.448 | 01:36.970 | 00.000 | ||
31 | John Nova | 01:37.460 | 01:37.460 | 03.938 | 01:37.460 | 00.000 | ||
32 | Alastair Baldwin | 01:37.477 | 01:37.477 | 03.955 | 01:37.477 | 00.000 | ||
33 | silver fox | 01:37.737 | 01:37.737 | 04.215 | 01:37.737 | 00.000 | ||
34 | Paul Martin | 01:38.162 | 01:38.162 | 04.640 | 01:38.162 | 00.000 | ||
35 | Leonardo Porco | 01:40.957 | 01:40.957 | 07.435 | 01:40.957 | 00.000 | ||
36 | Vency Raychinov | 01:41.192 | 01:41.192 | 07.670 | 01:41.192 | 00.000 | ||
37 | Kristers Podēns | 01:41.345 | 01:41.345 | 07.823 | 01:41.345 | 00.000 | ||
38 | Ivan Borimechkov | 01:41.642 | 01:41.642 | 08.120 | 01:41.642 | 00.000 | ||
39 | Krab Athor | 01:41.692 | 01:41.692 | 08.170 | 01:41.692 | 00.000 | ||
40 | Anton van Someren | 01:41.797 | 01:41.797 | 08.275 | 01:41.797 | 00.000 | ||
41 | Stefan Monz | 01:42.012 | 01:42.012 | 08.490 | 01:42.012 | 00.000 | ||
42 | Javi Hernando | 01:42.052 | 01:42.052 | 08.530 | 01:42.052 | 00.000 | ||
43 | Luca Ziege | 01:42.085 | 01:42.085 | 08.563 | 01:42.085 | 00.000 | ||
44 | Hans Peter | 01:42.157 | 01:42.157 | 08.635 | 01:42.157 | 00.000 | ||
45 | Damir Makhmutov | 01:42.215 | 01:42.215 | 08.693 | 01:42.215 | 00.000 | ||
46 | Calvin Leijdekkers | 01:42.312 | 01:42.312 | 08.790 | 01:42.312 | 00.000 | ||
47 | Dan Barnard | 01:42.340 | 01:42.340 | 08.818 | 01:42.340 | 00.000 | ||
48 | Jan Robohm | 01:42.350 | 01:42.350 | 08.828 | 01:42.350 | 00.000 | ||
49 | Brian Anderson | 01:42.640 | 01:42.640 | 09.118 | 01:42.640 | 00.000 | ||
50 | Claudio Zazza | SKY | 01:42.650 | 01:42.650 | 09.128 | 01:42.650 | 00.000 | ||
51 | dakuza | 01:42.685 | 01:42.685 | 09.163 | 01:42.685 | 00.000 | ||
52 | Maciej Chyrc | 01:42.685 | 01:42.685 | 09.163 | 01:42.685 | 00.000 | ||
53 | Jay Janz | 01:42.792 | 01:42.792 | 09.270 | 01:42.792 | 00.000 | ||
54 | Daniel Durette | 01:42.797 | 01:42.797 | 09.275 | 01:42.797 | 00.000 | ||
55 | Mateusz Nitsche | 01:42.827 | 01:42.827 | 09.305 | 01:42.827 | 00.000 | ||
56 | Benjamin King | 01:42.895 | 01:42.895 | 09.373 | 01:42.895 | 00.000 | ||
57 | Manuel Rutter | 01:42.985 | 01:42.985 | 09.463 | 01:42.985 | 00.000 | ||
58 | NynS | 01:42.985 | 01:42.985 | 09.463 | 01:42.985 | 00.000 | ||
59 | Kiki Mac | 01:42.987 | 01:42.987 | 09.465 | 01:42.987 | 00.000 | ||
60 | HaiCo | 01:43.120 | 01:43.120 | 09.598 | 01:43.120 | 00.000 | ||
61 | Richard Aconley | 01:43.217 | 01:43.217 | 09.695 | 01:43.217 | 00.000 | ||
62 | Michael Mantl | 01:43.585 | 01:43.585 | 10.063 | 01:43.585 | 00.000 | ||
63 | Karlo Babić | 01:43.640 | 01:43.640 | 10.118 | 01:43.640 | 00.000 | ||
64 | Viking Rap | 01:43.775 | 01:43.775 | 10.253 | 01:43.775 | 00.000 | ||
65 | Mike Willis | 01:43.857 | 01:43.857 | 10.335 | 01:43.857 | 00.000 | ||
66 | Andres Ann | 01:44.470 | 01:44.470 | 10.948 | 01:44.470 | 00.000 | ||
67 | Knobi | 01:44.850 | 01:44.850 | 11.328 | 01:44.850 | 00.000 | ||
68 | Co Eijpe | 01:46.865 | 01:46.865 | 13.343 | 01:46.865 | 00.000 |
Race length: | 90 minutes |
Mandatory pit-stop(s): | 1 |
Mandatory tire change: | No |
Mandatory refueling: | No |
Refueling allowed: | Yes |
100% dry |
0% wet |
0% changing conditions |
Session info Oulton Park
● Race - 18:30 UTC (19:30 BST 20:30 CEST)
Practice Races Oulton Park Fastest practice times
27.08.2023 18:30 UTC | Results |
Race length: | 90 minutes |
Mandatory pit-stop(s): | 1 |
Mandatory tire change: | No |
Mandatory refueling: | No |
Refueling allowed: | Yes |
53% dry |
11% wet |
36% changing conditions |
Session info Suzuka
● Race - 18:30 UTC (19:30 BST 20:30 CEST)
Practice Races Suzuka Fastest practice times
Race length: | 90 minutes |
Mandatory pit-stop(s): | 1 |
Mandatory tire change: | No |
Mandatory refueling: | No |
Refueling allowed: | Yes |
78% dry |
4% wet |
18% changing conditions |
Session info Monza
● Race - 18:30 UTC (19:30 BST 20:30 CEST)
Practice Races Monza Fastest practice times
Race length: | 90 minutes |
Mandatory pit-stop(s): | 1 |
Mandatory tire change: | No |
Mandatory refueling: | No |
Refueling allowed: | Yes |
61% dry |
2% wet |
36% changing conditions |
Session info Bathurst Mount Panorama
● Race - 18:30 UTC (19:30 BST 20:30 CEST)
Practice Races Bathurst Mount Panorama Fastest practice times
17.09.2023 18:30 UTC | Results |
- 1.1 Driver placements
-
Drivers will be placed in a tier, with a maximum of 50 drivers per tier.
In case there is clearly enough interest to make a second tier, the tiers will be decided upon on the hotlap times for race 1, while coordinators reserve the right to make changes to tier placements.In case there are more than 50 drivers who want to participate, but not enough interest to open a second tier, the last sign-ups will be put as reserves. In case you have a historically poor attendance, coordinators reserve the right to put you as a reserve too.
In case of multiple tiers, all drivers will be placed in a suitable tier based on various factors; the hotlap event held as part of the sign-up process and to some extent performances in the previous league seasons (for drivers who raced in previous seasons).
Finishing in the top half of the hotlaps would therefore not guarantee being placed in tier 1.
-
- 1.2 Joining mid season
-
If there is a possibility to do so after the first race, new and returning drivers will be able to sign up while the season is ongoing. They will still have to complete the steps on the sign-up website (sign up, hotlap). Then there are two possibilities:
1. There is space (in the tier closest to the driver's race pace). The driver will be placed in the tier.
2. There is no space in the tier. The driver will be put on the waiting/reserve list for their respective car class. A coordinator will contact you once there is space (again).
-
- 1.3 Mid season moving
-
In case of multiple tiers, drivers may be moved between tiers while the season is ongoing if it's clear they have been misplaced. This could be that they are clearly too fast or that they are unable to experience close racing due to being too slow.
Preferably we want to avoid having to move drivers between leagues against their will, but in extreme situations this can be a necessity to keep the leagues competitive or sufficiently filled up. The league coordinators reserve the right to move drivers up to a higher (or lower) tier, if this is deemed to be in the best interest of a tier, to avoid drivers from excessively dominating.
-
- 1.4 Changing cars
-
After signups close, drivers are allowed to change the car they drive within the same class, but they may only do so just once during the season. In this season, you cannot change from GT3 to GT4 or the other way around.
You are not allowed to change cars from 22:00 UTC the day before the race because of the grid order work coordinators have to do.
If you wish to change cars, write an ACC coordinator.
Changing car automatically means your championship points will be reset to zero.
You will start at the back of the grid.
After the second race your car choice cannot be changed anymore.
-
- 1.5 Teams
You can join a team with your fellow drivers, with a minimum of 1 and a maximum of 3 drivers. It is not required, but driving in a team is mostly to have people work together and push each other forward in a fun way.
This also does mean that the standings will give a crooked view as teams of 3 will score more points than teams of 1. For as much as it matters, your total number of points will be manually divided by the number of drivers in your team in the end result after the season.GT3 and GT4 drivers are not allowed to team up. Coordinators can and likely will remove GT3 + GT4 combinations if such teams are created.
The car you choose within your class does not matter for the team. You can drive a different GT3 or GT4 car as your teammate, but still team up.
- 2.1 Points system
-
The following points will be scored for each race finishing position, per class.
1st = 50 points
2nd = 43 points
3rd = 38 points
4th = 34 points
5th = 30 points
6th = 27 points
7th = 24 points
8th = 21 points
9th = 18 points
10th = 16 points
11th = 14 points
12th = 12 points
13th = 10 points
14th = 8 points
15th = 6 points
16th = 5 points
17th = 4 points
18th = 3 points
19th = 2 points
20th = 1 point
-
- 2.2 Starting grid
-
The starting grid for race 1 is decided by the fastest lap on the qualifying server (ApexOnline.Racing #95 | ACC Vintage Multiclass - Quali Hotlaps).
GT3 will always start in front of GT4.
If your qualifying lap is set in a different car than you will race in, you will start at the back of the grid.
The order of the starting grid from race 2 onwards is decided as follows:
GT3 always in front of GT4.
1. The drivers who have finished the previous race will be put on the grid spots in reversed order from their position on the overall standings.*
2. In case of an even amount of points, the best result (see under 2.6) puts the driver with best result ahead on the grid. In case this is even as well, the first signup gets the spot ahead.
3. The drivers who have not finished the previous race will start behind those that finished in reversed order of the standings.
4. The drivers who have not finished any races will start behind the drivers mentioned under 3, with the first sign up getting the spot ahead.
5. The drivers who have not raced earlier will start behind the drivers mentioned under 4, with the first sign up getting the spot ahead.*Race points reductions (RP penalties) from inquiries do not improve your track position for the next race, meaning the order for the reverse starting grid is being counted without any RP penalties from the last race.
-
- 2.3 DNF
-
Drivers who complete less than 70% of the race distance will be classified as DNF (Did Not Finish) in the race results and will score 0 points regardless of their final position.
You will start at the back of the field for the next (reverse grid) race regardless of your standings position.
-
- 2.4 DSQ
-
Drivers who get disqualified from a race - whether that be due to an in-game penalty or post-race disqualification via the stewards panel - will be classified as a DSQ (Disqualified) and moved below all other drivers in the results. A DSQ due to an in-game penalty can be appealed via the stewards panel.
If a driver is classified as DSQ within a points scoring position, they will score 0 points for that position regardless of race distance completed.
-
- 2.5 CNS, NS, DNS
-
Registered drivers who did not attend the race will be classified as CNS (Confirmed No Show), NS (No Show) or DNS (Did Not Start), and will not score any points.
-
- 2.6 Championship standings
-
Drivers and teams are ranked in the standings based on how many points they've scored over the course of the season. If two or more drivers or teams are tied on points, the higher place in the standings will be awarded the holder of most first places. If the number of first places is the same, the holder of most second places, then third places and so on until a winner emerges.
At the end of the season, results of all races count.
-
- 3.1 Disconnections
-
ACC has the ability to let you rejoin the session at any time. We encourage to rejoin the session so that you still score points for the championship.
In this specific multiclass league, it also has the advantage of not having to start at the back of the GT3 or GT4 grid.
-
- 3.2 Mass disconnection
-
During the race, if half (or more) of the drivers in a race lose connection at the same time, or over a short period of time, that counts as a mass disconnection.
- If less than 50% of the race was completed at the time of the mass disconnection, the race will be restarted as soon as possible.
- If more than 50% of the race was completed at the time of the mass disconnection, the race will end, and the race will be postponed.
-
- 3.3 Canceling a race
-
Unfortunately, sometimes the technology that allows us to go racing, turns against us. This means we may have to cancel a race. If we do so, it's because we feel it's the fairest option for everyone, as having the very few people that can race have a massive advantage is very unfair to those that cannot.
Reasons we may cancel a race include:
- Lobby/Connection issues: If drivers are continuously getting dropped and there is no way of getting or keeping everyone in the lobby, then we may cancel the race rather than having a very small grid.
- Mass Disconnection: See above.
-
For league related enquiries or questions, your first point of contact
should be a staff member within the tier you are assigned to. Upon
joining a league, it will be made clear who your tier's coordinators
are.
Example reasons to contact them could be:
● To get information about your tier
● To ask questions related to the league
● If you are unhappy about something, either with regards to a race or something on the forums
If you have an issue with your coordinator and would rather discuss the
issue with someone else, then seek out another person from the below
list and address the issue to them. Our coordinators and moderators are
expected to remain completely unbiased, and as long as you address the
situation sensibly and maturely they will be happy to discuss any issues
no matter who it is with.
League Organisers
@Jaycoool
@NynS
- 1.1 Clean racing
- 1.1.1Race cleanly at all times. No contact should occur between cars on track, and as a driver you are required to do your best to avoid this from happening. Accidents can happen, but if you are at fault for causing a collision, you are likely to be penalised.
- 1.1.2Deliberately crashing into another car will result in being permanently excluded from our ACC leagues and events.
- 1.1.3If lag (connection issues) is the cause of an incident, when it is obvious that your car's lag is the cause of another driver going off, this would still be classed as an unfair overtake. Please be more careful around other drivers if you are regularly involved in lag-related incidents.
- 1.2 Overtaking
- 1.2.1Don't be too aggressive when trying to overtake. As the chasing car, it is generally your responsibility to not make contact with the car in front.
- 1.2.2Overtaking another car on the track, when under yellow flags, is prohibited/not allowed. An exception to this rule is in place, when the other car drives very slow due to damage and/or was involved in the incident causing the yellow flags. When a driver overtakes another car under yellow flags, they are supposed to return the position. This rule only applies during race sessions.
- 1.3 Defending
- 1.3.1Dangerous weaving and blocking is not allowed. Do not force a chasing car off the track or into a situation where they are forced to go off the throttle or on the brakes. If the attacking car is alongside you going into a corner (generally if the attacking car's front wheels is alongside or ahead of the defending car's rear wheels), you must adjust your line to avoid contact.
- 1.3.2Do not leave it too late to defend a move. Make your move clearly and fairly. If you move too late and the car behind has no time to react, it is not them who will be blamed.
- 1.4 Corner cutting/track extending
- 1.4.1Stay within the track boundaries with at least two tyres at all times. The track boundaries are defined in-game. Cutting corners, or extending the track, to gain an advantage is not allowed. Drivers found to be persistently breaking this rule will be penalised retrospectively.
- 1.4.2If you overtake another driver with all four wheels off track, or as a consequence of cutting a corner, you must slow down and give the position back. Failing to do so will likely result in a penalty.
- 1.4.3The odd misjudgement of a corner can happen, but if you accidentally gain an advantage by going outside the track limits without getting a warning by the game, you are expected to back off to an extent that clearly negates any advantage gained. Failing to do so may result in an enquiry being opened for the stewards to review.
- 1.4.4If a driver is reported to the stewards for a breach of this rule, it is up to the stewards' discretion as to whether they feel the driver has abused the track limits to an extent where a penalty is justified, and if so what type of penalty is appropriate to be handed out. This will depend on the severity and frequency of the cuts. The bottom line is, if you want to make sure you are not in danger of being awarded a stewards penalty, make sure you don't gain time from leaving the track limits throughout qualifying and the race.
- 1.5 Qualifying Etiquette
- 1.5.1In qualifying, it is your own responsibility to find free space on the track when starting a hot lap. A car on a hot lap does not have to yield for a faster car approaching from behind. If you are on an in- or out-lap, however, you have to let faster cars pass you without blocking them. If you are on a fast lap approaching a slow car, flashing your lights is a way of notifying them that you're on a fast lap.
- 1.5.2
Some races/events will feature qualifying sessions ran on a separate server for a week before the race actually begins. Those will be timed-average sessions, in which all of the drivers in the team/squad are required to complete a fast lap on. They will also be used to place your team/squad in a tier in case the race will be separated.
- 1.5.3
In the case of superpole qualifying sessions, aka “Pole Shootouts”, the selected driver representing the squad will be required to follow the instructions made by the coordinators conducting the session through the in-game chat. Cars will be let out in reverse grid order and will be spaced out so that they won’t meet each other on the track.
- 1.6 Spatial Awareness
- 1.6.1If you spin off whilst the pack is close, rejoining the track immediately is ill-advised. You do not ghost and you will cause accidents. Staying still is the best option until the other cars have avoided you. It is far easier to avoid a stationary obstacle. If you spin off whilst one or more competitors are close, you have to prioritize safety over minimal time loss, which might include braking until the control of the car is regained. Failing to do so may result in a penalty.
- 1.6.2If you for whatever reason leave the track, rejoin in a manner that is predictable, safe and in no way a danger to other competitors. Realign your car with the direction of the track as much as possible before rejoining the track.
- 1.6.3Using the in-game spotter, an external app like the crew chief or at least having the proximity arrows enabled is strongly advised. This helps the drivers to be aware of their surroundings.
- 1.6.4In case of yellow flags and/or an incident happening in front of you, you have the obligation to slow down by going off-throttle if the situation is safe enough or by braking to avoid any collisions. Failing to do so may result in a penalty even if you're not responsible for the incident in front of you. This rule only applies during race sessions.
- 1.7 Pit exit and pit entry
- 1.7.1Cars on a qualifying hot lap have the right of way, cars that reset to the pit during qualifying must let the hot lap cars through before entering the track. During the race, cars exiting the pits have the right of way and must be allowed to exit back onto the track. During the race, do not cut off the pit exit when a car is leaving the pit lane.
- 1.7.2Every track has a pit entry and a pit exit lane designated by a solid white line. If there is a car within these boundaries, either entering or exiting the pits, passing cars are not to cross the lines and move out of the way of the car entering or exiting the pit lane. This is especially important on tracks whose pit exits intersect with the racing line - Paul Ricard and Spa, as an example. Should any incidents occur while a car is in the pit entry or pit exit line, the passing car will be held responsible.
- 1.7.3A car is considered to be in the pit exit or entry zone when all four wheels are within the white lines.
- 1.7.4Once the car has left the pit exit boundaries, it is no longer under "protection", and as such is considered to have rejoined the race. Any incidents that will happen beyond the pit exit line will be no longer considered in favour of the car leaving the pits.
- 1.7.5Use of turn indicators is strongly encouraged to signal entering the pit, especially on tracks which have a very tight pit lane entry starting right after the final corner of the track (Paul Ricard, Monza, Suzuka, Zolder are examples of this).
- 2.1 Being lapped
- 2.1.1We are running with the in-game rules & flags system, which means that the game should alert you with a blue flag when you are about to be lapped. When receiving a blue flag or know that a car is going to lap you and is approaching from behind, you should prepare to let them pass, without interfering with their race, when safe, within the next few corners. In single class races, this is done best by the car that is being shown a blue flag moving off the racing line and easing on the accelerator on a straight, or lifting / braking early, and/or giving up the inside line to a corner to let the lapping car pass. The exception to this rule applies when the car being lapped has completed their mandatory pit stop, and the car approaching to lap them has not yet completed their stop. In this, and only this, situation the car being shown the blue flag has no requirement to move out of the lapping cars way, and may stick to the racing line until the lapping car attempts a pass. However when the lapping car goes for a move, the blue flagged car should not defend in any way. This means that you're not allowed to brake later than the lapping car.
- 2.1.2As a means of helping with blue flags, we advise the leaders to flash their lights at cars due to be lapped. This should not be done excessively. This is their cue to inform that the driver on the lead lap is about to go for a move on the driver being lapped. Flashing your lights at a competitor you are racing for position is not to be used as a "distraction technique" or in anger at an incident.
- 2.1.3If you are faster than a car that has lapped you already, you are allowed to try and unlap yourself. Immediately after unlapping yourself, you are allowed to try to build a gap to the car behind giving you blue flags. If you don't manage to do so within one lap, and are still receiving blue flags, you must adhere to them as per rule 2.1.1.
- 2.2 Multiclass rules
- 2.2.1
If a faster car class meets a slower car class, the slower car class has the right to stay on the racing line. The slower car class is not allowed to defend against the faster car class. As the slower car class, it is recommended to use your indicator to indicate on which side you are going or staying, especially if you move off the racing line.
- 2.2.2
The faster car is generally responsible for safely passing the slower car. It can be that a bit of time is lost behind the slower car in a section of the track that passing is hard on. You are not allowed to use your car as a plough to force your way through.
- 2.3 Pit stops
- 2.3.1Stay within the white line and obey the speed limit when entering and exiting the pit lane. If you cause a dangerous situation by crossing the pit entrance or exit line, or if this is done in a way that blatantly gains time or track position, you will be penalised. Remember to assign your pit limiter button as well. The speed limit line is enforced by ACC.
- 2.3.2A pit stop with tire change is mandatory in every 60 minutes race, refueling will not be allowed. Every driver will have the ability to make their own choice on when to pit similar to the in-game Competition Races. A pit stop is mandatory in every 90 minutes race, but changing tires and/or adding fuel are not requirements.
- 2.3.3A pit stop must be served after the official widget start and earliest at the end of lap 1. A pit stop must also be served before the final lap of a race. This takes into account the potential for having been lapped. Failing to observe this rule will cause a race DSQ.
- 2.4 Driving in different conditions
- 2.4.1For races that take place at night time, all drivers are required to have their headlights on in order to make your car visible to others, and to make the road more visible for you. If you're involved in an accident which damages both of your headlights, you must return to the pits immediately for repairs. Please also make sure you have a button assigned to turn the headlights on.
- 2.4.2The above rule about having headlights on also applies to running in the fog and in the rain.
- 2.4.3During rainy conditions, having the rain lights turned on is mandatory.
- 2.4.4For races with rain or a chance of rain, please make sure you have a button assigned to turn the wipers on, or have the auto-wipers feature turned on.
- 2.5 Return to pit box
If at any point in qualifying you want to return to the pit box, please do this off-track or manually drive to the pits safely.
If your car is so damaged that it is too dangerous to drive to the pit box, it is very much recommended to return to garage. If your car is totalled on the start of the lap often you lose less time directly returning to garage, and you are not a danger to passing cars.
- 2.6 In-Game Disqualification
- If you are disqualified from the race in-game and you feel it's unfair, submit your full race replay to the stewards. If we feel that the disqualification was justified, it will remain. However if we feel that the disqualification was unfair, or a result of a game glitch, then you will be classified as the last finisher and score full points for that position. In case you get disqualified when coming across the finish-line, you can be put back to your original finishing position.
- 2.7 Formation lap/start
- Drivers are at all times supposed to strictly follow the instructions given by the in-game widget. Drive through penalties awarded by the game will not be reverted. An exception to this is during live-stewarding. There the drive through penalties will first be removed, then reviewed and possibly reinstated. Long formation lap is being used in our league races.
- 2.8 Restarts
- 2.8.1In case of a major incident involving a massive number of cars in the first lap of the race, or general problems with the servers, the coordinator(s) of the tier are allowed to announce a session restart at their own discretion. The decision made by the coordinator should not be discussed during the race, if you feel like the restart wasn't needed then please contact your coordinator after the race. Only one restart will be done per race week.
- 2.8.2Any incidents happening before the restart, are still reportable and will be reviewed by the stewards.
- 3.1 Communication
- 3.1.1For the PC leagues, usually a driver briefing will be done by the coordinators in the AOR Discord channels before races. A driver briefing can be done through voice chat in Discord, or through the in-game chat. This depends on what the coordinator prefers and the coordinator will announce it before the start of the season.
- 3.1.2During the driver briefings, it is not allowed for the drivers to use the in-game chat or talk in Discord. Not being up to date due to not attending a briefing or reading the chat, cannot be used as an excuse.
- 3.1.3Once qualifying has started, drivers are expected to no longer use the in-game chat function until the race has ended (for all drivers). Not obeying this rule may result in a penalty. It is advised to have the in-game chat pop-ups enabled, so messages written by the coordinators are being read. PC leagues have access to the Discord server, which acts as one of the official communication platforms in AOR.
- 3.1.4
Spotters are only allowed to use the spectator password when live-stewarding is involved in a race. Spotters are not allowed to use the in-game chat at all. Abuse of this will result in spotters no longer being allowed as spectators for the remainder of the season. This will be monitored by the coordinators.
- 3.2 Lobby etiquette
- 3.2.1Shouting, name-calling and generally speaking rudely is not acceptable. Drivers who are a disruptive influence on the lobby atmosphere will be penalised accordingly, or in extreme cases removed from the league.
- 3.2.2Respect the other drivers. Keep a friendly atmosphere in the race lobby and treat your fellow drivers as equals, regardless of them being quicker or slower than you.
- 3.2.3
Respect the coordinators and stewards.
Listen to the coordinators if they are giving a message, and accept the decisions they make. If you feel any actions/decisions are wrong, address the issue calmly and maturely. Coordinators' decisions are final within the lobby, but may be reviewed later if you feel an error has been made. Please accept that making a call instantly can be tricky and the coordinators, even if participating in the race, are expected to be entirely neutral.
Don't be disrespectful towards the stewards or publicly make fun of them. Being disappointed about a decision made by the stewards is understandable, but there is no need to be disrespectful.
- 3.3 Race etiquette
- 3.3.1If you are involved in an on-track incident, don't overreact. It may be frustrating, but you need to stay calm and get on with it. Losing out due to another driver's mistake or recklessness is no excuse for retaliation or acting against the rules.
- 3.3.2If another driver does something you feel is against the rules, report it to the Stewards Panel after the race rather than argue about it over the voice chat or in Discord post-race.
- 3.3.3If you are having a bad race, don't act foolishly. As a driver, you have to accept that some races will be better than others and you can't always have it your way. If you are unable to enjoy the racing due to not always being at the front, this is not the place for you - there are many drivers in the league, and someone will always have to be at the back.
- 3.3.4Wait until everyone has finished the session, both qualifying and race, to discuss the race either on Discord or using the in-game chat.
- 3.3.5The cool down lap is part of the race event and therefore the same rules are being applied. Crashing into each other is not allowed during the cool down lap or any other particular time during the race event.
- 3.3.6Penalties will be applied to drivers who knowingly take out brake marker boards and other signs that could be used as reference points.
- 3.4 Rage-quitting
- 3.4.1Deliberately quitting the race in any way - whether that is by quitting through the pause menu, getting yourself disqualified or deliberately crashing your car - is not allowed, unless you have a very good reason to do so. Accepted reasons for quitting could be that you are a danger to other drivers on track due to poor driving or connection issues. Quitting because you "couldn't be bothered" or due to being angry at something - rage-quitting, in other words - are not good reasons.
- 3.4.2Excuses such as 'poor driving' and 'connection issues' will be monitored. These are not a get-out of jail free cards if you can't be bothered. Poor driving is occasional, if perhaps life has been unkind and you haven't had as much time to practice. However, turning up each week having not practiced, and therefore not enjoying your racing because you're struggling will see you put under review. We don't expect every driver to complete a certain amount of practice each week, but we expect you to be able to control your car and be safe on track. Also the more practice you do, the more competitive you are.
- 3.4.3Connection issues can strike anybody, but drivers who are continually unable to race safely due to connection will be removed from the league - see Connection and Lag under Participation.
- 3.4.4Repeatedly quitting the race before it has finished, gives the coordinator team the freedom to remove you from the league. This may also mean that you will not be accepted in the league for the next season.
- 3.5 Discord
- 3.5.1You will need to be on the AOR Discord server while being a driver in our leagues. It is encouraged to get involved with the community in the chats on Discord. If staff members are trying to contact you for whatever reason, they are likely to message you on Discord.
- 3.5.2You are expected to behave in a respectful manner on the AOR Discord, like in the race lobbies. Please avoid name-calling, baiting and other behaviour that is intended to aggravate other members of the community.
- 4.1 Completing races
- To be eligible for being classified points after a race, you must have completed at least 70% of the race. The amount of laps the winner of the race drove, is considered to be 100%.
- 4.2 Missing races
- 4.2.1If you are unable to attend a race, you have to give sufficient notice for your absence before the race starts. As a main driver, you can sign out from a race through the apexonline.racing webpage. For every race there is an option to sign out from the race.
- 4.2.2When informing the coordinator of your absence, a proper reason must be given for why you can't attend. No-showing a race because you don't like the track, because you "can't be bothered", or other similar reasons are not accepted and you position in the league will be put under review immediately. If your social life/work/school is taking up more time than you anticipated then we may consider a reserve role for you. Ultimately we can also decide that it's best if you withdraw from the league completely. Drivers have accepted to regularly attend races as part of the sign-up process.
- 4.2.3As a main driver, you are supposed to sign out from a race at least 90 minutes before the race. This gives the coordinators enough time to contact reserve drivers who can then still practice as well.
- 4.2.4If you are absent without informing your league coordinator or signing out through the webpage at least twice, the coordinator of your tier can decide to remove you from the league. This may also result in you not being allowed to join the league the following season(s).
- 4.2.5The official starting time of a race will be stated in the race thread of every race. If everything goes according to plan, races start at this official starting time. In case of a race starting earlier or later than the official starting time, a coordinator will let all drivers of the tier know.
- 4.2.6Getting another driver to race in your name is completely prohibited and will result in serious punishment.
- 4.3 Connection & Lag
- It's an unfortunate aspect of online racing that having a stable connection can be critical to being able to race closely with other cars. While we understand that not everyone can have perfect connections, and that occasional lag can't be avoided, we reserve the right to ask a driver to step down from the league if their connection is causing too many issues for other drivers. Coordinators reserve the right to disqualify a driver during the race if their connection pose a serious danger to other cars on track.
- 4.4 Pulling out mid-season
- 4.4.1Commitment and good communications are very important on AOR. If you have to pull out of an ACC league while the season is ongoing, you must let a member of the ACC Coordinator team know. If you leave by simply not showing up for the races, without informing anyone, the coordinators reserve the right to remove you from the league and put your name on the blacklist, which means you might not be allowed to rejoin the leagues in the current and future seasons.
- 4.4.2It's impossible for us to stop anyone from leaving if they've made their mind up, but keep in mind when signing up that pulling out of the league without a proper reason while the season is ongoing will possibly see you placed on the blacklist. A proper reason would be something happening in your life that forces you to quit - something that you didn't expect when signing up - or that your equipment (hardware or lag issues) leave you unable to carry on. However, choosing to quit due to getting bored of the game, having a bad season or because something goes against you, is not a good reason. Remember, when signing up you commit yourself to racing for a full season, not only for a few races.
- 4.4.3If you find yourself in a situation where you're not enjoying your league because all other drivers are too quick or too slow compared to yourself, contact one of the AOR ACC coordinators rather than just giving up - and maybe we can find a solution. We may grant league swaps for drivers during the season if it's clear that they've been misplaced, given that this doesn't upset the balance between the leagues with regards to driver numbers.
- 4.4.4Note that the above rules only apply while the season is ongoing. We don't have a problem with drivers choosing to leave after a season has finished, for whatever reason.
- 5.1 Stewarding systems
- We have one system in place to enforce rules and penalize on-track wrongdoing. The Stewards Panel system will be in place during every official league race this season.
- 5.2 Saving Replays
- As a means of helping the stewards with their enquiries, all PC drivers are required to save their race replays and keep it stored for at least one week after the race has taken place. If possible, it's better if you can record your race so we can see a live view of your screen, although this is not required. PlayStation drivers are required to record their race and also save a replay at the end of the race, to make sure it covers their entire race.
In races with more than 75 minutes of replay, press (default key) M to save your replay half way.
- 5.3 Stewards Panel
- 5.3.1The Stewards Panel can be used to report incidents and other rule violations that occur in a race. A proper explanation and/or evidence of the incident must be provided in order for it to be investigated. This will then be looked into by the stewards and appropriate action will be taken.
- 5.3.2What you can make a stewards enquiry for:
• Racing incidents: If you feel another driver has caused an incident - eg. hitting your car, forcing you off the track, or generally driving too aggressively - you should report this to the stewards for investigation.
• Track limits: If you witness another driver persistently gaining time by abusing the track limits by either running wide or cutting corners, you should report this to the stewards for investigation.
• Dangerous driving: If a driver rejoins the track in an unsafe or dangerous manner, or drives in a way that is a danger to other cars, you should report it to the stewards.
You should report incidents that you are involved in. Reporting an incident that you heard about, or saw behind you for example, will not be accepted. This is to lower the risk of a "nit-picking" environment. Two drivers may collide, shake hands and speak no more of it. If someone goes and starts causing trouble for the sake of it, the enquiries will be closed if those involved in the incident prefer it to go no further. Members of the @ACC Coordinator group, may open steward enquiries on any driver. - 5.3.3Time limit for enquiries: Note that enquiries need to be submitted before Thursday 23:59 PM UK time for incidents you have been involved in. If any new rule violations come to light through videos released after this time, it is still possible to report this, but only if this violation is something that was not visible to the other driver(s) in the race at the time it happened.
- 5.3.4Uploading video evidence: Any video evidence submitted in a stewards enquiry must be uploaded to a video streaming site (such as YouTube and Streamable) before being embedded and/or linked to in the enquiry thread. Stewards should not have to download video files in order to watch your evidence.
The following elements, recorded from the race replay, are required in the video:
• Cockpit and Chase point of view of the driver submitting the enquiry, recorded at normal speed and with HUD activated
• Cockpit and Chase point of view of the driver who caused the incident, recorded at normal speed and with HUD activated
Any additional point of view can be added after the required elements. When the enquiry is related to ignoring blue flags, the cockpit point of views are not a requirement. If the video evidence is part of a longer video that also contains other parts of the race, a time stamp must be provided next to the video to guide the stewards to the relevant part of the video where the evidence can be found. Failing to do this may lead to the evidence being dismissed.
- 5.4 Race Penalties
- 5.4.1The stewards have a variety of penalties that may be applied to punish drivers who break our racing rules, depending on the severity of the violation. The available penalties received in the stewards panel are sorted below, in order of severity and will depend on the Stewards decision. Penalty points may or may not be added to the Drivers License - see further down for more details. (Note that penalties may be added together in the event of multiple violations in a race, which could result in total time penalties of a higher number than what is suggested below)
● 0-20 race results points reduction - Driving in a dangerous or unsporting manner.
● 0-20 race results points reduction - Causing a minor avoidable collision.
● 0-40 race results points reduction - Causing a moderate avoidable collision.
● 0-60 race results points reduction - Causing a significant avoidable collision.
● 0-80 race results points reduction - Causing a major avoidable collision.
The above means that the winner of a race could receive fewer points than the driver who finished in P2. This would mean that the winner of that race was to blame for causing a collision, while the P2 finisher had a clean race. - 5.4.2Modifiers to Race Penalties in the Stewards Panel:
• Returning the position after an avoidable collision may result in the points deduction being reduced. Stewards encourage giving the position back or an attempt at waiting.
• Causing an avoidable incident in the opening lap may result in an increase of result points deduction.
• If the consequences of a penalty are worse or not as bad as the contact itself, the points reduction may be higher/lower than the usual punishments mentioned in the overview above.
• Not slowing down when clearly witnessing an incident in front of you, may result in an increase of result points deduction.
- 5.5 Drivers License Penalties
- 5.5.1The Driver’s License points system is a way of keeping track of a driver's record of breaking the rules of clean racing, and to more severely punish repeat offenders. Driver’s License Points will not be influenced by external circumstances related to an incident, they will only be given for the severity of an incident. Driver License Points may or may not be applied alongside race penalties, as per the list below.
● 0 to 5 points - Driving in a dangerous or unsporting manner.
● 5 points - Causing a minor avoidable collision.
● 10 points - Causing a moderate avoidable collision.
● 15 points - Causing a significant avoidable collision.
● 20 points - Causing a major avoidable collision. - 5.5.2Modifiers to Driver’s License Penalties:
• +5 points - Causing an avoidable incident in the opening lap - 5.5.3
Clean Racing Award:
• -5 license points - Completing a race without any penalty.
• -10 license points - Completing consecutive races without any penalty.
Note: 0 is the minimum amount of license points a driver can have - 5.5.4
Driver’s License accumulations:
• Every licence point equals 1kg of ballast added to your car for the next race a driver participates in. The maximum amount is 30kg.
• If you accumulate 40 points, you will be awarded a Qualifying or a Race Ban (decided on by the coordinators) and your league status will be put under review.
• If you accumulate 25 or more points during one event, you will be awarded a Race Ban. - 5.5.5Driver’s License points will carry over to a new season
- 5.5.6Any penalties will be aimed at the person who has done wrong - we cannot compensate anyone else as a result of someone's actions. All penalties are discussed by the Stewards Panel (consisting of the members of the AOR ACC Team - Admins, Moderators and Coordinators - from all platforms) before being issued and the driver will always be informed of the outcome. The Stewards Panel is completely neutral and will not include anyone who may be affected by the incident in question with race results or championship points.
- 5.6 Reprimand system
- While the race penalties and penalty points systems are aimed at dealing with on-track issues, the reprimand system deals with issues that may occur off the track. If you receive 3 reprimands, you will be removed from the league. Receiving 3 reprimands would also see you placed on the blacklist, meaning you would not be allowed to return to the leagues in the future. You can receive a reprimand for the following:
● Deliberately crashing out of the session
● Showing abusive behavior towards another driver, either in the race lobby, discord or on the forum
● Intentionally hiding/removing evidence and/or footage to avoid receiving a penalty in an enquiry
Note that if we encounter situations where someone's behaviour gets completely out of hand and is extremely serious, a ban may be applied directly regardless of reprimands accumulated.
- 5.7 Blacklist
- The blacklist contains the names of drivers who have been removed from the leagues - either through accumulating 40 license points from the stewards panel, due to not attending races regularly - and drivers who have left the leagues during an ongoing season without a valid reason. Having your name applied to the blacklist generally means you will not be allowed to rejoin the leagues in the current and next season.
Porsche 718 Cayman GT4 (2019) | 15 | |
Mercedes AMG GT4 (2016) | 12 | |
BMW M6 GT3 (2017) | 11 | |
Lexus RC F GT3 (2016) | 11 | |
AMR V12 Vantage GT3 (2013) | 8 | |
Mercedes AMG GT3 (2015) | 6 | |
Aston Martin Vantage GT4 (2018) | 5 | |
Emil Frey Jaguar G3 (2012) | 4 | |
Maserati MC GT4 (2016) | 4 | |
McLaren 570S GT4 (2016) | 3 | |
Lamborghini Huracan GT3 (2015) | 3 | |
Audi R8 LMS (2015) | 3 | |
Ginetta G55 GT4 (2012) | 2 | |
Alpine A110 GT4 (2018) | 2 | |
Audi R8 LMS GT4 (2018) | 2 | |
Chevrolet Camaro GT4 (2017) | 1 | |
Honda NSX GT3 (2017) | 1 | |
Bentley Continental GT3 (2015) | 1 | |
McLaren 650S GT3 (2015) | 1 | |
BMW M4 GT4 (2018) | 1 | |
KTM X-Bow GT4 (2016) | 1 | |
Nissan GT R Nismo GT3 (2015) | 1 |
In-game name | Discord name | Social | Car | Number | |
---|---|---|---|---|---|
Joshua Hoffmann | @czakwes | Audi R8 LMS (2015) | 187 | ||
Jani Pintér | @sziauram46 | Lexus RC F GT3 (2016) | 12 | ||
Remi Papin | @fubarr | Ginetta G55 GT4 (2012) | 6 | ||
Nico Urbantat | uLR | @extasionicourbantat | Mercedes AMG GT3 (2015) | 95 | ||
Steffen Bley | uLR | @icarussteffen | Mercedes AMG GT3 (2015) | 610 | ||
Chad Hilton | @Chad3 | Mercedes AMG GT4 (2016) | 333 | ||
Marc Sutton | @vuurman | Mercedes AMG GT4 (2016) | 420 | ||
Paweł Zabagło | @.lordbafford | Maserati MC GT4 (2016) | 1 | ||
Kulakov Eugene | @no1else | Porsche 718 Cayman GT4 (2019) | 515 | ||
Rafael Braga Cortinhas | @curtas75 | Mercedes AMG GT4 (2016) | 75 | ||
malik mammad | @malikmammad | BMW M6 GT3 (2017) | 23 | ||
Angus Fender | @angusfender | BMW M6 GT3 (2017) | 9 | ||
arne korv | @skrotnisse2647 | BMW M6 GT3 (2017) | 77 | ||
Langley Plays | @langleyplays | Porsche 718 Cayman GT4 (2019) | 13 | ||
Declan Brogan | @decbrogan | BMW M6 GT3 (2017) | 67 | ||
Charles John | @ | Lamborghini Huracan GT3 (2015) | 69 | ||
DoR | @gaming_dor | Mercedes AMG GT4 (2016) | 917 | ||
Daniel Durette | @rogerthebeast | Porsche 718 Cayman GT4 (2019) | 30 | ||
silver fox | @silverfox7240 | Audi R8 LMS (2015) | 12 | ||
Thomas Jack | @tomppelii | Honda NSX GT3 (2017) | 13 | ||
Daniel Lopez | @FreeAcorn | Audi R8 LMS (2015) | 11 | ||
Marton Cynolter | @cs4sz4r | Nissan GT R Nismo GT3 (2015) | 451 | ||
Tobias Moberg | HeX | @tobiass9972 | Mercedes AMG GT3 (2015) | 777 | ||
Mike Willis | @mwillis28 | Aston Martin Vantage GT4 (2018) | 29 | ||
Leonardo Porco | @leonardo_porco | Alpine A110 GT4 (2018) | 288 | ||
Damir Makhmutov | @mak_racing | Mercedes AMG GT4 (2016) | 716 | ||
Knobi | @.knobi. | KTM X-Bow GT4 (2016) | 88 | ||
Stefano Zanobini | @stefanozanobini | BMW M6 GT3 (2017) | 82 | ||
Mateusz Nitsche | @mateonitsche | Aston Martin Vantage GT4 (2018) | 34 | ||
Luca Ziege | @kylo__ | Porsche 718 Cayman GT4 (2019) | 199 | ||
Cedric Holmbom | HeX | @cedric_holmboms | Porsche 718 Cayman GT4 (2019) | 99 | ||
Michael Mantl | @mantl_is_da | Mercedes AMG GT4 (2016) | 21 | ||
Viking Rap | @vikingrap | Porsche 718 Cayman GT4 (2019) | 25 | ||
Yorick Ten Brinke | @yorick.tk | Porsche 718 Cayman GT4 (2019) | 97 | ||
Anton van Someren | @blamant | Porsche 718 Cayman GT4 (2019) | 22 | ||
Calvin Leijdekkers | @wasdroger_ | Porsche 718 Cayman GT4 (2019) | 56 | ||
João Manso [RPMS] | @manso74 | BMW M6 GT3 (2017) | 222 | ||
Manuel Rutter | @saithron | Audi R8 LMS GT4 (2018) | 33 | ||
Jonas De Meyer | @fireape | AMR V12 Vantage GT3 (2013) | 777 | ||
Andres Ann | @andu1867 | BMW M4 GT4 (2018) | 32 | ||
John Nova | @j_nova | Lamborghini Huracan GT3 (2015) | 59 | ||
Eike Planer | @eike_gp555 | BMW M6 GT3 (2017) | 63 | ||
Catalin Iliescu | @captain_slow82 | Lexus RC F GT3 (2016) | 39 | ||
Co Eijpe | @thapt | McLaren 570S GT4 (2016) | 22 | ||
Vency Raychinov | @v.raychinov | Mercedes AMG GT4 (2016) | 24 | ||
Geoffrey Leemans | @geoffrey_lms | Mercedes AMG GT4 (2016) | 27 | ||
Hans Peter | @scfighter | Audi R8 LMS GT4 (2018) | 55 | ||
Krab Athor | @krabathor | Porsche 718 Cayman GT4 (2019) | 666 | ||
StevieB Beeswax Racing | @beswiche | Emil Frey Jaguar G3 (2012) | 833 | ||
Nojus Sabas | @ltukj | Lexus RC F GT3 (2016) | 72 | ||
Dan Barnard | @b4rn3y87 | Aston Martin Vantage GT4 (2018) | 187 | ||
Xander van Dijk | @nextaxander | AMR V12 Vantage GT3 (2013) | 207 | ||
Mert Sevinc | @mertsevinc | AMR V12 Vantage GT3 (2013) | 8 | ||
Chris Bradbury | @wacky_racer | Emil Frey Jaguar G3 (2012) | 111 | ||
Maurice Miller | @mauricemiller | BMW M6 GT3 (2017) | 58 | ||
Karlo Babić | @karlowo | Chevrolet Camaro GT4 (2017) | 24 | ||
Scott Ticehurst | @scottyio | Lexus RC F GT3 (2016) | 352 | ||
Ryan Rees | @trip.cb | BMW M6 GT3 (2017) | 420 | ||
Kristers Podēns | @jogurc | Ginetta G55 GT4 (2012) | 69 | ||
Maciej Chyrc | @maqs17 | Aston Martin Vantage GT4 (2018) | 17 | ||
JP Mc Kinley | @thekinky1 | Lexus RC F GT3 (2016) | 7 | ||
Jonathan Clifford | @jonathan_clifford | Lamborghini Huracan GT3 (2015) | 999 | ||
HaiCo | @haico77 | Maserati MC GT4 (2016) | 77 | ||
Charlotte Perkins | @charlotteperkins | Lexus RC F GT3 (2016) | 463 | ||
dakuza | @dakuza | Maserati MC GT4 (2016) | 80 | ||
Alastair Baldwin | @happyal | AMR V12 Vantage GT3 (2013) | 27 | ||
bolf ramshield | @bolf | Mercedes AMG GT3 (2015) | 51 | ||
Scott Ullmann | @bullittridauk | AMR V12 Vantage GT3 (2013) | 222 | ||
Jamie Sterritt | @spicyspice1 | BMW M6 GT3 (2017) | 271 | ||
Samuel Christiansen | @cuhlosamuelchristian | Lexus RC F GT3 (2016) | 227 | ||
Liam Dinning | @dinning | Alpine A110 GT4 (2018) | 919 | ||
Kalimazoo | @kalimazooracing | AMR V12 Vantage GT3 (2013) | 28 | ||
Alexa Gates | @amg35 | AMR V12 Vantage GT3 (2013) | 35 | ||
Ivan Borimechkov | @flexiefect | Mercedes AMG GT4 (2016) | 2 | ||
Pranav Kalavala | @pran_ | Emil Frey Jaguar G3 (2012) | 123 | ||
Simon Beeg | @simimuc | Mercedes AMG GT3 (2015) | 95 | ||
Penelope Dobbins | @pddobster | Emil Frey Jaguar G3 (2012) | 87 | ||
Tiago Cruz | @tiago_cruz | Mercedes AMG GT4 (2016) | 26 | ||
Thomas Allendorf | @mr.darktown | Lexus RC F GT3 (2016) | 16 | ||
Claudio Zazza | SKY | @zazza_._ | Porsche 718 Cayman GT4 (2019) | 712 | ||
Benjamin King | @.benjaminking | Porsche 718 Cayman GT4 (2019) | 18 | ||
Mikolaj Nowicki | @mikolajnowicki566 | Lexus RC F GT3 (2016) | 566 | ||
Richard Aconley | @richardaconley | McLaren 570S GT4 (2016) | 210 | ||
Stefan Monz | @psychoazubi | Porsche 718 Cayman GT4 (2019) | 33 | ||
Brian Anderson | @mr_ando_ | Porsche 718 Cayman GT4 (2019) | 707 | ||
Paul Martin | @saxondale76 | Bentley Continental GT3 (2015) | 76 | ||
Anna Foster | @.7734 | Lexus RC F GT3 (2016) | 734 | ||
Robin Moe | @robin_moe | McLaren 650S GT3 (2015) | 3 | ||
Nathaniel Shirley | @natnat4424 | Lexus RC F GT3 (2016) | 45 | ||
Jan Robohm | @matsudason | McLaren 570S GT4 (2016) | 166 | ||
Rytis Kazlauskas | @fuzkin | Mercedes AMG GT3 (2015) | 1 | ||
Javi Hernando | @warkki | Mercedes AMG GT4 (2016) | 47 | ||
Daniel Crinson | @thumbtwiddeler | BMW M6 GT3 (2017) | 909 | ||
Sam Mawdsley | @kero_the_hero | AMR V12 Vantage GT3 (2013) | 117 | ||
Kiki Mac | @kikimac | Maserati MC GT4 (2016) | 177 | ||
Manuel Düchs | @duce381 | Porsche 718 Cayman GT4 (2019) | 123 | ||
Jay Janz | @jaycoool | Mercedes AMG GT4 (2016) | 335 | ||
NynS | @nyns | Aston Martin Vantage GT4 (2018) | 20 |
Teams must consist of 1 - 3 drivers.
The deadline for creating a team is before race 2 of the season