BIZTRAC BETA
Development of building projects

DIN BOLIG AS

Org. no. 988973424 Limited company (AS) Ørsta Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 154.2m
Operating profit NOK 17.7m
Equity NOK 240.0m
Incorporated 2005
Employees 5
Share capital NOK 2.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

DIN BOLIG AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 988973424. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2005 and has 5 registered employees. Registered share capital is NOK 2.0m, divided into 2000 shares. The company's stated purpose is: “Oppføring og kjøp av bustader for utleige og sal. Selskapet skal kunne delta i andre verksemder med liknande føremål.”. The most recent filed accounts, for the 2024 financial year, show NOK 154.2m in revenue and NOK 17.7m in operating profit.

Key figures · 2024

Revenue
NOK 154.2m
Operating profit
NOK 17.7m
Equity
NOK 240.0m
Est. value
NOK 215.3m

Financial health · 2024

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

Who owns DIN BOLIG AS?

EIKEN HOLDING AS
DIN BOLIG AS
NOK 154.2m rev. · NOK 17.7m profit

DIN BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIN BOLIG AS

Who owns DIN BOLIG AS?

EIKEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DIN BOLIG AS?

DIN BOLIG AS had revenue of NOK 154.2m in 2024.

Who is the general manager of DIN BOLIG AS?

Roar Eiken is registered as general manager of DIN BOLIG AS.

Where is DIN BOLIG AS based?

DIN BOLIG AS has its business address in Ørsta.

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.