BIZTRAC BETA
Development of building projects

LINJEKVARTALET BOLIG AS

Org. no. 999216056 Limited company (AS) Aurskog-Høland Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 250,000
Operating profit NOK −1.1m
Equity NOK 40.0m
Incorporated 2012
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).

LINJEKVARTALET BOLIG AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 999216056. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Investering i fast eiendom, verdipapirer og andre formuesobjekter, samt alt som står i forbindelse med dette. Selskapet kan ta på seg annet inntektsgivende arbeid.”. The most recent filed accounts, for the 2024 financial year, show NOK 250,000 in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 250,000
Operating profit
NOK −1.1m
Equity
NOK 40.0m
Est. value
NOK 36.5m

Financial health · 2024

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

Who owns LINJEKVARTALET BOLIG AS?

BAKKE LEILIGHETER AS
LINJEKVARTALET BOLIG AS
NOK 250,000 rev. · NOK −1.1m profit

LINJEKVARTALET BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LINJEKVARTALET BOLIG AS

Who owns LINJEKVARTALET BOLIG AS?

BAKKE LEILIGHETER AS is the largest registered owner, with 100.0%.

What is the revenue of LINJEKVARTALET BOLIG AS?

LINJEKVARTALET BOLIG AS had revenue of NOK 250,000 in 2024.

Where is LINJEKVARTALET BOLIG AS based?

LINJEKVARTALET BOLIG AS has its business address in Aurskog.

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.