BIZTRAC BETA
Rental and operating of own or leased real estate

LIMO EIENDOM AS

Org. no. 982055784 Limited company (AS) Østre Toten Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 1.0m
Equity NOK 2.0m
Incorporated 2000
Share capital NOK 100,000

LIMO EIENDOM AS is registered as a limited company in Østre Toten, Innlandet with organisation number 982055784. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, drift og salg av fast eiendom, investering i andre selskaper samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 1.0m
Equity
NOK 2.0m
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns LIMO EIENDOM AS?

LIMO HOLDING AS
LIMO EIENDOM AS
NOK 1.8m rev. · NOK 1.0m profit

LIMO EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIMO EIENDOM AS own?

LIMO EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LIMO EIENDOM AS

Who owns LIMO EIENDOM AS?

LIMO HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LIMO EIENDOM AS?

LIMO EIENDOM AS had revenue of NOK 1.8m in 2024.

Who is the general manager of LIMO EIENDOM AS?

Svein Iversbakken is registered as general manager of LIMO EIENDOM AS.

Where is LIMO EIENDOM AS based?

LIMO EIENDOM AS has its business address in Lena.

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.