BIZTRAC BETA
Repair and maintenance of motor vehicles

KM AUTO HEIMDAL AS

Org. no. 924629878 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 70,000
Equity NOK 15,000
Incorporated 2020
Share capital NOK 30,000

KM AUTO HEIMDAL AS is registered as a limited company in Trondheim, Trøndelag with organisation number 924629878. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Biloppretting, billakkering og bilverksted.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 70,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 70,000
Equity
NOK 15,000
Est. value
NOK 272,000

Financial health · 2024

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

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

Who owns KM AUTO HEIMDAL AS?

KETIL UTHAUG
KM AUTO HEIMDAL AS
NOK 1.9m rev. · NOK 70,000 profit

KM AUTO HEIMDAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KM AUTO HEIMDAL AS own?

KM AUTO HEIMDAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KM AUTO HEIMDAL AS

Who owns KM AUTO HEIMDAL AS?

KETIL UTHAUG is the largest registered owner, with 100.0%.

What is the revenue of KM AUTO HEIMDAL AS?

KM AUTO HEIMDAL AS had revenue of NOK 1.9m in 2024.

Who is the general manager of KM AUTO HEIMDAL AS?

Ketil Uthaug is registered as general manager of KM AUTO HEIMDAL AS.

Where is KM AUTO HEIMDAL AS based?

KM AUTO HEIMDAL AS has its business address in Heimdal.

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.