Watkins Glen 7 hours - Multiclass
Apex Online Racing
- Signups open 07.08.2022
- Signups closure and squads locked 24.08.2022
- Qualifying server open: 07.08.2022 - 25.08.2022 23:59 BST
- Pre-race practice session: 27.08.2022 11:00 BST - 13:00 BST
- Race: 27.08.2022 13:00 BST - 7 hours
- Green flag: approx. 13:05 BST
- Signups open 07.08.2022
- In-game time of day/weather information:
- Qualifying conditions: SATURDAY 11:00 in-game time, 20 degrees ambient temperature, 25 degress track temperature with non-changing conditions ("isFixedConditionQualification": 1,) cloud level: 0.0.
- Race conditions: SUNDAY 14:00 in-game time, 27 degrees average ambient temperature, cloud level: 0.35, weather randomness: 3, rain level setting 0.2.
- Race day weather probabilities - according to testing:
- 24% dry
- 7% wet
- 69% mixed
- 24% dry
- Event-specific rules:
- Minimum of 2 drivers per team
- Maximum of 4 drivers per team
- No limitation on tire sets
- No mandatory pitstops
- No stint timer
- Refueling time not fixed
- Race server settings:
- Qualifying structure:
- Detached averaged qualifying - Team members set their fastest lap time on the designated qualifying server, the resulting grid position is decided on the average of the fastest lap times set by the teammates.
- Teams will be split into “Qualifying rankings”, depending on the amount of drivers of the team that have participated in the qualifying. As an example for a 4-man team:
- Qualifying ranking 1 - all team members have set a time
- Qualifying ranking 2 - one team member has not set a time
- Qualifying ranking 3 - two team members have not set a time
- Qualifying ranking 4 - no team member has set a time
- Teams in every tier will be divided in Pro and Silver class
- Custom skins:
- A custom skin pack will be created by the coordinating team. This will allow you to share your custom livery with the other drivers participating in the event.
- The skin pack submission form can be accessed HERE
- The skin submission deadline is 23.08.22 at 23:59 BST
- Here is an overview of the servers we have set up for the event:
- ApexOnline.Racing #27 | Watkins Glen 7H | Solo practice #1 | #AORERP
- ApexOnline.Racing #28 | Watkins Glen 7H | Solo practice #2 | #AORERP
- ApexOnline.Racing #29 | Watkins Glen 7H | Solo practice #3 (fixed conditions) | #AORERP
- ApexOnline.Racing #30 | Watkins Glen 7H | Solo practice (9x) | #AORERP
- ApexOnline.Racing #31 | Watkins Glen 7H | Solo practice (0.2 rain) | #AORERP
- ApexOnline.Racing #32 | Watkins Glen 7H | Solo practice (0.4 rain) | #AORERP
- ApexOnline.Racing #33 | Watkins Glen 7H | Solo practice (dark) | #AORERP
- ApexOnline.Racing #34 | Watkins Glen 7H | Team practice #1 | #AORERP
- ApexOnline.Racing #35 | Watkins Glen 7H | Team practice #2 (fixed conditions) | #AORERP
- ApexOnline.Racing #36 | Watkins Glen 7H | Qualifying server #1 | #AORERQ
- ApexOnline.Racing #37 | Watkins Glen 7H | Qualifying server #2 | #AORERQ
- ApexOnline.Racing #38 | Watkins Glen 7H | Qualifying server #3 | #AORERQ
- The password to enter every server is Apex.
- During the signups, the solo practice will never enforce the car number or the car model. Team practice servers and qualifying servers will always enforce car number, model and class.
- Details of the server for the race will be published a day before the actual race event on discord.
- The entry lists for each of the servers will be updated periodically, usually once a day.
- Your first point of contact should always be an event organizer. The organizers for this event are Tom#4284 and Cs4sz4r#0667 on discord.
- Squads are required to be present on the AOR Discord in order to participate in this event
- 1.1 Live Stewarding
Link to the page where you can create an enquiry: Enquiry form
- 1.1.2The event will feature live stewarding done by the AOR steward team.
- 1.1.3The process will be a bit different compared to the one used in the GT3 league, as the decision making has to be done fast. Neither of both teams will have the opportunity to give their personal opinion on the enquiries, therefore the team posting the enquiry will have to stay factual instead of explaining what - in their opinion - happened.
- 1.1.4Make sure that all members of your team have a functional recording solution ready before the start of the race.
- 1.1.5Instructions on which software to use to record incidents can be found in "how to record evidence"
- 1.2 How to report
- 1.2.1You have 30 minutes after the incident happened, to report it.
- 1.2.2To submit an enquiry, you have to first record and upload the evidence. Read the final few pages of this file to figure out how to record and upload the evidence. You can watch the replay of the race in the pause menu.
- 1.2.3The evidence of your steward enquiry must only show the chase cam and the onboard cam of all cars involved to ensure a seamless process for the stewards. You have to show what happen before the incident, the incident and after the incident (to show the stewards how many time has been lost). The Gear/Speed HUD must be activated to show the steward the input of the cars. (Example of valid evidence: YouTube link)
- 1.2.4If the evidence doesn’t contain only the chase cam and the onboard of all cars involved or the HUD, the enquiry will be refused.
- 1.2.5Afterwards, you need to complete the following Google Forms with the correct information (server number, number of the cars…)
- 1.2.6Once you have submitted the form, a steward will check if the enquiry if valid. If the enquiry is considered invalid, a message will appear in the “acc_race_control” discord chat stating that the enquiry is refused and why.
- 1.2.7The stewards will then debate and decide on a possible penalty for the enquiry. Once a decision has been made, it will be added to a queue of penalty.
- 1.2.8At regular intervals, the stewards will post a report on Discord including all the penalties of the enquiries judged. In this report will be listed the enquiries, the decision of these enquiries and the time of the next report.
Please note that every enquiry is either refused or closed. Enquiries are never lost, sending an enquiry more than once could end up in a penalty for your team.
Due to the length of the race and the possibility of a limited amount of stewards being available, it is possible a penalty is awarded later than you would normally expect.
- 1.4 What is penalized by the stewards
- 1.4.1Contact resulting in significant damage or a spin
- 1.4.2Push off the track
- 1.4.3Massive divebomb
- 1.4.4Unsafe rejoin
- 1.5 What won’t be looked at by the stewards
- 1.5.1Any Drive Through or Stop & Go penalties given by the game
- 1.6 Any imitation of the stewards and/or coordinators in the in-game chat will result in an instant kick of the responsible car.
- 2.1 Windows 10’s Game Bar
To use the Windows 10’s Game Bar it must be activated in the settings of your computer, in the Gaming section.
Then you can open it by pressing Windows+G and you can start the record by using the button on the top left.
Once your evidence is recorded, you can see it on the folder "Videos/Captures" of your computer.
As the result file is relatively big (~50MB for 30s) this method is preferred if you have a strong connection.
- 2.2 NVIDIA ShadowPlay
This method is to be used if you have a really strong connection, 30 seconds of video will result in a ~180MB file in higher quality, ~60MB in lower quality (prefer OBS if you need to reduce the file size).
To use NVIDIA ShadowPlay, you need to have Geforce Experience installed.(https://www.nvidia.com/fr-fr/geforce/geforce-experience/shadowplay/#download)
Then once in game you can press ALT+F9 to start/stop the recording, the resulting file will be available in "Videos/Assetto Corsa Competizione".
- 2.3 AMD ReLive
As we don’t have AMD material to test this method, we can’t say the size of the files but it is to be expected as the same size as NVIDIA ShadowPlay as the solution are similar.
To use this method, you need to use the latest AMD Software (https://www.amd.com/en/support).
You need to activate ReLive on the AMD Software.
Then, once in game, you can use CTRL+SHIFT+R to start/stop the recording, the resulting file will be in the folder "Videos/Radeon ReLive"
- 2.4 OBS
This method requires more configuration but it will result in the lighter video files (2.5MB for 30s) making it better if you have a slow connection.
Start by downloading the latest version of OBS on their website https://obsproject.com/.
Once the software is installed and started, you need to add a display source. This solution is not optimal on the performance but it is not the focus of this guide, the goal is to make it simple.
Validate the two windows, make sure it is setup to your correct screen. Then open the settings and go to “Output” and define the “Video Bitrate” on 1000kbps.
Then in the “Video” section, edit “Output (Scaled) Resolution to "852x480" and "Common FPS Values" to "24 NTSC".
Then you can use the “Start Recording” and “Stop Recording” button to record your evidence. The resulting file will be available in the “Videos” folder of your computer.
- 3.1 Streamable
This one doesn’t require an account. Go to https://streamable.com/ then select "Upload a video file". Choose the video file on your computer then copy the link and paste it in the form.
- 3.2 Youtube
Using Youtube require a Google account. Go to https://www.youtube.com then click on upload button.
Select the video file on your computer.
Then select "No, it’s not made for kids" and copy the link in your clipboard.
Click Next two times then select "Unlisted" then "Save".
You can then paste the Youtube link in the form.
- 4.1 How do I swap drivers?
There is an extensive tutorial on both the official ACC forums and the previous endurance race threads. You have to do it using the MFD - cycle to the pit menu, then you have to move the cursor using your up and down buttons and then you can select different drivers using left and right. Don't have to "confirm" anything, just leave it on the name of the driver you want to switch seats with and pit. After the pit is done he'll get teleported into the car.
- 4.2 I joined the server as a spectating driver and I’m focused on another team’s car
Click “Drive” and find your car using the Shift+L/R arrow key. Once this is done, pressing "Drive" at any time in continuation will focus your camera on the correct car. Make sure you check that the "Drive" mode is focusing on the correct car before taking over the car. If the player is still focused on a different entry after receiving the car during a swap, pressing Shift+Up Arrow will focus the view to the player car instantly. Note that this requires the possession of the car. While spectating, only the Shift+Left/Right Arrows will cycle the focus as described above.
- 4.3 Who out of my squad should join the server first?
The driver designated to join the server first is marked as "First Driver" on the Teams tab. The first-joining driver will define the in-game car name and the livery. In the event of a disconnection and loss of car, the original join order must be respected to retain the car’s progress (see next question).
- 4.4 The active driver disconnected from the server, what can we do in order to keep racing?
Depending on the squad’s ability to perform the correct rejoin sequence, disconnecting is likely to result in a DNF. However, the squad might be able to reconnect and regain control over the original car. When a car is lost, make sure all drivers of the squad first leave the server. After that, it must be the driver of the entry who was originally the first one to join the server that reconnects first, followed by the other teammates. The success of the rejoin will be indicated by the fact that the Driver Swap widget is visible on the HUD with the teammates correctly indicated and the timing widget showing the car’s progress from before the disconnection. If the driver who originally joined the server first from the squad is unable to reconnect and regain the car, the original entry unfortunately remains lost and the remaining drivers will not be able to continue the race in the same entry.
- 4.5 Our squad joined the server but we don’t see each other online in the Driver Swap widget (usually also manifested in an incremented race number when joining)
This is a sign of desynced entry information that occurs due to wrong connecting order. (See 4.4)
- 4.6 I experienced a game crash or disconnection after giving the car away, is this affecting the squad?
If the driver swap is completed successfully, any issue a spectating driver might experience is irrelevant to the connection status of the entry and the player should be able to reconnect to spectate.
- 4.7 One of my mates isn't going to turn up to the race, what now?
You have to remove him from your squad, otherwise your team will get disqualified if one of the drivers doesn't enter the car at all before the end of the race. You are also adviced to message a coordinator. More information can be found unter "Rules" 3.5.2.
- 4.8 Can I solo the race?
No. We no longer accept drivers to drive endurance events solo.
- 4.9 What is the password?
Password for all servers = Apex
- 4.10 What does "Maximum stint time of X minutes" mean?
You have to pit before the X minutes run out. You don't have to necessarily change the drivers or even complete the service - the stint timer is frozen when entering the lane and gets reset every time the car drives through it, apart from when serving a penalty. This also means that if it’s strategically feasible for your squad, you can extend the stint if you still have enough fuel in the tank.The timer should be visible on the top left of your HUD. The car's Racelogic display can also be cycled to show the current stint time on the dashboard.
- 4.11 (if applicable) Why is there a maximum stint time imposed in the first place?
Two reasons: The first one is that the real world series has the same rule as well, and the second one is that it balances out the more fuel efficient cars with the ones that have a drinking problem.
- 4.12 (if applicable) Why is the refuelling time fixed, and what does it mean?
It essentially means that every full-service stop will take 30 seconds (excluding repair time) because all the servicing and driver swapping is done simultaneously, regardless of how big your fuel tank is. In case the event does not have the refuelling time fixed, the time it takes to refill your car depends on the amount you want to put in. Refuelling in GT World Challenge is done simultaneously with the tire and driver changes and takes much less to complete than the other two tasks, so if you opt for a full stop, the pit will take 30 seconds anyway - so this only matters if you only want to fill up your car without changing the drivers or the tires.
- 4.13 Further Information
For more detailed issues or questions related to the game, please contact the event organizers. For further information on team racing in ACC, take a look at Kunos Team Racing Guide: TEAM RACING AND DRIVER SWAP GUIDE for ACC
- 5.1 Virtual mirror disappears after entering the car
Cycle through the views using the F1 button on your keyboard
- 5.2 After swapping drivers the camera ends up in a different car
Hold SHIFT and press left/right arrow keys to cycle views between the cars to cycle back to your vehicle
- 5.3 The HUD stint timer shows exaggerated/negative values
The bug is only visual, the in-game crew chief will alert you 10 and 5 minutes before your stint ends. The in-car Racelogic display also works properly regardless
- 5.4 My game crashes when I press setup while one of my teammates is driving
The only solution for now is: don’t press that button when you’re not the one controlling the car
- 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. Teammates of someone deliberately crashing into another car, will be disqualified from the race but can participate again the following race.
- 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 an other 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.1Excessive weaving and blocking is not allowed. As soon as a driver is in striking distance behind you, you are supposed to choose and stick to one line. When defending from another car, choose a line on the track and stick to it. Do not force a chasing car off the track by leaving it too little room. 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.2It is generally accepted that the attacker must be at least halfway alongside the defender when they reach the apex to have a reasonable claim to this piece of track.
- 1.3.3The defending driver is required to make their defending move early enough for the attacking driver to react accordingly. Making the move too late might result in a crash.
- 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 by the stewarding team.
- 1.4.2Penalties applied by the game for excessive corner cutting can range from a drive-through to a stop-and-go penalty. Your team is required to serve those penalties within 3 race laps, as defined by the game. These penalties are not protestable.
- 1.5 Qualifying etiquette
- 1.5.1In the case of regular qualifying sessions, it is your own responsibility to find some free space on the track when starting your outlap. 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. Excessive flashing is not allowed, however, and can result in a grid penalty applied before the race.
- 1.5.2Some 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.3In 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 Spacial Awareness
- 1.6.1You are only allowed to ignore the pit entry and pit exit line if you don't create a dangerous situation. This means that on the start/finish straight, you are allowed to cross the white pit lane lines (when not performing a pit stop), but you should make sure you don't endanger other drivers.
- 1.6.2If 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 a competitor is close, you have to brake and stay on the brake to avoid your car rolling randomly back onto or over the track. Failing to do so may result in a penalty.
- 1.6.3If your car is sent into a spin, hit the brakes in order to avoid your car from veering into an unpredictable course. During stewarding, failing to do so will be taken into account and can result in a more severe punishment.
- 1.6.4If you go off the track, rejoin in a manner that is both safe and in no way a danger to other competitors.
- 1.6.5Using the in-game spotter, an external app like the crew chief or at least having the proximity arrows and the radar enabled is strongly advised. This helps the drivers to be aware of their surroundings.
- 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.
- 2.1.2In 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 corner and racing line to let the lapping car pass. Blatantly refusing to let the car behind pass you, will most likely result in a penalty. Tight corners and chicanes are not considered safe places to let a car through. Also, you can see if the driver is a lap higher than you by looking at the relative board - the driver’s name will be highlighted by an orange colour, instead of a regular white name.
- 2.1.3As 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 pass the driver being lapped, and should let the lapping car pass at the next safe available opportunity.
- 2.1.4Flashing 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.5If you are faster than a car that lapped you, you are allowed to try and unlap yourself. But keep in mind the following rules too: At all times - if you are under blue flags - you are not allowed to defend. So if you don't get away from the same car, blue flags will mean that you are not allowed to defend (if the other car makes an attempt to lap you). Follow the regular rules of overtaking and don't go for a dive bomb on the inside.
- 2.2 Multiclass racing
- 2.2.1In the case of multiclass events, the driver of the faster car is always the one responsible for making a safe pass on the slower car.
- 2.2.2The driver of the slower class car is advised to use the turn indicators to indicate the direction in which he’s going to go in order to let the faster class car by.
- 2.2.3At all times, the slower class car is required to stick to one racing line and not change his direction erratically.
- 2.2.4Passes on slower cars don’t have to be done immediately, both parties involved are advised to pick the next straight or more relaxed section of the track as the overtaking area.
- 2.3 Pit stops
- 2.3.1Every 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.
- 2.3.2A car is considered to be in the pit exit or entry zone when all four wheels are within the white lines.
- 2.3.3Once 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.
- 2.3.4Use of turn indicators is once again 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).
- 2.3.5The pit stop strategy is open by default unless stated otherwise in the event thread. You can choose to change the tires, drivers and refill you car at your team’s discretion.
- 2.4 Inclement weather and night time racing
- 2.4.1Endurance races are expected to stretch longer time frames, often continuing into the night. As such, turning on your headlamps should the night fall is required and will also be policed by the game. If the driver continues to drive the car with headlamps turned off, the game will automatically issue a "meatball" (Black flag with an orange circle) penalty after 3 laps, disqualifying the car as unfit to race.
- 2.4.2If for whatever reason your headlamps are broken while in night time, the game will also automatically advise you to pit for repairs - should you fail to do so, you will be disqualified by the game on the same grounds as not having your headlamps on.
- 2.4.3It is encouraged to use a version of the car with additional endurance lighting to improve night time visibility.
- 2.4.4Should rain occur, the drivers are required to turn on both regular lighting and the rain light. If a driver is spotted driving without one, he will be first issued a warning before getting penalized.
- 2.5 Returning to the garage
- 2.5.1If at any point during qualifying you want to return to the garage, either drive your car completely off the track and use the “back to garage” option or drive into the pit lane first. The former option is strongly encouraged in case your car gets damaged to the point where it is no longer safe to drive it back while avoiding incoming traffic.
- 2.5.2Using the “back to garage” option in race sessions is only allowed in case your car is either impossible to drive or would be very hard to limp back to the pit lane in order to commence repairs. The game will automatically freeze your controls if you do so for a set period of time, serving as a penalty for using the aforementioned option.
- 2.6 In-Game Disqualification
In-game disqualifications can not be removed while the event is ongoing.
- 2.7 Widget formation lap/start
- 2.7.1Drivers are at all times supposed to strictly follow the instructions given by the in-game widget.
- 2.7.2Drive through penalties awarded by the game will not be reverted.
- 3.1 Communication
- 3.1.1All members of the squad are expected to be present on the AOR discord server and have the "ACC Racers" and "ACC Endurance Racer" roles claimed through the #game-assignment and #acc-assignment channels. Squads may be removed if there is no way to contact them through the AOR Discord or if members of the squad seemingly ignore organizers instructions or messages.
- 3.1.2Driver briefings will be held in form of a short post made by the event organizers before the respective race in the endurance_info channel of the AOR Discord. Not being up to date due to not bothering to read them cannot be used as an excuse.
- 3.1.3Once the race 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.
- 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 disqualified from the race.
- 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.3Respect the coordinators. Listen if he is giving a message, and accept the decisions he makes. 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 Coordinator, even if participating in the race, is expected to be entirely neutral.
- 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 through the live stewarding form rather than argue about it over the voice chat, game chat, discord or in the forums 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/event, 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.
- 3.4.3Connection issues can strike anybody, but drivers who are continually unable to race safely due to connection will be removed from the race - see Connection and Lag under Participation.
- 4.1 Completing races
To be eligible for being classified points after a race, your team/squad 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 your squad is unable to attend a race, you have to give sufficient notice for your absence before the signout deadline (Friday before the race at 23:59 British local time). You can sign your squad out from the race through the apexonline.racing webpage. For every race there is an option to sign out from the race.
- 4.2.2If you are absent without informing the race organizers or signing out through the webpage on-time, your team may not be allowed to join future endurance races.
- 4.2.3The official starting time of a race will be stated in the event info. 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, an event organizer will let all teams/squads know.
- 4.2.4Getting 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 leave the server if their connection is causing too many issues for other drivers. The organizers reserve the right to disqualify a team/squad during the race if their connection pose a serious danger to other cars on track.
- 5.1 Live stewarding
- 5.1.1This race will feature live stewarding done by the AOR steward team. For the first 3 laps of the race, all avoidable collisions will be reported by the stewards themselves. For the remainder of the race, teams/squads can report incidents to the stewards themselves, by using the provided form.
- 5.1.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.
What won’t be looked at by the stewards:
• Any Drive Through or Stop & Go penalties given by the game.
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.
Link to the page where you can create an enquiry: Enquiry form
- 5.1.4The process is a bit different when compared to the AOR GT3 league, as the decision making has to be done fast. Neither of both teams/squads will have the opportunity to give their personal opinion on the enquiries, therefore the team/squad posting the enquiry will have to stay factual instead of explaining what - in their opinion - happened.
- 5.1.5Make sure that all members of your squad have a functional recording solution ready before the start of the race. Instructions on which software to use to record incidents can be found in "how to record evidence".
- 5.2 How to report
- 5.2.1You have 30 minutes after the incident happened, to report it.
- 5.2.2To submit an enquiry, you have to first record and upload the evidence. Read the final few pages of this file to figure out how to record and upload the evidence. You can watch the replay of the race in the pause menu.
- 5.2.3The evidence of your steward enquiry must only show the chase cam and the onboard cam of all cars involved to ensure a seamless process for the stewards. You have to show what happened before the incident, the incident itself and what happened after the incident (to show the stewards how much time has been lost). The Gear/Speed and pedal input HUD must be activated to show the steward the inputs of the cars. (Example of valid evidence: YouTube link)
- 5.2.4If the evidence doesn’t contain only the chase cam and the onboard of all cars involved or the HUD, the enquiry will be refused.
- 5.2.5Afterwards, you need to fill out the provided Google Forms with the correct information (server number, number of the cars…).
- 5.2.6Once you have submitted the form, a steward will check if the enquiry if valid. If the enquiry is considered invalid, a message will appear in the “race_control” discord chat stating that the enquiry is refused and why.
- 5.2.7The stewards will then debate and decide on a possible penalty for the enquiry. Once a decision has been made, it will be added to a queue of penalty.
- 5.2.8At regular intervals, the stewards will post a report on Discord including all the penalties of the enquiries judged. In this report will be listed the enquiries, the decision of these enquiries and the time of the next report.
- 5.2.9Any imitation of the stewards and/or coordinators in the in-game chat will result in an instant kick of the responsible car.
Due to the length of the race and the possibility of a limited amount of stewards being available, it is possible a penalty is awarded later than you would normally expect.
- 5.4 Live stewarding - Penalties and license points system
- 5.4.1The available race penalties during live stewarding are:
● 5-10-15 second time penalty - Dangerous driving, driving in an unsporting manner or causing a minor avoidable collision.
● 0-45 second time penalty - Causing a moderate avoidable collision.
● 0-90 second time penalty - Causing a major avoidable collision.
● Disqualification - Intentionally trying or crashing into another car and other unacceptable behavior. Can also be used by the race director for various other reasons like causing too many incidents within a single race (which will be stated in Discord after the race).
- 5.4.2Penalty modifiers:
• +5 seconds and one additional license point - Causing an avoidable incident in the opening lap.
- 5.4.3After every race, an overview of penalties awarded during the race will be published.
Note: License points may additionally be handed out for writing in the in-game chat during the superpole or race session.
- 5.5 Reprimand system
While the race penalties and license 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 2 reprimands, you're out. Receiving 2 reprimands will also likely result in being excluded from future endurance races.
A reprimand can be given for:
● 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.
By signing up to this race, your team automatically accepts to follow the rules and guidelines made by AOR for this race.
Your main source of information should always be the AOR Discord.
If sudden changes to the event have to be made due to game updates, we will announce this in Discord through the designated discord tag. We will then also update this manual if needed.
The organizers of the race will always have the final say on matters not clearly explained in the rules/guidelines.
The organizers of the race reserve the right to adjust weather or event settings if deemed necessary.
The organizers of the race reserve the right to remove a team/squad from the event if the squad is identified as a "placeholder-entry", meaning that the team/squad, in it's current form, doesn't fulfill the criteria to participate in the race and is hence considered to be used to block a spot and prevent other teams/squads from signing up.
In case of requests/questions:
If you have any questions or requests, please direct message one of the event organizers. This should always be the first go-to to for example let the organizers make last-minute changes to the entrylists or in general get questions answered.
|404 Apex Not Found||GT4||Aston Martin Vantage GT4 (2018)||404|
|Ankarada Icmece||BMW M2||BMW M2 CS (2022)||601|
|BeesWax Racing||Crab||BMW M2||BMW M2 CS (2022)||333|
|BeesWax Racing||GT4-2||GT4||Porsche 718 Cayman GT4 (2019)||888|
|Békés Esport Racing Team||Endurance||CUP||Porsche 992 GT3 Cup (2022)||258|
|Capital SimRacers||TC is overrated||CUP||Porsche 992 GT3 Cup (2022)||16|
|Celtic Bromance||45th president of the United States||GT4||Porsche 718 Cayman GT4 (2019)||277|
|Celtic Bromance||AMURICA||GT4||Aston Martin Vantage GT4 (2018)||177|
|Celtic Bromance||F Yeah!||GT4||Aston Martin Vantage GT4 (2018)||27|
|Celtic Bromance||sBinotto Fanclub||CUP||Porsche 992 GT3 Cup (2022)||377|
|Drehmoment Racing||GT4||Porsche 718 Cayman GT4 (2019)||69|
|Full Boost Racing||Full Boost Racing||BMW M2||BMW M2 CS (2022)||467|
|G Ligue eSport 1||G Ligue eSport 1||BMW M2||BMW M2 CS (2022)||59|
|Goat Racing||Man United||BMW M2||BMW M2 CS (2022)||777|
|Goat Racing||The Goat's New Groove||BMW M2||BMW M2 CS (2022)||222|
|Handicap Racing||5s off pace||GT4||Aston Martin Vantage GT4 (2018)||88|
|Helios E-sport Studio||GT4||Porsche 718 Cayman GT4 (2019)||996|
|HeXagon Nation||Team Amber||BMW M2||BMW M2 CS (2022)||111|
|HeXagon Nation||Team Black||CUP||Porsche 992 GT3 Cup (2022)||114|
|HeXagon Nation||Team Blue||GT4||Porsche 718 Cayman GT4 (2019)||49|
|Intercontinental Racing||CUP||Porsche 992 GT3 Cup (2022)||77|
|IRL Racing Team||CUP||Porsche 992 GT3 Cup (2022)||6|
|JarZomB Community Team||CUP||Porsche 992 GT3 Cup (2022)||36|
|Karimbabimba Motorsport||BMW M2||BMW M2 CS (2022)||17|
|N7 Racing||GT4||Porsche 718 Cayman GT4 (2019)||117|
|No Time To Pee||Nor Practice||BMW M2||BMW M2 CS (2022)||340|
|Northern Ireland Nighthawks||Zulu||GT4||Porsche 718 Cayman GT4 (2019)||969|
|Porsche Sbinnala Team||Giga Cooper||GT4||Porsche 718 Cayman GT4 (2019)||420|
|Pulse SimSport||CUP||Porsche 992 GT3 Cup (2022)||52|
|Rising Panda Racing||GT4||Porsche 718 Cayman GT4 (2019)||46|
|RPMS SimSport||992 Cup #808||CUP||Porsche 992 GT3 Cup (2022)||808|
|RPMS SimSport||Not Chevy #707||GT4||Aston Martin Vantage GT4 (2018)||707|
|Silver Racing Team||GT4||Porsche 718 Cayman GT4 (2019)||101|
|Single and good looking||GT4||Porsche 718 Cayman GT4 (2019)||7|
|smol pp||the smolest||BMW M2||BMW M2 CS (2022)||13|
|SPQRacing Team||SPQRACING #1||CUP||Porsche 992 GT3 Cup (2022)||201|
|SPQRacing Team||SPQRACING #2||BMW M2||BMW M2 CS (2022)||202|
|SPQRacing Team||SPQRACING #3||GT4||Porsche 718 Cayman GT4 (2019)||203|
|Team Hivemind||Grumpy Old Porkers||CUP||Porsche 992 GT3 Cup (2022)||728|
|Team Racing Point 3||Team Racing Point||GT4||Porsche 718 Cayman GT4 (2019)||85|
|The Brexit Bois||Purple||BMW M2||BMW M2 CS (2022)||8|
|Turn1||M2||BMW M2||BMW M2 CS (2022)||102|
|URL||GT4||Porsche 718 Cayman GT4 (2019)||28|
|1||Willem Karsten||Team Hivemind Grumpy Old Porkers||01:45.445||CUP||1||68||1|
|2||Pawel Jarzebowski||JarZomB Community Team||01:45.780||CUP||2||169||4|
|3||Matteo Cinotti||SPQRacing Team SPQRACING #1||01:45.812||CUP||3||158||3|
|4||Alessandro Zampieri||SPQRacing Team SPQRACING #1||01:45.822||CUP||4||207||4|
|5||Alberto Betti [SPQR]||SPQRacing Team SPQRACING #1||01:45.887||CUP||5||44||2|
|6||Daniele Riccitelli||SPQRacing Team SPQRACING #1||01:46.067||CUP||6||47||5|
|7||Christian Hamrebo||HeXagon Nation Team Black||01:46.185||CUP||7||293||0|
|8||Matt Stevens[RPMS]||RPMS SimSport 992 Cup #808||01:46.457||CUP||8||39||11|
|9||John GIXXER_osg||Team Hivemind Grumpy Old Porkers||01:46.467||CUP||9||88||2|
|10||dakuza||Team Hivemind Grumpy Old Porkers||01:46.477||CUP||10||61||4|
|11||Jay Janz||Capital SimRacers TC is overrated||01:46.545||CUP||11||126||9|
|12||Ciaran Hendriks||IRL Racing Team||01:46.660||CUP||12||72||8|
|13||Philipp Döhring||IRL Racing Team||01:46.810||CUP||13||67||8|
|14||Thomas Wright||IRL Racing Team||01:46.810||CUP||14||93||2|
|15||Rytis Kazlauskas||Celtic Bromance sBinotto Fanclub||01:46.930||CUP||15||66||6|
|16||Daniel Holmer||HeXagon Nation Team Black||01:47.010||CUP||16||75||0|
|17||Jake Mills||Celtic Bromance sBinotto Fanclub||01:47.105||CUP||17||37||7|
|18||Thomas Allendorf||Capital SimRacers TC is overrated||01:47.110||CUP||18||181||7|
|19||Jerzy Wawrzyczek||JarZomB Community Team||01:47.120||CUP||19||49||14|
|20||Richard Phillips[RPMS]||RPMS SimSport 992 Cup #808||01:47.300||CUP||20||22||6|
|21||Michal Balicki||JarZomB Community Team||01:47.387||CUP||21||133||5|
|22||Samuel Christiansen||HeXagon Nation Team Black||01:47.547||CUP||22||240||2|
|23||Claudio Voodoo||Team Hivemind Grumpy Old Porkers||01:47.567||CUP||23||100||6|
|24||Oskar Motin||HeXagon Nation Team Black||01:47.590||CUP||24||242||4|
|25||Szabolcs Békés||Békés Esport Racing Team Endurance||01:48.522||CUP||25||129||4|
|26||Simone Bisoglio[SPQR]||SPQRacing Team SPQRACING #3||01:53.747||GT4||1||229||4|
|28||Diego Carlino||SPQRacing Team SPQRACING #3||01:54.120||GT4||3||60||2|
|29||Fabio Calandrino||SPQRacing Team SPQRACING #3||01:54.187||GT4||4||77||7|
|31||Christian Campregher||Rising Panda Racing||01:54.220||GT4||6||53||3|
|32||Simon Beeg||N7 Racing||01:54.280||GT4||7||40||2|
|33||Kristers Podēns||Celtic Bromance 45th president of the United States||01:54.410||GT4||8||64||5|
|34||Luke Stokes||Rising Panda Racing||01:54.557||GT4||9||79||5|
|35||Michael Löffler||Rising Panda Racing||01:54.600||GT4||10||110||2|
|36||HaiCo||Single and good looking||01:54.672||GT4||11||13||5|
|37||Krab Athor||Celtic Bromance 45th president of the United States||01:54.747||GT4||12||92||3|
|38||Kulakov Eugene||BeesWax Racing GT4-2||01:54.792||GT4||13||32||1|
|39||Mikolaj Nowicki||Silver Racing Team||01:54.820||GT4||14||18||8|
|40||Sam Mawdsley||N7 Racing||01:54.845||GT4||15||35||5|
|41||Kiki Mac||Celtic Bromance AMURICA||01:54.962||GT4||16||20||1|
|42||Tom Shipston||RPMS SimSport Not Chevy #707||01:54.987||GT4||17||11||9|
|43||NynS||404 Apex Not Found||01:54.990||GT4||18||92||8|
|44||Ryan Cooper||Porsche Sbinnala Team Giga Cooper||01:55.040||GT4||19||23||9|
|45||Mateusz Cienkowski||Silver Racing Team||01:55.072||GT4||20||25||7|
|46||Paweł Cieśla||Silver Racing Team||01:55.142||GT4||21||14||6|
|47||Alex Zackdahl||HeXagon Nation Team Blue||01:55.167||GT4||22||32||13|
|48||Rene Battenberg||N7 Racing||01:55.220||GT4||23||31||1|
|49||Dan Barnard||Celtic Bromance AMURICA||01:55.252||GT4||24||85||1|
|50||Josh Waring||Celtic Bromance AMURICA||01:55.290||GT4||25||43||12|
|51||Luoper||Helios E-sport Studio||01:55.307||GT4||26||63||5|
|52||Chris Saybia||BeesWax Racing GT4-2||01:55.447||GT4||27||41||0|
|53||Luca Ziege||Porsche Sbinnala Team Giga Cooper||01:55.475||GT4||28||5||0|
|54||Kalimazoo||Celtic Bromance F Yeah!||01:55.525||GT4||29||42||1|
|55||Daniel Hedström||HeXagon Nation Team Blue||01:55.720||GT4||30||19||10|
|56||Daniel Crinson||RPMS SimSport Not Chevy #707||01:55.892||GT4||31||40||4|
|57||Hubert Bibr||Handicap Racing 5s off pace||01:55.897||GT4||32||22||7|
|58||Manuel Düchs||Single and good looking||01:55.935||GT4||33||51||13|
|59||Bart De Jong||404 Apex Not Found||01:56.025||GT4||34||30||2|
|60||JP Mc Kinley||Celtic Bromance F Yeah!||01:56.065||GT4||35||32||6|
|61||Alastair Baldwin||Celtic Bromance F Yeah!||01:56.257||GT4||36||15||8|
|62||Edison Qiu||Helios E-sport Studio||01:56.327||GT4||37||103||2|
|63||Scott Cranston||Northern Ireland Nighthawks Zulu||01:56.390||GT4||38||10||8|
|64||Wiktor Nykaza||Handicap Racing 5s off pace||01:56.565||GT4||39||14||9|
|65||Telescope||Helios E-sport Studio||01:56.632||GT4||40||34||11|
|66||Wiktor Tkaczynski||Handicap Racing 5s off pace||01:57.400||GT4||41||25||8|
|67||1k||Helios E-sport Studio||01:57.452||GT4||42||36||11|
|68||Tobias Hakansson||HeXagon Nation Team Blue||01:57.967||GT4||43||63||6|
|69||Jamie Sterritt||Northern Ireland Nighthawks Zulu||01:58.052||GT4||44||9||3|
|70||Willy Cranston||Northern Ireland Nighthawks Zulu||01:58.497||GT4||45||10||54|
|71||Tomasz Siwek||Full Boost Racing Full Boost Racing||02:00.467||BMW M2||1||20||6|
|72||Robin Moe||smol pp the smolest||02:00.907||BMW M2||2||38||2|
|73||Michał Pochopień||Full Boost Racing Full Boost Racing||02:00.925||BMW M2||3||49||3|
|74||Jérôme Demazure | GL||G Ligue eSport 1 G Ligue eSport 1||02:01.147||BMW M2||4||222||2|
|75||Thomas Jack||smol pp the smolest||02:01.252||BMW M2||5||36||0|
|76||Xavier Lavost | GL||G Ligue eSport 1 G Ligue eSport 1||02:01.445||BMW M2||6||146||4|
|77||Victor BoE||smol pp the smolest||02:01.837||BMW M2||7||54||5|
|78||Michal Augustynek [NTTP]||No Time To Pee Nor Practice||02:01.885||BMW M2||8||36||15|
|79||Westie||HeXagon Nation Team Amber||02:01.920||BMW M2||9||243||4|
|80||Daniel VanderLinde||Goat Racing The Goat's New Groove||02:01.955||BMW M2||10||29||3|
|81||Daniel Nilsson||HeXagon Nation Team Amber||02:01.965||BMW M2||11||59||6|
|82||Marton Cynolter||BeesWax Racing Crab||02:02.057||BMW M2||12||40||6|
|83||Jonathan Serafino||SPQRacing Team SPQRACING #2||02:02.095||BMW M2||13||93||5|
|84||Dami Ayo||BeesWax Racing Crab||02:02.360||BMW M2||14||4||6|
|85||Artur Myszka [NTTP]||No Time To Pee Nor Practice||02:02.535||BMW M2||15||36||8|
|86||Arkadiusz Kuprowski||No Time To Pee Nor Practice||02:02.595||BMW M2||16||34||17|
|87||Luca Matrigiani [SPQR]||SPQRacing Team SPQRACING #2||02:02.600||BMW M2||17||50||13|
|88||Tudor Florea||Goat Racing Man United||02:02.680||BMW M2||18||35||46|
|89||Jasper van Ruiten||Goat Racing Man United||02:02.812||BMW M2||19||56||2|
|90||Patrik Pfeffer||HeXagon Nation Team Amber||02:03.685||BMW M2||20||43||11|
|91||Claudio Davi||SPQRacing Team SPQRACING #2||02:03.705||BMW M2||21||89||13|
|92||Alyssa Pelletier-Sharpe||Turn1 M2||02:04.167||BMW M2||22||7||5|
|93||William Burfield||Goat Racing The Goat's New Groove||02:04.615||BMW M2||23||13||5|
|94||Tristan Ferguson||Turn1 M2||02:04.775||BMW M2||24||9||25|
|#||Team||Class||Car||Team Avg Best||Gap to #1||Gap||Rank||Valid|
|1||SPQRacing Team SPQRACING #1||CUP||01:45.897||00.000||00.000||1||4 / 4|
Alberto Betti [SPQR]
|2||Team Hivemind Grumpy Old Porkers||CUP||01:46.489||00.592||00.592||1||4 / 4|
|3||IRL Racing Team||CUP||01:46.760||00.863||00.271||1||3 / 3|
|4||JarZomB Community Team||CUP||01:46.762||00.865||00.002||1||3 / 3|
|5||Capital SimRacers TC is overrated||CUP||01:46.827||00.930||00.065||1||2 / 2|
|6||RPMS SimSport 992 Cup #808||CUP||01:46.878||00.981||00.051||1||2 / 2|
|7||Celtic Bromance sBinotto Fanclub||CUP||01:47.017||01.120||00.139||1||2 / 2|
|8||HeXagon Nation Team Black||CUP||01:47.083||01.186||00.065||1||4 / 4|
|9||Békés Esport Racing Team Endurance||CUP||01:48.522||02.625||01.439||2||1 / 2|
|10||SPQRacing Team SPQRACING #3||GT4||01:54.018||08.121||05.496||1||3 / 3|
|11||URL||GT4||01:54.131||08.234||00.113||1||2 / 2|
|12||Rising Panda Racing||GT4||01:54.459||08.562||00.328||1||3 / 3|
|13||Celtic Bromance 45th president of the United States||GT4||01:54.578||08.681||00.119||1||2 / 2|
|14||N7 Racing||GT4||01:54.781||08.884||00.203||1||3 / 3|
|15||Silver Racing Team||GT4||01:55.011||09.114||00.229||1||3 / 3|
|16||BeesWax Racing GT4-2||GT4||01:55.119||09.222||00.108||1||2 / 2|
|17||Celtic Bromance AMURICA||GT4||01:55.168||09.271||00.048||1||3 / 3|
|18||Porsche Sbinnala Team Giga Cooper||GT4||01:55.257||09.360||00.089||1||2 / 2|
|19||Single and good looking||GT4||01:55.303||09.406||00.046||1||2 / 2|
|20||RPMS SimSport Not Chevy #707||GT4||01:55.439||09.542||00.136||1||2 / 2|
|21||404 Apex Not Found||GT4||01:55.507||09.610||00.068||1||2 / 2|
Bart De Jong
|22||Celtic Bromance F Yeah!||GT4||01:55.949||10.052||00.441||1||3 / 3|
JP Mc Kinley
|23||HeXagon Nation Team Blue||GT4||01:56.284||10.387||00.335||1||3 / 3|
|24||Helios E-sport Studio||GT4||01:56.429||10.532||00.144||1||4 / 4|
|25||Handicap Racing 5s off pace||GT4||01:56.620||10.723||00.191||1||3 / 3|
|26||Northern Ireland Nighthawks Zulu||GT4||01:57.646||11.749||01.025||1||3 / 3|
|27||Full Boost Racing Full Boost Racing||BMW M2||02:00.696||14.799||03.049||1||2 / 2|
|28||G Ligue eSport 1 G Ligue eSport 1||BMW M2||02:01.296||15.399||00.600||1||2 / 2|
|Jérôme Demazure | GL|
Xavier Lavost | GL
|29||smol pp the smolest||BMW M2||02:01.332||15.435||00.036||1||3 / 3|
|30||BeesWax Racing Crab||BMW M2||02:02.208||16.311||00.876||1||2 / 2|
|31||No Time To Pee Nor Practice||BMW M2||02:02.338||16.441||00.129||1||3 / 3|
|Michal Augustynek [NTTP]|
Artur Myszka [NTTP]
|32||HeXagon Nation Team Amber||BMW M2||02:02.523||16.626||00.185||1||3 / 3|
|33||Goat Racing Man United||BMW M2||02:02.746||16.849||00.222||1||2 / 2|
Jasper van Ruiten
|34||SPQRacing Team SPQRACING #2||BMW M2||02:02.800||16.903||00.054||1||3 / 3|
Luca Matrigiani [SPQR]
|35||Goat Racing The Goat's New Groove||BMW M2||02:03.285||17.388||00.485||1||2 / 2|
|36||Turn1 M2||BMW M2||02:04.471||18.574||01.186||1||2 / 2|
|37||Team Racing Point 3 Team Racing Point||GT4||00:00.000||5||0 / 3|
|38||Drehmoment Racing||GT4||00:00.000||5||0 / 2|
|39||Pulse SimSport||CUP||00:00.000||5||0 / 2|
|40||Ankarada Icmece||BMW M2||00:00.000||5||0 / 4|
|41||Intercontinental Racing||CUP||00:00.000||5||0 / 2|
|42||Karimbabimba Motorsport||BMW M2||00:00.000||5||0 / 2|
|43||The Brexit Bois Purple||BMW M2||00:00.000||5||0 / 3|
|1||SPQRacing Team SPQRACING #1|| Alessandro Zampieri|
Alberto Betti [SPQR]
|2||Celtic Bromance sBinotto Fanclub|| Rytis Kazlauskas|
|3||RPMS SimSport 992 Cup #808|| Richard Phillips[RPMS]|
|4||JarZomB Community Team|| Pawel Jarzebowski|
|5||Capital SimRacers TC is overrated|| Thomas Allendorf|
|6||HeXagon Nation Team Black|| Samuel Christiansen|
|7||IRL Racing Team|| Ciaran Hendriks|
|8||Team Hivemind Grumpy Old Porkers|| dakuza|
|9||Békés Esport Racing Team Endurance|| Szabolcs Békés|
|10||Silver Racing Team|| Mikolaj Nowicki|
|11||RPMS SimSport Not Chevy #707|| Daniel Crinson|
|12||Celtic Bromance AMURICA|| Kiki Mac|
|13||N7 Racing|| Sam Mawdsley|
|14||404 Apex Not Found|| NynS|
Bart De Jong
|15||BeesWax Racing GT4-2|| Kulakov Eugene|
|16||Celtic Bromance 45th president of the United States|| Kristers Podēns|
|17||Handicap Racing 5s off pace|| Wiktor Nykaza|
|18||Celtic Bromance F Yeah!|| Alastair Baldwin|
JP Mc Kinley
|19||Full Boost Racing Full Boost Racing|| Michał Pochopień|
|20||Helios E-sport Studio|| Telescope|
|21||BeesWax Racing Crab|| Dami Ayo|
|22||SPQRacing Team SPQRACING #3|| Simone Bisoglio[SPQR]|
|23||smol pp the smolest|| Thomas Jack|
|24||Goat Racing The Goat's New Groove|| Daniel VanderLinde|
|25||Goat Racing Man United|| Jasper van Ruiten|
|26||G Ligue eSport 1 G Ligue eSport 1|| Jérôme Demazure | GL|
Xavier Lavost | GL
|27||Northern Ireland Nighthawks Zulu|| Scott Cranston|
|28||SPQRacing Team SPQRACING #2|| Claudio Davi|
Luca Matrigiani [SPQR]
|29||Rising Panda Racing|| Christian Campregher|
|30||Porsche Sbinnala Team Giga Cooper|| Ryan Cooper|
|31||No Time To Pee Nor Practice|| Arkadiusz Kuprowski|
Michal Augustynek [NTTP]
Artur Myszka [NTTP]
|33||HeXagon Nation Team Amber|| Westie|
|34||Turn1 M2|| Tristan Ferguson|