BIZTRAC BETA
Other captive investment companies

DYRSTAD-INVEST AS

Org. no. 997811461 Limited company (AS) Lindesnes Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −12,000
Equity NOK 1.4m
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−12k kr).

DYRSTAD-INVEST AS is registered as a limited company in Lindesnes, Agder with organisation number 997811461. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å eie aksjer og andeler i andre selskaper, investere i og utvikle eiendom, samt det som står i forbindelse med dette, og i tillegg drive med konsulentvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 1.4m
Est. value
NOK 871,000

Financial health · 2025

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

Who owns DYRSTAD-INVEST AS?

THORSTEIN DYRSTAD
DYRSTAD-INVEST AS
NOK 0 rev. · NOK −12,000 profit

DYRSTAD-INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DYRSTAD-INVEST AS own?

DYRSTAD-INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about DYRSTAD-INVEST AS

Who owns DYRSTAD-INVEST AS?

THORSTEIN DYRSTAD is the largest registered owner, with 100.0%.

What is the revenue of DYRSTAD-INVEST AS?

DYRSTAD-INVEST AS had revenue of NOK 0 in 2024.

Where is DYRSTAD-INVEST AS based?

DYRSTAD-INVEST AS has its business address in Mandal.

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.