Map › Slovakia in the European stack
How international, EU and Slovak rules combine from technical approval to road deployment. Position as of 2026-08-27.
| Regulatory question | UNECE and international | European Union | Slovakia | Practical effect |
|---|---|---|---|---|
| Who or what may drive? operation | Vienna Convention 1968, Article 8(5 bis) and Article 34 bis | The EU technical framework does not comprehensively replace national traffic-law rules | Act No. 8/2009 Coll. on road traffic; the parliamentary print 1329 reform track | Technical legality of the system must still fit road-traffic rules and the allocation of actors. |
| Can the vehicle or the system be approved? type approval | UN R157; the new UN ADS Regulation; the ADS GTR | Regulation 2018/858; Regulation 2019/2144; Regulation 2022/1426; Regulation 2026/481 | Act No. 106/2018 Coll. carries the national approval and vehicle-operation interfaces | EU and UNECE approval can establish technical compliance, but it does not itself create a right to operate commercially. |
| Can it be tested on public roads? operation | NATM informs the safety evidence; WP.1 supplies the traffic-law context | EU type-approval rules influence the evidence, but access for testing remains largely national | Act No. 106/2018 Coll. § 49 test operation; the Act No. 131/2026 amendment effective 1 September 2026 | A separate Slovak test-operation permission remains the gateway for non-standard testing on public roads. |
| Who may operate and supervise it? operation | UNECE work on remote intervention and interaction; remote-driving papers | Regulation 2022/1426 with JRC guidance addresses remote management inside the approval context | The current Slovak framework and the proposed print 1329: operator, control centre, supervision operator | Operational roles need a national legal allocation even where the system is technically approved. |
| What data and cyber rules apply? approval and operation | UN R155; UN R156; UN R160 | GDPR; Data Act; NIS2; Cybersecurity Act; event-data rules; the AI Act where applicable | Slovak implementation of GDPR and NIS2 with sectoral enforcement | Vehicle approval, operator governance and data or cyber compliance overlap rather than substitute for one another. |
| Can it provide a commercial service? operation | There is no complete global service-licensing regime | Internal-market, transport and consumer rules may apply; there is no single EU licence for an automated-vehicle service | Road transport and service law, plus a future specific operational framework | Commercial use needs a second legal layer beyond type approval and test operation. |
| What happens after deployment? approval and operation | UN R155 and R156; the emerging in-service framework for automated driving systems | Regulation 2022/1426 in-service monitoring; market surveillance; product-liability and data rules | Police and incident powers, administrative supervision, sanctions, recall and operating restrictions | Approval becomes a continuous lifecycle obligation, not a one-off certificate. |
The same seven questions run through the decision tree; Module 02 codes the Slovak deployment gate against seven other regimes in Second Gate.
Provenance
ROAT Regulatory Map 2026 – Reconstructed Draft v0.7.1 (PraF UK), sheet "Slovakia EU Stack", cut-off 2026-08-27. Orientation table. Module 02 codes the Slovak deployment gate against seven other regimes; the Slovak reform track is followed as parliamentary print 1329.