BIZTRAC BETA
Education at authorised driving schools

BORG TRAFIKKSKOLE AS

Org. no. 921605781 Limited company (AS) Sarpsborg Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 6.7m
Operating profit NOK 67,000
Equity NOK 59,000
Incorporated 2018
Employees 5
Share capital NOK 30,000

BORG TRAFIKKSKOLE AS is registered as a limited company in Sarpsborg, Østfold with organisation number 921605781. The business is classified under education at authorised driving schools (NACE 85.531). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Trafikkopplæring og annen trafikksikkerhetsrelatert virksomhet, samt transportoppdrag for gods og personer.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.7m in revenue and NOK 67,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.7m
Operating profit
NOK 67,000
Equity
NOK 59,000
Est. value
NOK 261,000

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
2.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BORG TRAFIKKSKOLE AS?

ZO HOLDING AS
BORG TRAFIKKSKOLE AS
NOK 6.7m rev. · NOK 67,000 profit

BORG TRAFIKKSKOLE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BORG TRAFIKKSKOLE AS

Who owns BORG TRAFIKKSKOLE AS?

ZO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BORG TRAFIKKSKOLE AS?

BORG TRAFIKKSKOLE AS had revenue of NOK 6.7m in 2025.

Who is the general manager of BORG TRAFIKKSKOLE AS?

Zarif Okanovic is registered as general manager of BORG TRAFIKKSKOLE AS.

Where is BORG TRAFIKKSKOLE AS based?

BORG TRAFIKKSKOLE AS has its business address in Sarpsborg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.