BIZTRAC BETA
Uoppgitt

RPB HOLDING AS

Org. no. 925560219 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −15,000
Equity NOK 265,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

RPB HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925560219. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å inneha eierandeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 265,000
Est. value
NOK 311,000

Financial health · 2024

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

Who owns RPB HOLDING AS?

ROBIN PEDERSEN BRAUTI
RPB HOLDING AS
NOK 0 rev. · NOK −15,000 profit

RPB HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RPB HOLDING AS own?

RPB HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

RPB HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about RPB HOLDING AS

Who owns RPB HOLDING AS?

ROBIN PEDERSEN BRAUTI is the largest registered owner, with 100.0%.

What is the revenue of RPB HOLDING AS?

RPB HOLDING AS had revenue of NOK 0 in 2024.

Where is RPB HOLDING AS based?

RPB HOLDING AS has its business address in Trondheim.

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.