BIZTRAC BETA
Uoppgitt

NAP HOLDING AS

Org. no. 935656966 Limited company (AS) Klepp Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 0
Operating profit NOK −500
Equity NOK 37,000
Incorporated 2025
Share capital NOK 500,000

Signals

2 flags
  • Driftsunderskudd Siste driftsresultat er negativt (−500 kr).
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

NAP HOLDING AS is registered as a limited company in Klepp, Rogaland with organisation number 935656966. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 500,000, divided into 10 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder kjøp og salg av aksjer og andeler i andre selskapet, samt annen virksomhet som naturlig hører med i denne forbindelse.”.

Key figures

Revenue
NOK 0
Operating profit
NOK −500
Equity
NOK 37,000
Est. value
NOK 43,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns NAP HOLDING AS?

MARTIN NAPIERALA
NAP HOLDING AS
NOK 0 rev. · NOK −500 profit

NAP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NAP HOLDING AS own?

NAP HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NAP HOLDING AS

Who owns NAP HOLDING AS?

MARTIN NAPIERALA is the largest registered owner, with 100.0%.

What is the revenue of NAP HOLDING AS?

NAP HOLDING AS had revenue of NOK 0.

Who is the general manager of NAP HOLDING AS?

Martin Napierala is registered as general manager of NAP HOLDING AS.

Where is NAP HOLDING AS based?

NAP HOLDING AS has its business address in Bryne.

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.