BIZTRAC BETA
Construction of residential and non-residential buildings

BRP HOLDING AS

Org. no. 927164930 Limited company (AS) Ålesund Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 272,000
Operating profit NOK −100,000
Equity NOK 167,000
Incorporated 2021
Share capital NOK 90,000

Signals

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

BRP HOLDING AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 927164930. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 90,000, divided into 90000 shares. The company's stated purpose is: “Drift og investeringer i eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 272,000 in revenue and NOK −100,000 in operating profit.

Key figures · 2024

Revenue
NOK 272,000
Operating profit
NOK −100,000
Equity
NOK 167,000
Est. value
NOK 172,000

Financial health · 2024

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

Who owns BRP HOLDING AS?

KETIL PEDERSEN INVEST AS
BRP HOLDING AS
NOK 272,000 rev. · NOK −100,000 profit

BRP HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRP HOLDING AS own?

BRP HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BRP HOLDING AS

Who owns BRP HOLDING AS?

KETIL PEDERSEN INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of BRP HOLDING AS?

BRP HOLDING AS had revenue of NOK 272,000 in 2024.

Where is BRP HOLDING AS based?

BRP HOLDING AS has its business address in Ålesund.

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.