BIZTRAC BETA
Other captive investment companies

ØDEGÅRD HOLDING 1 AS

Org. no. 918713689 Limited company (AS) Frogn Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 60,000
Operating profit NOK 2,000
Equity NOK 13.8m
Incorporated 2016
Share capital NOK 38,000

ØDEGÅRD HOLDING 1 AS is registered as a limited company in Frogn, Akershus with organisation number 918713689. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 38,000, divided into 15 shares. The company's stated purpose is: “Investeringsselskap, herunder investeringer i aksjer, andeler i selskap etter selskapsloven og utenlandske selskaper, obligasjoner, fast eiendom og annet som står i naturlig forbindelse til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 60,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2024

Revenue
NOK 60,000
Operating profit
NOK 2,000
Equity
NOK 13.8m
Est. value
NOK 7.6m

Financial health · 2024

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

Who owns ØDEGÅRD HOLDING 1 AS?

STIAN ØDEGÅRD
ØDEGÅRD HOLDING 1 AS
NOK 60,000 rev. · NOK 2,000 profit

ØDEGÅRD HOLDING 1 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØDEGÅRD HOLDING 1 AS own?

ØDEGÅRD HOLDING 1 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØDEGÅRD HOLDING 1 AS

Who owns ØDEGÅRD HOLDING 1 AS?

STIAN ØDEGÅRD is the largest registered owner, with 100.0%.

What is the revenue of ØDEGÅRD HOLDING 1 AS?

ØDEGÅRD HOLDING 1 AS had revenue of NOK 60,000 in 2024.

Where is ØDEGÅRD HOLDING 1 AS based?

ØDEGÅRD HOLDING 1 AS has its business address in Drøbak.

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.