BIZTRAC BETA
Rental and operating of own or leased real estate

RAL EIENDOM AS

Org. no. 915831702 Limited company (AS) Nome Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 1.4m
Equity NOK 2.4m
Incorporated 2015
Share capital NOK 36,000

RAL EIENDOM AS is registered as a limited company in Nome, Telemark with organisation number 915831702. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 36,000, divided into 600 shares. The company's stated purpose is: “Eiendomsutvikling med kjøp, utleie og salg av fast eiendom til bolig- og næringsformål, herunder alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 1.4m
Equity
NOK 2.4m
Est. value
NOK 4.4m

Financial health · 2025

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

Who owns RAL EIENDOM AS?

RUNE ANDERS LANGELAND
RAL EIENDOM AS
NOK 1.5m rev. · NOK 1.4m profit

RAL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RAL EIENDOM AS own?

RAL EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RAL EIENDOM AS

Who owns RAL EIENDOM AS?

RUNE ANDERS LANGELAND is the largest registered owner, with 100.0%.

What is the revenue of RAL EIENDOM AS?

RAL EIENDOM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of RAL EIENDOM AS?

Rune Anders Langeland is registered as general manager of RAL EIENDOM AS.

Where is RAL EIENDOM AS based?

RAL EIENDOM AS has its business address in Ulefoss.

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.