Freedom 12H - COTA

Apex Online Racing

Event Information

Signups closed

Entries:

42 / 50

Sign-ups are limited to maximum 50 teams

Signup period:

08.07.2022 - 02.08.2022

Event date:

06.08.2022 11:00 UTC

Qualifying period:

24.07.2022 09:00 - 03.08.2022 23:59

Event Information:

Dates:
- Signups open 08.07.2022
- Signups closure and squads locked 02.08.2022
- Qualifying server open: 24.07.2022 - 03.08.2022 23:59 BST
- Pre-race practice session: 06.08.2022 11:00 BST - 12:00 BST
- Race: 06.08.2022 12:00 BST - 12 hours
- Green flag: approx. 12:05 BST

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, 22 degrees average ambient temperature, cloud level: 0.3, weather randomness: 3, rain level setting 0.00.

Race day weather probabilities - according to testing:
- 75% dry

Event-specific rules:
- Minimum of 2 drivers per team
- Maximum of 4 drivers per team
- Maximum stint time - 65 minutes
- No limitation on tire sets
- No mandatory pitstops
- Refueling time not fixed
- GT3 only

Race server settings:

Custom BOP:
- AMR V8 Vantage: +10kg
- Audi R8 LMS Evo II: +30kg
- Bentley Continental GT3 2018: +10kg
- BMW M4 GT3: +5kg
- Ferrari 488 GT3 Evo: +10kg
- Lamborghini Huracan GT3 Evo +5kg
- McLaren 720S GT3: +5kg
- Porsche 991 II GT3 R: +15kg
- All other cars: +0kg

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 02.08.22 at 23:59 BST

Here is an overview of the servers we have set up for the event:
- ApexOnline.Racing #27 | Freedom 12H | Solo practice #1 | #AORERP
- ApexOnline.Racing #28 | Freedom 12H | Solo practice #2 | #AORERP
- ApexOnline.Racing #29 | Freedom 12H | Solo practice #3 (fixed conditions) | #AORERP
- ApexOnline.Racing #30 | Freedom 12H | Solo practice (9x) | #AORERP
- ApexOnline.Racing #31 | Freedom 12H | Solo practice (0.2 rain) | #AORERP
- ApexOnline.Racing #32 | Freedom 12H | Solo practice (0.4 rain) | #AORERP
- ApexOnline.Racing #33 | Freedom 12H | Solo practice (dark) | #AORERP
- ApexOnline.Racing #34 | Freedom 12Hn | Team practice #1 | #AORERP
- ApexOnline.Racing #35 | Freedom 12H | Team practice #2 (fixed conditions) | #AORERP
- ApexOnline.Racing #36 | Freedom 12H | Qualifying server #1 | #AORERQ
- ApexOnline.Racing #37 | Freedom 12H | Qualifying server #2 | #AORERQ
- ApexOnline.Racing #38 | Freedom 12H | Qualifying server #3 | #AOREQ

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 and model.
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 organizer for this event is @HaiCo#5686 on discord.
Squads are required to be present on the AOR Discord in order to participate in this event

1.1 Live Stewarding
- 1.1.1
  
  Link to the page where you can create an enquiry: Enquiry form
- 1.1.2
  
  The event will feature live stewarding done by the AOR steward team.
- 1.1.3
  
  The 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.4
  
  Make sure that all members of your team have a functional recording solution ready before the start of the race.
- 1.1.5
  
  Instructions on which software to use to record incidents can be found in "how to record evidence"
1.2 How to report
- 1.2.1
  
  You have 30 minutes after the incident happened, to report it.
- 1.2.2
  
  To 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.3
  
  The 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.4
  
  If 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.5
  
  Afterwards, you need to complete the following Google Forms with the correct information (server number, number of the cars…)
- 1.2.6
  
  Once 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.7
  
  The 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.8
  
  At 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.
1.3
- 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.1
  
  Contact resulting in significant damage or a spin
- 1.4.2
  
  Push off the track
- 1.4.3
  
  Massive divebomb
- 1.4.4
  
  Unsafe rejoin
1.5 What won’t be looked at by the stewards
- 1.5.1
  
  Any 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.1
  
  Race 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.2
  
  Deliberately 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.3
  
  If 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.1
  
  Don'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.2
  
  Overtaking 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.1
  
  Excessive 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.2
  
  It 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.3
  
  The 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.1
  
  Stay 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.2
  
  Penalties 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.1
  
  In 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.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 Spacial Awareness
