BIZTRAC BETA
Rental and operating of own or leased real estate

KROKUSVEIEN EIENDOM AS

Org. no. 918984518 Limited company (AS) Sandefjord Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −1.4m
Equity NOK −4.4m
Incorporated 2017
Share capital NOK 100,000

Signals

4 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−4,4 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,4 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-13 Adresseendring registrert 2026-04-13.

KROKUSVEIEN EIENDOM AS is registered as a limited company in Sandefjord, Vestfold with organisation number 918984518. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Å investere i fast eiendom, aksjer, verdipapirer, herunder deltagelse i andre selskaper, samt plassering av likvid kapital på en sikker og regningssvarende måte.”.

Key figures · 2025

Operating profit
NOK −1.4m
Equity
NOK −4.4m

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-19533.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KROKUSVEIEN EIENDOM AS?

ZUM AS
KROKUSVEIEN EIENDOM AS
· NOK −1.4m profit

KROKUSVEIEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KROKUSVEIEN EIENDOM AS

Who owns KROKUSVEIEN EIENDOM AS?

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

Where is KROKUSVEIEN EIENDOM AS based?

KROKUSVEIEN EIENDOM AS has its business address in Stokke.

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.