BIZTRAC BETA
Roofing activities

NRBV INVEST AS

Org. no. 990468583 Limited company (AS) Haugesund Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK 5.7m
Incorporated 2006
Share capital NOK 300,000

Signals

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

NRBV INVEST AS is registered as a limited company in Haugesund, Rogaland with organisation number 990468583. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 2006. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Selskapets formål er investering i aksjer og andeler, samt å kunne delta i foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 5.7m
Est. value
NOK 5.8m

Financial health · 2024

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

Who owns NRBV INVEST AS?

PROVENT AS
NRBV INVEST AS
NOK 0 rev. · NOK −18,000 profit

NRBV INVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does NRBV INVEST AS own?

NRBV INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NRBV INVEST AS

Who owns NRBV INVEST AS?

PROVENT AS is the largest registered owner, with 33.3%.

What is the revenue of NRBV INVEST AS?

NRBV INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of NRBV INVEST AS?

Anders Petter Clausen is registered as general manager of NRBV INVEST AS.

Where is NRBV INVEST AS based?

NRBV INVEST AS has its business address in Haugesund.

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.