- 1.6.1
  
  You 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.2
  
  If 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.3
  
  If 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.4
  
  If you go off the track, rejoin in a manner that is both safe and in no way a danger to other competitors.
- 1.6.5
  
  Using 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.1
  
  We 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.2
  
  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 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.3
  
  As 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.4
  
  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.5
  
  If 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.1
  
  In 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.2
  
  The 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.3
  
  At all times, the slower class car is required to stick to one racing line and not change his direction erratically.
- 2.2.4
  
  Passes 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.1
  
  Every 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.2
  
  A car is considered to be in the pit exit or entry zone when all four wheels are within the white lines.
- 2.3.3
  
  Once 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.4
  
  Use 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.5
  
  The 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.1
  
  Endurance 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.2
  
  If 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.3
  
  It is encouraged to use a version of the car with additional endurance lighting to improve night time visibility.
- 2.4.4
  
  Should 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.1
  
  If 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.2
  
  Using 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.1
  
  Drivers are at all times supposed to strictly follow the instructions given by the in-game widget.
- 2.7.2
  
  Drive through penalties awarded by the game will not be reverted.

3.1 Communication
- 3.1.1
  
  All 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.2
  
  Driver 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.3
  
  Once 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.1
  
  Shouting, 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.2
  
  Respect 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. 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.1
  
  If 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.2
  
  If 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.3
  
  If 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.4
  
  Wait 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.5
  
  The 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.6
  
  Penalties 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.1
  
  Deliberately 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.2
  
  Excuses 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.3
  
  Connection 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.1
  
  If 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.2
  
  If 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.3
  
  The 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.4
  
  Getting 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.1
  
  This 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.2
  
  What 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.
- 5.1.3
  
  Link to the page where you can create an enquiry: Enquiry form
- 5.1.4
  
  The 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.5
  
  Make 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.1
  
  You have 30 minutes after the incident happened, to report it.
- 5.2.2
  
  To 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.3
  
  The 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.4
  
  If 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.5
  
  Afterwards, you need to fill out the provided Google Forms with the correct information (server number, number of the cars…).
- 5.2.6
  
  Once 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.7
  
  The 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.8
  
  At 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.9
  
  Any imitation of the stewards and/or coordinators in the in-game chat will result in an instant kick of the responsible car.
5.3
- 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.
5.4 Live stewarding - Penalties and license points system
- 5.4.1
  
  The 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.2
  
  Penalty modifiers:
  • +5 seconds and one additional license point - Causing an avoidable incident in the opening lap.
- 5.4.3
  
  After 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.

6.1
- By signing up to this race, your team automatically accepts to follow the rules and guidelines made by AOR for this race.
6.2
- Your main source of information should always be the AOR Discord.
6.3
- 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.
6.4
- The organizers of the race will always have the final say on matters not clearly explained in the rules/guidelines.
6.5
- The organizers of the race reserve the right to adjust weather or event settings if deemed necessary.
6.6
- 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.
6.7
- 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.

Teamname	Squadname	Class	Car	#

Team Average
Individual

