BIZTRAC BETA
Repair and maintenance of motor vehicles

AUTOEXPERTEN KIRKENÆR AS

Org. no. 920286321 Limited company (AS) Grue Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 5.8m
Operating profit NOK 773,000
Equity NOK 1.2m
Incorporated 2018
Share capital NOK 100,000

AUTOEXPERTEN KIRKENÆR AS is registered as a limited company in Grue, Innlandet with organisation number 920286321. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av bilverksted og reparasjon og vedlikehold av motorkjøretøyer samt beslektet virksomhet forøvrig.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.8m in revenue and NOK 773,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.8m
Operating profit
NOK 773,000
Equity
NOK 1.2m
Est. value
NOK 3.4m

Financial health · 2024

Liquidity
2.45
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.6%
Very good
Equity as a share of total capital

Who owns AUTOEXPERTEN KIRKENÆR AS?

ALINA REBECCA HAUG DRAZKOWSKI
AUTOEXPERTEN KIRKENÆR AS
NOK 5.8m rev. · NOK 773,000 profit

AUTOEXPERTEN KIRKENÆR AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about AUTOEXPERTEN KIRKENÆR AS

Who owns AUTOEXPERTEN KIRKENÆR AS?

ALINA REBECCA HAUG DRAZKOWSKI is the largest registered owner, with 38.0%.

What is the revenue of AUTOEXPERTEN KIRKENÆR AS?

AUTOEXPERTEN KIRKENÆR AS had revenue of NOK 5.8m in 2024.

Who is the general manager of AUTOEXPERTEN KIRKENÆR AS?

Kenneth Tveter Sunde Skoglund is registered as general manager of AUTOEXPERTEN KIRKENÆR AS.

Where is AUTOEXPERTEN KIRKENÆR AS based?

AUTOEXPERTEN KIRKENÆR AS has its business address in Kirkenær.

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.