BIZTRAC BETA
Architectural activities

DOMAAS AS

Org. no. 920658458 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 49,000
Operating profit NOK −13,000
Equity NOK 622,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

DOMAAS AS is registered as a limited company in Oslo, Oslo with organisation number 920658458. The business is classified under architectural activities (NACE 71.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “å levere tjenester innen arkitektur og kunst, samt andre tjenester/produkter som naturlig faller sammen med dette, herunder å 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.”. The most recent filed accounts, for the 2024 financial year, show NOK 49,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 49,000
Operating profit
NOK −13,000
Equity
NOK 622,000
Est. value
NOK 340,000

Financial health · 2024

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

Who owns DOMAAS AS?

KAREN NISJA DOMAAS
DOMAAS AS
NOK 49,000 rev. · NOK −13,000 profit

DOMAAS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DOMAAS AS

Who owns DOMAAS AS?

KAREN NISJA DOMAAS is the largest registered owner, with 50.0%.

What is the revenue of DOMAAS AS?

DOMAAS AS had revenue of NOK 49,000 in 2024.

Who is the general manager of DOMAAS AS?

Stein Domaas is registered as general manager of DOMAAS AS.

Where is DOMAAS AS based?

DOMAAS AS has its business address in Oslo.

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.