BIZTRAC BETA
Rental and operating of own or leased real estate

LINSTAD EIENDOM AS

Org. no. 922958335 Limited company (AS) Gran Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 1.7m
Equity NOK 5.0m
Incorporated 2019
Share capital NOK 60,000

Signals

1 flags
  • Nylig endring 2026-02-11 Adresseendring registrert 2026-02-11.

LINSTAD EIENDOM AS is registered as a limited company in Gran, Innlandet with organisation number 922958335. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 60,000, divided into 100 shares. The company's stated purpose is: “Drift og utvikling av fast eiendom samt annen virksomhet i forbindelse med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 1.7m
Equity
NOK 5.0m
Est. value
NOK 7.4m

Financial health · 2024

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

Who owns LINSTAD EIENDOM AS?

LINSTAD HOLDING AS
LINSTAD EIENDOM AS
NOK 4.2m rev. · NOK 1.7m profit

LINSTAD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LINSTAD EIENDOM AS own?

LINSTAD EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LINSTAD EIENDOM AS

Who owns LINSTAD EIENDOM AS?

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

What is the revenue of LINSTAD EIENDOM AS?

LINSTAD EIENDOM AS had revenue of NOK 4.2m in 2024.

Where is LINSTAD EIENDOM AS based?

LINSTAD EIENDOM AS has its business address in Gran.

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.