BIZTRAC BETA
Rental and operating of own or leased real estate

KISTEFOS EIENDOM AS

Org. no. 943734305 Limited company (AS) Oslo Incorporated 1987 Active
Ownership graph ↗
Operating profit NOK −75,000
Equity NOK 303.7m
Incorporated 1987
Share capital NOK 60,000

Signals

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

KISTEFOS EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 943734305. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 60,000, divided into 157620 shares. The company's stated purpose is: “Erverv, utvikling, drift og salg av fast eiendom, handel-, konsulent-, shipping- og industrivirk- somhet og alt som hermed står i forbindelse, her- under deltagelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −75,000
Equity
NOK 303.7m
Est. value
NOK 277.1m

Financial health · 2025

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

Who owns KISTEFOS EIENDOM AS?

KISTEFOS AS
KISTEFOS EIENDOM AS
· NOK −75,000 profit

KISTEFOS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KISTEFOS EIENDOM AS own?

KISTEFOS EIENDOM AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

KISTEFOS EIENDOM AS er morselskap for 5 datterselskaper:

Frequently asked questions about KISTEFOS EIENDOM AS

Who owns KISTEFOS EIENDOM AS?

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

Where is KISTEFOS EIENDOM AS based?

KISTEFOS EIENDOM 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.