#	Driver	Team	BestRun	Class	Laps	Fuel
1	Tommy Lyden	LeMans RennSport	02:03.937	GT3	14	0
2	Patryk Lipka	SimuNation eSport SimuNation E-Sport	02:04.492	GT3	7	0
3	Jamie Nuttall	CRACKD.Racing	02:04.695	GT3	57	0
4	Predrag Jevremovic	LeMans RennSport	02:04.695	GT3	14	3
5	Máté Mezőffy	Kúpteam FuturEsportS #1	02:04.710	GT3	88	0
6	Vuksan Videnovic	LeMans RennSport	02:04.800	GT3	54	1
7	Kristers Podēns	Celtic Bromance NoGrip.exe	02:04.832	GT3	79	0
8	Tobias Madl	Garage991	02:04.880	GT3	41	7
9	Bence Szilagyi	Kúpteam FuturEsportS #1	02:05.080	GT3	26	2
10	Bence Fazekas	Kúpteam FuturEsportS #1	02:05.082	GT3	108	6
11	Markus Deck	Team Hivemind Grumpy Old Farts	02:05.202	GT3	162	4
12	DoR	Team Hivemind Cubed	02:05.202	GT3	47	1
13	Nils Schroer	Garage991	02:05.210	GT3	91	7
14	Thomas Jack	smol pp	02:05.240	GT3	75	7
15	Derrick Son	CRACKD.Racing	02:05.260	GT3	64	2
16	Kulakov Eugene	BeesWax Racing DT Crew	02:05.312	GT3	27	1
17	Aider Willspin	Yeet Gaming	02:05.312	GT3	8	3
18	Tim Moors	Team Hivemind Cubed	02:05.372	GT3	116	4
19	Rafael Malho	Consistency OP	02:05.430	GT3	38	3
20	#80 Shooter80	Team Hivemind Cubed	02:05.460	GT3	96	10
21	Kamil Panus	SimuNation eSport SimuNation E-Sport	02:05.482	GT3	114	7
22	Stefan Jentzsch	Garage991	02:05.497	GT3	13	11
23	Josh Waring	Celtic Bromance NoGrip.exe	02:05.507	GT3	59	13
24	Rachel Konkoly	Victorious Secret OG squad	02:05.545	GT3	67	11
25	Pedro Oliveira	Consistency OP	02:05.652	GT3	60	3
26	Igor55	Victorious Secret OG squad	02:05.680	GT3	25	8
27	Jay Fang	Yeet Gaming	02:05.680	GT3	30	1
28	Remco Langedyk	Victorious Secret OG squad	02:05.730	GT3	42	8
29	Dan Barnard	Celtic Bromance NoGrip.exe	02:05.737	GT3	62	2
30	dakuza	Team Hivemind Cubed	02:05.765	GT3	84	0
31	Kiki Mac	Celtic Bromance NoGrip.exe	02:05.772	GT3	26	6
32	Marton Cynolter	BeesWax Racing Bee Quick	02:05.802	GT3	57	4
33	Pawel Jarzebowski	2 sec off pace	02:05.847	GT3	18	3
34	Dami Ayo	BeesWax Racing Bee Quick	02:05.860	GT3	10	7
35	Jordan Woodley	CRACKD.Racing	02:05.965	GT3	169	4
36	Filip Ślaski	SimuNation eSport SimuNation E-Sport	02:05.980	GT3	4	6
37	Thomas Allendorf	Capital SimRacers	02:06.002	GT3	126	10
38	Claudio Voodoo	Team Hivemind Grumpy Old Farts	02:06.037	GT3	155	3
39	Jay Janz	Capital SimRacers	02:06.127	GT3	136	14
40	Krab Athor	Celtic Bromance Drift Club	02:06.130	GT3	53	8
41	Tommy Schets	The Brexit Bois Purple	02:06.142	GT3	11	0
42	Richard Phillips[RPMS]	RPMS SimSport	02:06.272	GT3	58	2
43	Michele Rizzo	Virtual Drivers Alliance	02:06.297	GT3	157	1
44	Alastair Baldwin	Celtic Bromance Drift Club	02:06.335	GT3	34	0
45	Sebastian Björkholm	smol pp	02:06.342	GT3	109	4
46	Jason Dyer	RevolutionSimRacing	02:06.407	GT3	12	6
47	Gaurav Arora	Indian Racing Community	02:06.437	GT3	32	11
48	Kalimazoo	Celtic Bromance Drift Club	02:06.442	GT3	57	4
49	Feri Danics	Kúpteam FuturEsportS #1	02:06.457	GT3	85	4
50	Jerzy Wawrzyczek	2 sec off pace	02:06.482	GT3	17	3
51	Corne Borchers	RevolutionSimRacing	02:06.505	GT3	37	0
52	Samuel Christiansen	HeXagon Nation White	02:06.507	GT3	127	4
53	Daniel Crinson	RPMS SimSport	02:06.517	GT3	45	5
54	Chris Saybia	BeesWax Racing DT Crew	02:06.537	GT3	64	9
55	Raj Deepak	Indian Racing Community	02:06.550	GT3	24	11
56	Michal Balicki	2 sec off pace	02:06.617	GT3	111	0
57	Liam Young	SXS Racing Team Blue	02:06.622	GT3	80	0
58	Matt Stevens[RPMS]	RPMS SimSport	02:06.640	GT3	64	4
59	Brian Schekkerman	NoName	02:06.765	GT3	9	4
60	Javi Hernando	JVM Racing	02:06.772	GT3	56	1
61	Michal Augustynek [NTTP]	No Time To Pee	02:06.805	GT3	55	0
62	Furkan Hosman	Amino-Asseto Motorhersteller Amino-Asseto	02:06.910	GT3	99	8
63	Daniel Smith	Team Hivemind Grumpy Old Farts	02:06.930	GT3	44	8
64	Armando Ortenzi	Virtual Drivers Alliance	02:06.965	GT3	126	3
65	Roy Momann	Garage991	02:07.080	GT3	9	16
66	Daniel Nilsson	HeXagon Nation Black	02:07.107	GT3	70	1
67	Safa Kelkit	Amino-Asseto Motorhersteller Amino-Asseto	02:07.242	GT3	79	5
68	R Matthieson \| HeX	HeXagon Nation White	02:07.247	GT3	184	7
69	Miguel Aguerri	JVM Racing	02:07.262	GT3	41	1
70	The Lazy-Badger	BeesWax Racing DT Crew	02:07.290	GT3	53	2
71	Oskar Motin \| HeX	HeXagon Nation Black	02:07.317	GT3	116	2
72	Yannick Lautenschläger	Hela Gewürzketchup Racing Boom & Zoom	02:07.320	GT3	25	6
73	Berke Aras	Amino-Asseto Motorhersteller Amino-Asseto	02:07.347	GT3	47	5
74	Artur Myszka [NTTP]	No Time To Pee	02:07.465	GT3	54	13
75	Lord Nem	FuzzyLlamas	02:07.510	GT3	103	5
76	Alfred Lubich	Hela Gewürzketchup Racing Boom & Zoom	02:07.555	GT3	92	1
77	Adrian Reilly	No Time To Pee	02:07.630	GT3	27	13
78	NynS	FuzzyLlamas	02:07.662	GT3	48	6
79	Tiago Presa de Castro	Castro ESports Team	02:07.677	GT3	22	3
80	Casper Björk \| HeX	HeXagon Nation Black	02:07.745	GT3	55	4
81	Attila Kodé	CRACKD.Racing	02:07.790	GT3	24	10
82	Daniel Blakeman	Celtic Bromance Drift Club	02:07.822	GT3	10	19
83	Blindguy Morphee7	Team Hivemind Grumpy Old Farts	02:07.880	GT3	146	4
84	Víctor Fernández	JVM Racing	02:07.900	GT3	122	103
85	Stuart Pietzka	FuzzyLlamas	02:07.957	GT3	107	6
86	Rikka Takanashi	Karimbabimba Motorsport	02:07.992	GT3	12	30
87	Jamie Ellis	The Brexit Bois Purple	02:07.997	GT3	7	7
88	Harald Klöppelmann	Karimbabimba Motorsport	02:08.142	GT3	35	14
89	Viking Rap	FuzzyLlamas	02:08.207	GT3	109	9
90	Wojciech Zarzecki	Secret Scam Chads	02:08.460	GT3	40	46
91	Moberg	smol pp	02:08.462	GT3	33	12
92	HaiCo	Snail Racing	02:08.677	GT3	16	12
93	Thomas Kinell \| HeX	HeXagon Nation Black	02:08.842	GT3	130	6
94	michael lievens	Snail Racing	02:09.025	GT3	28	3
95	Craig Parsons	Hyperion Racing bubblegum	02:09.395	GT3	45	4
96	Daan van Geloven	BeesWax Racing Bee Quick	02:09.462	GT3	25	2
97	Andrew Hardy	SXS Racing Team Blue	02:09.690	GT3	37	4
98	Kian Dickens	SXS Racing Team Blue	02:09.887	GT3	7	4
99	Patrik Pfeffer \| HeX	HeXagon Nation White	02:09.960	GT3	108	14
100	Chris Jenkins \| HeX	HeXagon Nation White	02:09.970	GT3	24	4
101	Octavian Robu	Secret Scam Chads	02:10.160	GT3	11	8
102	Darren Reynolds	Snail Racing	02:12.012	GT3	23	2

