BIZTRAC BETA
Rental and operating of own or leased real estate

LINJEGÅRDEN NÆRING AS

Org. no. 920699383 Limited company (AS) Lillestrøm Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK 1.6m
Equity NOK 1.9m
Incorporated 2018
Share capital NOK 3.0m

LINJEGÅRDEN NÆRING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 920699383. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 3.0m, divided into 3030000 shares. The company's stated purpose is: “Erverve, utvikle, eie, selge og leie ut fast eiendom og annet som står i naturlig forbindelse med dette, samt investere i aksjer og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK 1.6m
Equity
NOK 1.9m
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns LINJEGÅRDEN NÆRING AS?

ROMERIKE SPAREBANK
LINJEGÅRDEN NÆRING AS
NOK 3.5m rev. · NOK 1.6m profit

LINJEGÅRDEN NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LINJEGÅRDEN NÆRING AS

Who owns LINJEGÅRDEN NÆRING AS?

ROMERIKE SPAREBANK is the largest registered owner, with 100.0%.

What is the revenue of LINJEGÅRDEN NÆRING AS?

LINJEGÅRDEN NÆRING AS had revenue of NOK 3.5m in 2024.

Who is the general manager of LINJEGÅRDEN NÆRING AS?

Marius Larsen Vesthagen is registered as general manager of LINJEGÅRDEN NÆRING AS.

Where is LINJEGÅRDEN NÆRING AS based?

LINJEGÅRDEN NÆRING AS has its business address in Sørumsand.

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.