BIZTRAC BETA
Rental and operating of own or leased real estate

DAG ERLAND OLSEN AS

Org. no. 998906059 Limited company (AS) Gjøvik Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −23,000
Equity NOK 7.0m
Incorporated 2012
Share capital NOK 1.1m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

DAG ERLAND OLSEN AS is registered as a limited company in Gjøvik, Innlandet with organisation number 998906059. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 1.1m, divided into 3000 shares. The company's stated purpose is: “Å eie eiendom og aksjer i andre selskap. Selskapet vil også kunne delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”.

Key figures · 2024

Operating profit
NOK −23,000
Equity
NOK 7.0m
Est. value
NOK 9.9m

Financial health · 2024

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

Who owns DAG ERLAND OLSEN AS?

DAG ERLAND OLSEN
DAG ERLAND OLSEN AS
· NOK −23,000 profit

DAG ERLAND OLSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DAG ERLAND OLSEN AS own?

DAG ERLAND OLSEN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about DAG ERLAND OLSEN AS

Who owns DAG ERLAND OLSEN AS?

DAG ERLAND OLSEN is the largest registered owner, with 100.0%.

Where is DAG ERLAND OLSEN AS based?

DAG ERLAND OLSEN AS has its business address in Hunndalen.

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.