#	Team	Class	Team Avg Best	Gap to #1	Gap	Rank	Valid
1	LeMans RennSport	GT3	02:04.477	00.000	00.000	1	3 / 3
	Tommy Lyden Predrag Jevremovic Vuksan Videnovic		02:03.937 02:04.695 02:04.800
2	SimuNation eSport SimuNation E-Sport	GT3	02:05.318	00.840	00.840	1	3 / 3
	Patryk Lipka Kamil Panus Filip Ślaski		02:04.492 02:05.482 02:05.980
3	Kúpteam FuturEsportS #1	GT3	02:05.332	00.854	00.014	1	4 / 4
	Máté Mezőffy Bence Szilagyi Bence Fazekas Feri Danics		02:04.710 02:05.080 02:05.082 02:06.457
4	Team Hivemind Cubed	GT3	02:05.449	00.972	00.117	1	4 / 4
	DoR Tim Moors #80 Shooter80 dakuza		02:05.202 02:05.372 02:05.460 02:05.765
5	Celtic Bromance NoGrip.exe	GT3	02:05.462	00.984	00.012	1	4 / 4
	Kristers Podēns Josh Waring Dan Barnard Kiki Mac		02:04.832 02:05.507 02:05.737 02:05.772
6	Yeet Gaming	GT3	02:05.496	01.018	00.034	1	2 / 2
	Aider Willspin Jay Fang		02:05.312 02:05.680
