BIZTRAC BETA
Other captive investment companies

LRP HOLDING AS

Org. no. 914636531 Limited company (AS) Fredrikstad Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 157,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

LRP HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 914636531. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering og deltakelse i andre selskaper, samt salg av konsulenttjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 157,000
Est. value
NOK 143,000

Financial health · 2025

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

Who owns LRP HOLDING AS?

LASSE RENÈ PEDERSEN
LRP HOLDING AS
NOK 0 rev. · NOK −6,000 profit

LRP HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LRP HOLDING AS own?

LRP HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LRP HOLDING AS

Who owns LRP HOLDING AS?

LASSE RENÈ PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of LRP HOLDING AS?

LRP HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of LRP HOLDING AS?

Lasse Renè Pedersen is registered as general manager of LRP HOLDING AS.

Where is LRP HOLDING AS based?

LRP HOLDING AS has its business address in Gressvik.

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.