BIZTRAC BETA
Rental and operating of own or leased real estate

RL HOLDING AS

Org. no. 888873252 Limited company (AS) Vennesla Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −26,000
Equity NOK 677,000
Incorporated 2005
Share capital NOK 677,000

Signals

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

RL HOLDING AS is registered as a limited company in Vennesla, Agder with organisation number 888873252. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 677,000, divided into 677 shares. The company's stated purpose is: “Investering og finansplassering i eiendommer, aksjer og andre virksomheter, samt kjøp, salg og utleie av fast eiendom, med alt hva hermed står i forbindelse. Selskapet kan gjennom aksjetegning eller på annen måte delta i andre selskap eller foretak. Selskapet kan også drive vanlig handel.”.

Key figures · 2025

Operating profit
NOK −26,000
Equity
NOK 677,000
Est. value
NOK 2.2m

Financial health · 2025

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

Who owns RL HOLDING AS?

ELISABETH LIEBERMANN
RL HOLDING AS
· NOK −26,000 profit

RL HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does RL HOLDING AS own?

RL HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RL HOLDING AS

Who owns RL HOLDING AS?

ELISABETH LIEBERMANN is the largest registered owner, with 85.2%.

Who is the general manager of RL HOLDING AS?

Roy Erik Liebermann is registered as general manager of RL HOLDING AS.

Where is RL HOLDING AS based?

RL HOLDING AS has its business address in Vennesla.

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.