BIZTRAC BETA
Rental and operating of own or leased real estate

O RØNNING EIENDOM AS

Org. no. 913854330 Limited company (AS) Alstahaug Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 600,000
Operating profit NOK 435,000
Equity NOK 2.7m
Incorporated 2014
Share capital NOK 37,000

O RØNNING EIENDOM AS is registered as a limited company in Alstahaug, Nordland with organisation number 913854330. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 37,000, divided into 37 shares. The company's stated purpose is: “Investeringer i og drift og utleie av fast eiendom og driftsmidler, konsulentarbeid og investeringer i aksjer samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 600,000 in revenue and NOK 435,000 in operating profit.

Key figures · 2025

Revenue
NOK 600,000
Operating profit
NOK 435,000
Equity
NOK 2.7m
Est. value
NOK 2.8m

Financial health · 2025

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

Who owns O RØNNING EIENDOM AS?

LIV RØNNING
O RØNNING EIENDOM AS
NOK 600,000 rev. · NOK 435,000 profit

O RØNNING EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about O RØNNING EIENDOM AS

Who owns O RØNNING EIENDOM AS?

LIV RØNNING is the largest registered owner, with 100.0%.

What is the revenue of O RØNNING EIENDOM AS?

O RØNNING EIENDOM AS had revenue of NOK 600,000 in 2025.

Who is the general manager of O RØNNING EIENDOM AS?

Liv Rønning is registered as general manager of O RØNNING EIENDOM AS.

Where is O RØNNING EIENDOM AS based?

O RØNNING EIENDOM AS has its business address in Sandnessjøen.

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.