BIZTRAC BETA
Other real estate activities on a fee or contract basis

KREFTING EIENDOM AS

Org. no. 929219597 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK 30.0m
Incorporated 2022
Share capital NOK 30,000

Signals

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

KREFTING EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 929219597. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å investere i fast eiendom, eie, salg og drift av fast eiendom, og alt som dermed står i forbindelse.”.

Key figures · 2024

Operating profit
NOK −28,000
Equity
NOK 30.0m
Est. value
NOK 27.4m

Financial health · 2024

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

Who owns KREFTING EIENDOM AS?

CLEAN SHIP AS
KREFTING EIENDOM AS
· NOK −28,000 profit

KREFTING EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KREFTING EIENDOM AS own?

KREFTING EIENDOM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about KREFTING EIENDOM AS

Who owns KREFTING EIENDOM AS?

CLEAN SHIP AS is the largest registered owner, with 100.0%.

Who is the general manager of KREFTING EIENDOM AS?

Carl Christian Krefting is registered as general manager of KREFTING EIENDOM AS.

Where is KREFTING EIENDOM AS based?

KREFTING EIENDOM AS has its business address in Vøyenenga.

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.