BIZTRAC BETA
Development of building projects

ODIN INVESTERING AS

Org. no. 986720502 Limited company (AS) Bergen Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 656,000
Operating profit NOK −721,000
Equity NOK −22.6m
Incorporated 2003
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−22,6 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−721k kr).

ODIN INVESTERING AS is registered as a limited company in Bergen, Vestland with organisation number 986720502. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2003. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i fast eiendom, aksjer, verdipapirer og finansielle instrumenter, samt alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 656,000 in revenue and NOK −721,000 in operating profit.

Key figures · 2024

Revenue
NOK 656,000
Operating profit
NOK −721,000
Equity
NOK −22.6m

Financial health · 2024

Liquidity
3.79
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-89.3%
Weak
Equity as a share of total capital

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

Who owns ODIN INVESTERING AS?

HAUGLAND GRUPPEN AS
ODIN INVESTERING AS
NOK 656,000 rev. · NOK −721,000 profit

ODIN INVESTERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ODIN INVESTERING AS

Who owns ODIN INVESTERING AS?

HAUGLAND GRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of ODIN INVESTERING AS?

ODIN INVESTERING AS had revenue of NOK 656,000 in 2024.

Where is ODIN INVESTERING AS based?

ODIN INVESTERING AS has its business address in Bergen.

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.