7	Consistency OP	GT3	02:05.541	01.063	00.045	1	2 / 2
	Rafael Malho Pedro Oliveira		02:05.430 02:05.652
8	Victorious Secret OG squad	GT3	02:05.651	01.174	00.110	1	3 / 3
	Rachel Konkoly Igor55 Remco Langedyk		02:05.545 02:05.680 02:05.730
9	Garage991	GT3	02:05.666	01.189	00.015	1	4 / 4
	Tobias Madl Nils Schroer Stefan Jentzsch Roy Momann		02:04.880 02:05.210 02:05.497 02:07.080
10	CRACKD.Racing	GT3	02:05.927	01.450	00.260	1	4 / 4
	Jamie Nuttall Derrick Son Jordan Woodley Attila Kodé		02:04.695 02:05.260 02:05.965 02:07.790
11	Capital SimRacers	GT3	02:06.064	01.587	00.137	1	2 / 2
	Thomas Allendorf Jay Janz		02:06.002 02:06.127
12	2 sec off pace	GT3	02:06.315	01.838	00.250	1	3 / 3
	Pawel Jarzebowski Jerzy Wawrzyczek Michal Balicki		02:05.847 02:06.482 02:06.617
13	BeesWax Racing DT Crew	GT3	02:06.379	01.902	00.064	1	3 / 3
	Kulakov Eugene Chris Saybia The Lazy-Badger		02:05.312 02:06.537 02:07.290
14	RevolutionSimRacing	GT3	02:06.456	01.978	00.076	1	2 / 2
	Jason Dyer Corne Borchers		02:06.407 02:06.505
15	RPMS SimSport	GT3	02:06.476	01.999	00.020	1	3 / 3
	Richard Phillips[RPMS] Daniel Crinson Matt Stevens[RPMS]		02:06.272 02:06.517 02:06.640
16	Indian Racing Community	GT3	02:06.493	02.016	00.017	2	2 / 3
	Gaurav Arora Raj Deepak		02:06.437 02:06.550
17	Team Hivemind Grumpy Old Farts	GT3	02:06.512	02.034	00.018	1	4 / 4
	Markus Deck Claudio Voodoo Daniel Smith Blindguy Morphee7		02:05.202 02:06.037 02:06.930 02:07.880
18	Virtual Drivers Alliance	GT3	02:06.631	02.153	00.118	1	2 / 2
	Michele Rizzo Armando Ortenzi		02:06.297 02:06.965
19	smol pp	GT3	02:06.681	02.204	00.050	1	3 / 3
	Thomas Jack Sebastian Björkholm Moberg		02:05.240 02:06.342 02:08.462
20	Celtic Bromance Drift Club	GT3	02:06.682	02.204	00.000	1	4 / 4
	Krab Athor Alastair Baldwin Kalimazoo Daniel Blakeman		02:06.130 02:06.335 02:06.442 02:07.822
21	NoName	GT3	02:06.765	02.287	00.082	2	1 / 2
	Brian Schekkerman		02:06.765
22	BeesWax Racing Bee Quick	GT3	02:07.041	02.564	00.276	1	3 / 3
	Marton Cynolter Dami Ayo Daan van Geloven		02:05.802 02:05.860 02:09.462
23	The Brexit Bois Purple	GT3	02:07.069	02.592	00.028	1	2 / 2
	Tommy Schets Jamie Ellis		02:06.142 02:07.997
