BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

NAA HOLDING AS

Org. no. 820238222 Limited company (AS) Ullensvang Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 130,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

NAA HOLDING AS is registered as a limited company in Ullensvang, Vestland with organisation number 820238222. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investere i andre selskaper og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −7,000
Equity
NOK 130,000
Est. value
NOK 208,000

Financial health · 2024

Liquidity
0.41
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.4%
Good
Equity as a share of total capital

Who owns NAA HOLDING AS?

DANIEL OLASON NAA
NAA HOLDING AS
· NOK −7,000 profit

NAA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NAA HOLDING AS own?

NAA HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NAA HOLDING AS

Who owns NAA HOLDING AS?

DANIEL OLASON NAA is the largest registered owner, with 100.0%.

Who is the general manager of NAA HOLDING AS?

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

Where is NAA HOLDING AS based?

NAA HOLDING 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.