Skip to content
ROAT — Regulation of Automated TransportROAT — Regulation of Automated Transport

Jurisdictions › Croatia

ROAT-JUR-HR

Croatia

Last verified 2026-09-05 (JA)Authorities Transport and road authorities · Licensing authority under the national transport framework

Croatia combines EU ADS type approval with dedicated road-traffic rules, owner responsibility for offences in driverless operation, recognised remote-intervention arrangements and a mandatory real-world service validation on a registered sample vehicle before passenger service — a deployment-assurance gate of the service-test variant.

Road Traffic Safety Act amendments (NN 145/2024) and Road Transport Act amendments (NN 154/2024) in force.

In Module 01 · snapshot 2026-08-25 review snapshot

Regulatory normalisation by functional layer

RegimeTechnical approvalRoad access / operationActor allocationLiability / riskBehavioural rulesInfrastructureInternational / cross-borderRange · asynchronyConfiguration family
CroatiaMandatory real-world service validation on a registered sample vehicle before passenger serviceN3N3N3N2N3N2N21 · MildDeployment-assurance configuration – service-test variant

Croatia Deployment-assurance configuration – service-test variant

Technical approval
N3 — Dedicated institutionalisation
Road access / operation
N3 — Dedicated institutionalisation
Actor allocation
N3 — Dedicated institutionalisation
Liability / risk
N2 — Bridge-based integration
Behavioural rules
N3 — Dedicated institutionalisation
Infrastructure
N2 — Bridge-based integration
International / cross-border
N2 — Bridge-based integration
Primary current-law rationale
Croatia combines EU technical approval with dedicated road-traffic rules, remote/intervention actors, owner enforcement duties and a mandatory service-level real-world validation procedure before public passenger transport.
Dominant legal bridge / gate
Mandatory real-world service validation on a registered sample vehicle before passenger service
Sensitivity range
Liability N2–N3; infrastructure N1–N2; international N2–N3.
Robust conclusion
Deployment-assurance configuration remains robust under conservative recoding.
Important caveat
Civil liability and quantitative retesting/change-control rules remain less clear than traffic-offence and service-assurance rules.
Confidence
High
Core ROAT records
ROAT-2026-0262ROAT-2026-0303ROAT-2026-0304ROAT-2026-0305
N0Unintegrated / exceptional
N1Ad hoc or conditional accommodation
N2Bridge-based integration
N3Dedicated institutionalisation
N4Routinisation / mainstream recognition

In Module 02 · snapshot 2026-09-07 review snapshot

Post-type-approval deployment models

RegimeDeployment gateRemote human roleDominant deployment modelLegal statusConfidence
Croatia – current lawDedicated road-traffic rules plus mandatory real-world service validation before passenger-service deploymentRemote intervention role recognised; boundaries and concurrency remain implementation questionsOwner-centred deployment-validation modelIn forceHigh

Croatia – current law

Regulatory object
Fully automated vehicle + owner + operating area + transport service + remote intervention arrangements
Technical approval baseline
EU ADS type approval
Additional deployment / road-use gate
Dedicated road-traffic rules plus mandatory real-world service validation before passenger-service deployment
ODD / operating-area legalisation
Operating area / territory forms part of deployment validation and service conditions
Competent authority / decision maker
Transport/road authorities; licensing authority under national transport framework
Primary accountable organisational actor
Vehicle owner is a central road-traffic accountability actor; service operator duties exist at transport layer
Remote human role
Remote intervention role recognised; boundaries and concurrency remain implementation questions
DDT / fallback allocation
ADS performs driverless operation; remote intervention supports defined operational/safety functions
Traffic-offence allocation
Owner bears dedicated responsibility for traffic offences of fully automated vehicle in driverless operation
Civil liability / insurance
Traffic-offence allocation is clear; broader AV-specific civil-liability architecture is less complete
Data / logging
Strong telemetry/event-data access and video-surveillance duties
Post-market / in-use oversight
Service/deployment oversight, incident management and licence conditions
Material change / software update
Partial change-control only: a new special-conditions certificate is required within 15 days if certificate data change; general testing applies to converted/modified vehicle hardware under Road Safety Act Art 276.
Retesting / revalidation
No equally explicit rule located that a material ADS/ODD/software/service change automatically re-triggers the Art 13b–13d real-world service-validation procedure. Serious incidents can trigger temporary prohibition of a FAV type under Art 290a.
Commercial service pathway
Yes, through transport licensing after service-level real-world validation
Dominant deployment model
Owner-centred deployment-validation model
Legal status
In force
Primary-source anchor
NN 145/2024 Arts 281a–281f; NN 154/2024 Arts 13b–13d / Art 51a framework
Primary current-law rationale
Croatia is especially useful for the bridge from EU type approval to local service validation in real operating conditions.
Confidence
High
Core ROAT records
ROAT-2026-0262ROAT-2026-0303ROAT-2026-0304ROAT-2026-0305

Sources

Public Library records for Croatia

ROAT-2026-0303
Act amending the Road Traffic Safety Act, NN 145/2024 (Zakon o izmjenama i dopunama Zakona o sigurnosti prometa na cestama)
ROAT-2026-0305
Act amending the Road Transport Act, NN 77/2026 (Zakon o izmjenama i dopunama Zakona o prijevozu u cestovnom prometu)
ROAT-2026-0304
Ordinance amending the Ordinance on special conditions for vehicles used in public road transport and own-account transport, NN 154/2024 (Pravilnik o izmjenama i dopunama Pravilnika o posebnim uvjetima za vozila kojima se obavlja javni cestovni prijevoz i prijevoz za vlastite potrebe)