BIZTRAC BETA
Rental and operating of own or leased real estate

KURLANDSÅSEN 2 EIENDOM AS

Org. no. 898374122 Limited company (AS) Nordre Follo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 1.1m
Equity NOK 3.3m
Incorporated 2012
Share capital NOK 839,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

KURLANDSÅSEN 2 EIENDOM AS is registered as a limited company in Nordre Follo, Akershus with organisation number 898374122. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 839,000, divided into 839088 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som driver fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 1.1m
Equity
NOK 3.3m
Est. value
NOK 4.2m

Financial health · 2024

Liquidity
1.00
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.0%
Good
Equity as a share of total capital

Who owns KURLANDSÅSEN 2 EIENDOM AS?

COOP ØST SA
KURLANDSÅSEN 2 EIENDOM AS
NOK 1.5m rev. · NOK 1.1m profit

KURLANDSÅSEN 2 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KURLANDSÅSEN 2 EIENDOM AS

Who owns KURLANDSÅSEN 2 EIENDOM AS?

COOP ØST SA is the largest registered owner, with 100.0%.

What is the revenue of KURLANDSÅSEN 2 EIENDOM AS?

KURLANDSÅSEN 2 EIENDOM AS had revenue of NOK 1.5m in 2024.

Where is KURLANDSÅSEN 2 EIENDOM AS based?

KURLANDSÅSEN 2 EIENDOM AS has its business address in Kolbotn.

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.