BIZTRAC BETA
Uoppgitt

NERETUNET HOLDING AS

Org. no. 931670239 Limited company (AS) Gloppen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 17.5m
Incorporated 2023
Share capital NOK 30,000

Signals

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

NERETUNET HOLDING AS is registered as a limited company in Gloppen, Vestland with organisation number 931670239. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper og eventuelt eiendom, samt forvalte eierinteressen av disse. Selskapet skal også kunne forestå administrative tjenester for andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −13,000
Equity
NOK 17.5m
Est. value
NOK 37.4m

Financial health · 2025

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

Who owns NERETUNET HOLDING AS?

PER KANDAL
NERETUNET HOLDING AS
NOK 0 rev. · NOK −13,000 profit

NERETUNET HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NERETUNET HOLDING AS own?

NERETUNET HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NERETUNET HOLDING AS

Who owns NERETUNET HOLDING AS?

PER KANDAL is the largest registered owner, with 100.0%.

What is the revenue of NERETUNET HOLDING AS?

NERETUNET HOLDING AS had revenue of NOK 0 in 2025.

Where is NERETUNET HOLDING AS based?

NERETUNET HOLDING AS has its business address in Sandane.

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.