BIZTRAC BETA
Rental and operating of own or leased real estate

ERLING RØD EIENDOM AS

Org. no. 815549872 Limited company (AS) Indre Østfold Incorporated 1961 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 2.7m
Equity NOK 11.1m
Incorporated 1961
Share capital NOK 2.0m

ERLING RØD EIENDOM AS is registered as a limited company in Indre Østfold, Østfold with organisation number 815549872. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1961. Registered share capital is NOK 2.0m, divided into 4900 shares. The company's stated purpose is: “Eiendomsutvikling og utleie.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 2.7m
Equity
NOK 11.1m
Est. value
NOK 13.3m

Financial health · 2025

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

Who owns ERLING RØD EIENDOM AS?

PERNILLE RØD
ERLING RØD EIENDOM AS
NOK 3.3m rev. · NOK 2.7m profit

ERLING RØD EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ERLING RØD EIENDOM AS own?

ERLING RØD EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ERLING RØD EIENDOM AS

Who owns ERLING RØD EIENDOM AS?

PERNILLE RØD is the largest registered owner, with 30.0%.

What is the revenue of ERLING RØD EIENDOM AS?

ERLING RØD EIENDOM AS had revenue of NOK 3.3m in 2025.

Who is the general manager of ERLING RØD EIENDOM AS?

Geir Listrøm Pedersen is registered as general manager of ERLING RØD EIENDOM AS.

Where is ERLING RØD EIENDOM AS based?

ERLING RØD EIENDOM AS has its business address in Askim.

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.