BIZTRAC BETA
Other captive investment companies

KRICLA AS

Org. no. 919591684 Limited company (AS) Drammen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 32,000
Operating profit NOK −17,000
Equity NOK 4.4m
Incorporated 2017
Share capital NOK 61,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

KRICLA AS is registered as a limited company in Drammen, Buskerud with organisation number 919591684. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 61,000, divided into 72 shares. The company's stated purpose is: “Import/eksport, salg av handelsvare, rådgivning, eiendomsinvesteringer og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 32,000 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 32,000
Operating profit
NOK −17,000
Equity
NOK 4.4m
Est. value
NOK 9.7m

Financial health · 2025

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

Who owns KRICLA AS?

KRISTIN STANGNES CLAUDI
KRICLA AS
NOK 32,000 rev. · NOK −17,000 profit

KRICLA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KRICLA AS own?

KRICLA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KRICLA AS

Who owns KRICLA AS?

KRISTIN STANGNES CLAUDI is the largest registered owner, with 100.0%.

What is the revenue of KRICLA AS?

KRICLA AS had revenue of NOK 32,000 in 2025.

Who is the general manager of KRICLA AS?

Kristin Stangnes Claudi is registered as general manager of KRICLA AS.

Where is KRICLA AS based?

KRICLA AS has its business address in Drammen.

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.