24	Amino-Asseto Motorhersteller Amino-Asseto	GT3	02:07.166	02.689	00.096	1	3 / 3
	Furkan Hosman Safa Kelkit Berke Aras		02:06.910 02:07.242 02:07.347
25	No Time To Pee	GT3	02:07.300	02.822	00.133	1	3 / 3
	Michal Augustynek [NTTP] Artur Myszka [NTTP] Adrian Reilly		02:06.805 02:07.465 02:07.630
26	JVM Racing	GT3	02:07.311	02.834	00.011	1	3 / 3
	Javi Hernando Miguel Aguerri Víctor Fernández		02:06.772 02:07.262 02:07.900
27	Hela Gewürzketchup Racing Boom & Zoom	GT3	02:07.437	02.960	00.126	1	2 / 2
	Yannick Lautenschläger Alfred Lubich		02:07.320 02:07.555
28	Castro ESports Team	GT3	02:07.677	03.199	00.239	2	1 / 2
	Tiago Presa de Castro		02:07.677
29	HeXagon Nation Black	GT3	02:07.752	03.275	00.075	1	4 / 4
	Daniel Nilsson Oskar Motin \| HeX Casper Björk \| HeX Thomas Kinell \| HeX		02:07.107 02:07.317 02:07.745 02:08.842
30	FuzzyLlamas	GT3	02:07.834	03.356	00.081	1	4 / 4
	Lord Nem NynS Stuart Pietzka Viking Rap		02:07.510 02:07.662 02:07.957 02:08.207
31	Karimbabimba Motorsport	GT3	02:08.067	03.589	00.233	1	2 / 2
	Rikka Takanashi Harald Klöppelmann		02:07.992 02:08.142
32	HeXagon Nation White	GT3	02:08.421	03.943	00.354	1	4 / 4
	Samuel Christiansen R Matthieson \| HeX Patrik Pfeffer \| HeX Chris Jenkins \| HeX		02:06.507 02:07.247 02:09.960 02:09.970
33	SXS Racing Team Blue	GT3	02:08.733	04.255	00.312	1	3 / 3
	Liam Young Andrew Hardy Kian Dickens		02:06.622 02:09.690 02:09.887
34	Secret Scam Chads	GT3	02:09.310	04.832	00.577	1	2 / 2
	Wojciech Zarzecki Octavian Robu		02:08.460 02:10.160
35	Hyperion Racing bubblegum	GT3	02:09.395	04.917	00.085	2	1 / 2
	Craig Parsons		02:09.395
36	Snail Racing	GT3	02:09.904	05.427	00.509	1	3 / 3
	HaiCo michael lievens Darren Reynolds		02:08.677 02:09.025 02:12.012
37	Drehmoment Racing	GT3	00:00.000			5	0 / 2

38	Like and Subscribe Team	GT3	00:00.000			5	0 / 2

39	U.R.L.	GT3	00:00.000			5	0 / 2

40	Porsche Sbinnala Team	GT3	00:00.000			5	0 / 4

41	Karimbabimba Motorsport Karimbabimbois	GT3	00:00.000			5	0 / 3

Tier 1

