biztrac. BETA
COMPANY REGISTER PROFILE
930122386 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Retail sale of motor vehicles

BILEXPORT AS

Org. no. 930122386 Limited company (AS) Overhalla Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 16.3m
Operating profit NOK 164,000
Equity NOK 353,000
Incorporated 2022
Share capital NOK 30,000

BILEXPORT AS is registered as a limited company in Overhalla, Trøndelag with organisation number 930122386. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp, salg samt import og eksport av brukte biler og bildeler og bilpleie og dekkshifte og andre produkter og tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på en annen måte gjøre seg interessant i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 16.3m in revenue and NOK 164,000 in operating profit.

Key figures · 2025

Revenue
NOK 16.3m
▲ +3 %
Operating profit
NOK 164,000
▲ +114 %
Equity
NOK 353,000
▼ −35 %
Est. value
NOK 212,000

Financial health · 2025

Liquidity
2.93
Very good
Current assets ÷ current liabilities
Profitability
17.1%
Very good
Return on total assets
Solidity
40.0%
Good
Equity as a share of total capital

Who owns BILEXPORT AS?

BILEXPORT AS
NOK 16.3m rev. · NOK 164,000 profit

BILEXPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BILEXPORT AS

Who owns BILEXPORT AS?

Kyrylo Slukhov is the largest registered owner, with 100.0%.

What is the revenue of BILEXPORT AS?

BILEXPORT AS had revenue of NOK 16.3m in 2025.

Where is BILEXPORT AS based?

BILEXPORT AS has its business address in Overhalla.

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

Report a problem

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