BIZTRAC BETA
Wholesale of motor vehicles

BUSSEXPERTEN AS

Org. no. 897499282 Limited company (AS) Aurskog-Høland Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 17.7m
Operating profit NOK 1.1m
Equity NOK 1.8m
Incorporated 2011
Share capital NOK 1.8m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BUSSEXPERTEN AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 897499282. The business is classified under wholesale of motor vehicles (NACE 46.710). The company was incorporated in 2011. Registered share capital is NOK 1.8m, divided into 1000 shares. The company's stated purpose is: “Renovering og oppussing av kjøretøy, samt det som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.7m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 17.7m
Operating profit
NOK 1.1m
Equity
NOK 1.8m
Est. value
NOK 4.1m

Financial health · 2024

Liquidity
1.53
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.2%
Satisfactory
Equity as a share of total capital

Who owns BUSSEXPERTEN AS?

FOSSER INVEST AS
BUSSEXPERTEN AS
NOK 17.7m rev. · NOK 1.1m profit

BUSSEXPERTEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BUSSEXPERTEN AS

Who owns BUSSEXPERTEN AS?

FOSSER INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BUSSEXPERTEN AS?

BUSSEXPERTEN AS had revenue of NOK 17.7m in 2024.

Who is the general manager of BUSSEXPERTEN AS?

Espen Husvik is registered as general manager of BUSSEXPERTEN AS.

Where is BUSSEXPERTEN AS based?

BUSSEXPERTEN AS has its business address in Fosser.

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.