BIZTRAC BETA
Development of building projects

KROL AS

Org. no. 999276423 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 14,000
Operating profit NOK −57,000
Equity NOK 5.7m
Incorporated 2013
Share capital NOK 130,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−57k kr).

KROL AS is registered as a limited company in Oslo, Oslo with organisation number 999276423. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 130,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling, salg/kjøp av eiendommer, import/eksport, salg av handelsvarer, rådgivning og deltagelse i andre virksomheter, eiendomsutleie.”. The most recent filed accounts, for the 2024 financial year, show NOK 14,000 in revenue and NOK −57,000 in operating profit.

Key figures · 2024

Revenue
NOK 14,000
Operating profit
NOK −57,000
Equity
NOK 5.7m
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns KROL AS?

JAROSLAW ARNOLD ZAGIERSKI
KROL AS
NOK 14,000 rev. · NOK −57,000 profit

KROL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KROL AS own?

KROL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KROL AS

Who owns KROL AS?

JAROSLAW ARNOLD ZAGIERSKI is the largest registered owner, with 100.0%.

What is the revenue of KROL AS?

KROL AS had revenue of NOK 14,000 in 2024.

Who is the general manager of KROL AS?

Jaroslaw Arnold Zagierski is registered as general manager of KROL AS.

Where is KROL AS based?

KROL 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.