biztrac. BETA
COMPANY REGISTER PROFILE
999529259 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other construction installation

ODD MAGNE AASHEIM AS

Org. no. 999529259 Limited company (AS) Kristiansand Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 48,000
Equity NOK 314,000
Incorporated 2013
Share capital NOK 30,000

ODD MAGNE AASHEIM AS is registered as a limited company in Kristiansand, Agder with organisation number 999529259. The business is classified under other construction installation (NACE 43.240). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg og momntering av solskjerming, samt montering og reparasjon av vedovner.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 48,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▲ +17 %
Operating profit
NOK 48,000
▲ +258 %
Equity
NOK 314,000
▲ +10 %
Est. value
NOK 259,000

Financial health · 2025

Liquidity
1.94
Good
Current assets ÷ current liabilities
Profitability
7.6%
Satisfactory
Return on total assets
Solidity
49.1%
Very good
Equity as a share of total capital

Who owns ODD MAGNE AASHEIM AS?

ODD MAGNE AASHEIM AS
NOK 2.7m rev. · NOK 48,000 profit

ODD MAGNE AASHEIM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ODD MAGNE AASHEIM AS

Who owns ODD MAGNE AASHEIM AS?

Odd Magne Aasheim is the largest registered owner, with 100.0%.

What is the revenue of ODD MAGNE AASHEIM AS?

ODD MAGNE AASHEIM AS had revenue of NOK 2.7m in 2025.

Who is the general manager of ODD MAGNE AASHEIM AS?

Odd Magne Aasheim is registered as general manager of ODD MAGNE AASHEIM AS.

Where is ODD MAGNE AASHEIM AS based?

ODD MAGNE AASHEIM AS has its business address in Kristiansand S.

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.