#	Team	Driver	Time	Fastest	Laps	Gap	Class	Nr
1	SimuNation eSport SimuNation E-Sport	Filip Ślaski Patryk Lipka Kamil Panus	12:01:48.874	02:06.260	333			484
2	Yeet Gaming	Jay Fang Aider Willspin	12:02:05.564	02:06.627	333	00:16.690		117
3	Garage991	Nils Schroer Roy Momann Tobias Madl Stefan Jentzsch	12:03:33.999	02:06.505	333	01:45.125		991
4	Team Hivemind Cubed	DoR dakuza #80 Shooter80 Tim Moors	12:03:12.450	02:06.257	332	+1 Laps		729
5	smol pp	Thomas Jack Moberg Sebastian Björkholm	12:03:50.027	02:06.835	331	+2 Laps	GT3	1
6	Victorious Secret OG squad	Igor55 Rachel Konkoly Remco Langedyk	12:01:59.082	02:07.355	330	+3 Laps		55
7	Capital SimRacers	Thomas Allendorf Jay Janz	12:03:28.192	02:07.235	330	+3 Laps		16
8	Karimbabimba Motorsport	Rikka Takanashi Harald Klöppelmann	12:02:14.337	02:07.427	329	+4 Laps	GT3	21
9	2 sec off pace	Michal Balicki Jerzy Wawrzyczek Pawel Jarzebowski	12:02:21.426	02:07.230	329	+4 Laps	GT3	26
10	Celtic Bromance NoGrip.exe	Kiki Mac Kristers Podēns Dan Barnard Josh Waring	12:03:02.461	02:06.475	329	+4 Laps		177
11	Hela Gewürzketchup Racing Boom & Zoom	Yannick Lautenschläger Alfred Lubich	12:03:11.623	02:07.632	329	+4 Laps		77
12	RPMS SimSport	Daniel Crinson Richard Phillips[RPMS] Matt Stevens[RPMS]	12:03:24.946	02:07.460	329	+4 Laps	GT3	707
13	BeesWax Racing Bee Quick	Marton Cynolter Dami Ayo Daan van Geloven	12:04:22.262	02:07.290	329	+4 Laps		451
14	The Brexit Bois Purple	Jamie Ellis Tommy Schets	12:02:08.266	02:07.207	328	+5 Laps	GT3	88
15	BeesWax Racing DT Crew	Kulakov Eugene Chris Saybia The Lazy-Badger	12:03:01.672	02:06.065	328	+5 Laps		888
16	CRACKD.Racing	Jamie Nuttall Derrick Son Attila Kodé Jordan Woodley	12:02:36.210	02:05.840	327	+6 Laps		420
17	No Time To Pee	Michal Augustynek [NTTP] Adrian Reilly Artur Myszka [NTTP]	12:02:04.394	02:07.802	326	+7 Laps		340
18	Amino-Asseto Motorhersteller Amino-Asseto	Berke Aras Furkan Hosman Safa Kelkit	12:02:44.042	02:07.722	326	+7 Laps		28
19	Celtic Bromance Drift Club	Alastair Baldwin Kalimazoo Krab Athor Daniel Blakeman	12:02:04.577	02:07.867	325	+8 Laps		27
20	Team Hivemind Grumpy Old Farts	Claudio Voodoo Daniel Smith Blindguy Morphee7 Markus Deck	12:02:05.161	02:07.397	324	+9 Laps		728
21	SXS Racing Team Blue	Liam Young Andrew Hardy Kian Dickens	12:03:06.718	02:07.070	324	+9 Laps		44
22	FuzzyLlamas	Viking Rap Lord Nem NynS Stuart Pietzka	12:02:58.212	02:08.005	323	+10 Laps	GT3	69
23	HeXagon Nation Black	Daniel Nilsson Thomas Kinell \| HeX Casper Björk \| HeX Oskar Motin \| HeX	12:02:58.572	02:08.240	323	+10 Laps		114
24	HeXagon Nation White	R Matthieson \| HeX Samuel Christiansen Chris Jenkins \| HeX Patrik Pfeffer \| HeX	12:03:17.098	02:08.177	321	+12 Laps	GT3	10
25	Snail Racing	michael lievens HaiCo Darren Reynolds	12:02:17.409	02:07.722	315	+18 Laps	GT3	76
26	LeMans RennSport	Tommy Lyden Vuksan Videnovic Predrag Jevremovic	08:02:51.850	02:05.885	222	+111 Laps		2
27	Virtual Drivers Alliance	Michele Rizzo Armando Ortenzi	06:50:47.596	02:07.375	188	+145 Laps	GT3	115
28	Secret Scam Chads	Wojciech Zarzecki Octavian Robu	06:57:27.097	02:08.020	185	+148 Laps	GT3	360
29	RevolutionSimRacing	Jason Dyer Corne Borchers	06:34:55.036	02:06.685	180	+153 Laps	GT3	33
30	JVM Racing	Javi Hernando Miguel Aguerri Víctor Fernández	05:06:20.572	02:08.317	137	+196 Laps	GT3	478
31	Kúpteam FuturEsportS #1	Máté Mezőffy Feri Danics Bence Fazekas Bence Szilagyi	02:08:26.609	02:07.040	59	+274 Laps	GT3	333
32	Castro ESports Team	Tiago Presa de Castro Afonso Souto	01:00:24.642	02:08.732	27	+306 Laps	GT3	25
33	NoName	Sem Smeets Brian Schekkerman	00:57:31.339	02:08.097	23	+310 Laps	GT3	95