Police vehicles should be selected for the incident role, not simply for maximum speed. Patrol, traffic work, pursuits, suspect transport, and specialized response place different demands on handling, seating, equipment, and scene access. The current police garage determines which models and branches your account can use.
Choose a fleet role
Check access before spawning
Join the police team through the current station, select the branch or role, and inspect the garage. Job experience or other requirements can control vehicle access. A locked model is a progression target; do not rely on an old unlock number when the current screen is available.
Update V3.16 added vehicles and a new police station, so screenshots recorded before it may show an outdated fleet or spawn flow.
Patrol setup
Choose a vehicle you can place accurately at stops and scenes. Learn the station exit, normal braking distance, and the route to the prison or completion waypoint. Confirm that the vehicle supports any required transport before initiating an arrest sequence.
Keep equipment decisions separate from the vehicle’s appearance. The police equipment guide explains tool roles, while the police job guide covers the full incident and detention loop.
Pursuit driving
Spacing
Preserve reaction time
Follow far enough back to brake for sudden turns and collisions. Crowding the target can disable both vehicles.
Coordination
Use more than one route
Additional units can cover likely exits instead of stacking on the same bumper.
Control
Slow before intersections
Emergency lights do not remove cross traffic or shorten the vehicle's actual stopping distance.
If contact or road equipment is part of the current rules, use it only where the game and server permit. Avoid turning routine roleplay into repeated vehicle damage.
Scene placement
Park where the vehicle supports the objective while preserving fire, HARS, and traffic access. At a detention, allow room for doors and transport. At a road incident, use warning equipment and create a visible work zone without sealing the entire map route.
Comparing fleet options
Test available vehicles on the same short route with the same input method. Note braking, corner stability, visibility, size, seating, and equipment access. Do not publish inferred speed or acceleration values as facts when the game does not show or support them.
The maintained vehicle catalog helps identify the current fleet structure, and the Police reference explains job context. Use the live police garage for models, branch access, requirements, and current performance.
Fleet test record
For each available model, note the current garage name, branch, unlock or access state, seats, supported police role, equipment context, handling on a fixed route, and check date. Do not convert a pursuit impression into exact speed or acceleration data.
Test parking at the station, a normal traffic stop, and the prison or completion waypoint. A useful patrol vehicle must fit the entire job loop, not only the open road.
Missing or locked vehicle
Confirm the current police branch, job experience, product access, and garage filter. Update-era fleet changes can move a model or change its requirement. If the interface shows a lock, record the live requirement; if it shows no model, rejoin once before reporting removal.
At a scene, switch vehicles only when the current one cannot perform the role. Spawning several options for comparison can block headquarters and consume server resources.
Record any branch-specific equipment or transport limitation separately from speed and handling.
Recheck station exits and prison access after a map update, because route fit is part of a useful patrol-vehicle decision.