BIZTRAC BETA
Rental and operating of own or leased real estate

KIRKEPARKEN NÆRINGSEIENDOM AS

Org. no. 923478213 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 642,000
Equity NOK 380,000
Incorporated 2019
Share capital NOK 30,000

KIRKEPARKEN NÆRINGSEIENDOM AS is registered as a limited company in Lillestrøm, Akershus with organisation number 923478213. 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 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 642,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 642,000
Equity
NOK 380,000
Est. value
NOK 675,000

Financial health · 2025

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

Who owns KIRKEPARKEN NÆRINGSEIENDOM AS?

LANDSOME AS
KIRKEPARKEN NÆRINGSEIENDOM AS
NOK 1.2m rev. · NOK 642,000 profit

KIRKEPARKEN NÆRINGSEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

KIRKEPARKEN NÆRINGSEIENDOM AS er morselskap for 2 datterselskaper:

Frequently asked questions about KIRKEPARKEN NÆRINGSEIENDOM AS

Who owns KIRKEPARKEN NÆRINGSEIENDOM AS?

LANDSOME AS is the largest registered owner, with 100.0%.

What is the revenue of KIRKEPARKEN NÆRINGSEIENDOM AS?

KIRKEPARKEN NÆRINGSEIENDOM AS had revenue of NOK 1.2m in 2025.

Where is KIRKEPARKEN NÆRINGSEIENDOM AS based?

KIRKEPARKEN NÆRINGSEIENDOM AS has its business address in Lillestrøm.

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.