BIZTRAC BETA
Plumbing installation

NANNESTAD VVS AS

Org. no. 926145290 Limited company (AS) Nannestad Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 17.7m
Operating profit NOK 658,000
Equity NOK 822,000
Incorporated 2020
Share capital NOK 30,000

NANNESTAD VVS AS is registered as a limited company in Nannestad, Akershus with organisation number 926145290. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Rørleggervirksomhet. Selskapet kan også drive med kjøp, salg og utleie av maskiner.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.7m in revenue and NOK 658,000 in operating profit.

Key figures · 2024

Revenue
NOK 17.7m
Operating profit
NOK 658,000
Equity
NOK 822,000
Est. value
NOK 2.1m

Financial health · 2024

Liquidity
0.93
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.5%
Satisfactory
Equity as a share of total capital

Who owns NANNESTAD VVS AS?

NIX HOLDING AS
NANNESTAD VVS AS
NOK 17.7m rev. · NOK 658,000 profit

NANNESTAD VVS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NANNESTAD VVS AS own?

NANNESTAD VVS AS holds a stake in 1 company:

See the full ownership structure →

Group structure

NANNESTAD VVS AS er morselskap for 1 datterselskap:

Frequently asked questions about NANNESTAD VVS AS

Who owns NANNESTAD VVS AS?

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

What is the revenue of NANNESTAD VVS AS?

NANNESTAD VVS AS had revenue of NOK 17.7m in 2024.

Who is the general manager of NANNESTAD VVS AS?

Andreas Erlandsen is registered as general manager of NANNESTAD VVS AS.

Where is NANNESTAD VVS AS based?

NANNESTAD VVS AS has its business address in Maura.

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.