BIZTRAC BETA
Rental and operating of own or leased real estate

LIMA EIENDOM AS

Org. no. 857648382 Limited company (AS) Gjesdal Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 2.4m
Equity NOK 1.6m
Incorporated 1990
Share capital NOK 500,000

LIMA EIENDOM AS is registered as a limited company in Gjesdal, Rogaland with organisation number 857648382. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990. Registered share capital is NOK 500,000, divided into 760 shares. The company's stated purpose is: “Eiendomsutvikling, utleie og hva dermed står i forbindelse, samt deltakelse i virksomheter med dels likeartede og beslektede formål, herunder deltakelse gjennom aksjekjøp. I tillegg skal selskapet ha mulighet til å investere i ulike finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 2.4m in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK 2.4m
Equity
NOK 1.6m
Est. value
NOK 5.8m

Financial health · 2025

Liquidity
0.20
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.2%
Weak
Equity as a share of total capital

Who owns LIMA EIENDOM AS?

ASTRI HOLDING AS
LIMA EIENDOM AS
NOK 4.7m rev. · NOK 2.4m profit

LIMA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LIMA EIENDOM AS

Who owns LIMA EIENDOM AS?

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

What is the revenue of LIMA EIENDOM AS?

LIMA EIENDOM AS had revenue of NOK 4.7m in 2025.

Who is the general manager of LIMA EIENDOM AS?

Tor Arne Lima is registered as general manager of LIMA EIENDOM AS.

Where is LIMA EIENDOM AS based?

LIMA EIENDOM AS has its business address in Ålgård.

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.