BIZTRAC BETA
Miscellaneous vehicular training excluding authorised driving schools

KO-LK TRAFIKKOPPLÆRING AS

Org. no. 930067938 Limited company (AS) Asker Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 42,000
Equity NOK 159,000
Incorporated 2022
Share capital NOK 30,000

KO-LK TRAFIKKOPPLÆRING AS is registered as a limited company in Asker, Akershus with organisation number 930067938. The business is classified under miscellaneous vehicular training excluding authorised driving schools (NACE 85.532). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Konsulenttjeneste for trafikkskoler.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 42,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 42,000
Equity
NOK 159,000
Est. value
NOK 273,000

Financial health · 2025

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

Who owns KO-LK TRAFIKKOPPLÆRING AS?

EIRIK LE SIMENSEN
KO-LK TRAFIKKOPPLÆRING AS
NOK 1.6m rev. · NOK 42,000 profit

KO-LK TRAFIKKOPPLÆRING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KO-LK TRAFIKKOPPLÆRING AS

Who owns KO-LK TRAFIKKOPPLÆRING AS?

EIRIK LE SIMENSEN is the largest registered owner, with 53.3%.

What is the revenue of KO-LK TRAFIKKOPPLÆRING AS?

KO-LK TRAFIKKOPPLÆRING AS had revenue of NOK 1.6m in 2025.

Who is the general manager of KO-LK TRAFIKKOPPLÆRING AS?

Eirik Le Simensen is registered as general manager of KO-LK TRAFIKKOPPLÆRING AS.

Where is KO-LK TRAFIKKOPPLÆRING AS based?

KO-LK TRAFIKKOPPLÆRING AS has its business address in Hyggen.

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.