BIZTRAC BETA
Uoppgitt

LIMSTRAND EIENDOM AS

Org. no. 929351924 Limited company (AS) Sula Incorporated 1979 Active
Ownership graph ↗
Revenue 2025 NOK 713,000
Operating profit NOK 324,000
Equity NOK 13.1m
Incorporated 1979
Share capital NOK 100,000

LIMSTRAND EIENDOM AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 929351924. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 1979. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Produksjon av butikkinnredning, samt annen virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 713,000 in revenue and NOK 324,000 in operating profit.

Key figures · 2025

Revenue
NOK 713,000
Operating profit
NOK 324,000
Equity
NOK 13.1m
Est. value
NOK 8.1m

Financial health · 2025

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

Who owns LIMSTRAND EIENDOM AS?

HALLGEIR EDVIN LIMSTRAND
LIMSTRAND EIENDOM AS
NOK 713,000 rev. · NOK 324,000 profit

LIMSTRAND EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LIMSTRAND EIENDOM AS own?

LIMSTRAND EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LIMSTRAND EIENDOM AS

Who owns LIMSTRAND EIENDOM AS?

HALLGEIR EDVIN LIMSTRAND is the largest registered owner, with 100.0%.

What is the revenue of LIMSTRAND EIENDOM AS?

LIMSTRAND EIENDOM AS had revenue of NOK 713,000 in 2025.

Who is the general manager of LIMSTRAND EIENDOM AS?

Hallgeir Edvin Limstrand is registered as general manager of LIMSTRAND EIENDOM AS.

Where is LIMSTRAND EIENDOM AS based?

LIMSTRAND EIENDOM AS has its business address in Eidsnes.

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.