BIZTRAC BETA
Rental and operating of own or leased real estate

NAA EIENDOM AS

Org. no. 925559237 Limited company (AS) Ullensvang Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 623,000
Equity NOK 1.6m
Incorporated 2020
Share capital NOK 100,000

Signals

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

NAA EIENDOM AS is registered as a limited company in Ullensvang, Vestland with organisation number 925559237. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie og drift av fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 623,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 623,000
Equity
NOK 1.6m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns NAA EIENDOM AS?

NAA HOLDING AS
NAA EIENDOM AS
NOK 1.6m rev. · NOK 623,000 profit

NAA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NAA EIENDOM AS

Who owns NAA EIENDOM AS?

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

What is the revenue of NAA EIENDOM AS?

NAA EIENDOM AS had revenue of NOK 1.6m in 2025.

Who is the general manager of NAA EIENDOM AS?

Daniel Olason Naa is registered as general manager of NAA EIENDOM AS.

Where is NAA EIENDOM AS based?

NAA EIENDOM AS has its business address in Nå.

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.