BIZTRAC BETA
Rental and operating of own or leased real estate

ASPELIN REITAN KJELLER AS

Org. no. 966816228 Limited company (AS) Oslo Incorporated 1993 Active
Ownership graph ↗
Operating profit NOK −77,000
Equity NOK 107.6m
Incorporated 1993
Share capital NOK 10.6m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−77k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ASPELIN REITAN KJELLER AS is registered as a limited company in Oslo, Oslo with organisation number 966816228. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1993. Registered share capital is NOK 10.6m, divided into 9602 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.”.

Key figures · 2024

Operating profit
NOK −77,000
Equity
NOK 107.6m
Est. value
NOK 98.2m

Financial health · 2024

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

Who owns ASPELIN REITAN KJELLER AS?

ASPELIN REITAN EIENDOM AS
ASPELIN REITAN KJELLER AS
· NOK −77,000 profit

ASPELIN REITAN KJELLER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ASPELIN REITAN KJELLER AS own?

ASPELIN REITAN KJELLER AS holds a stake in 1 company:

See the full ownership structure →

Group structure

ASPELIN REITAN KJELLER AS er morselskap for 24 datterselskaper:

Frequently asked questions about ASPELIN REITAN KJELLER AS

Who owns ASPELIN REITAN KJELLER AS?

ASPELIN REITAN EIENDOM AS is the largest registered owner, with 100.0%.

Where is ASPELIN REITAN KJELLER AS based?

ASPELIN REITAN KJELLER AS has its business address in Oslo.

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.