biztrac. BETA
COMPANY REGISTER PROFILE
925876704 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

CIRENITA AS

Org. no. 925876704 Limited company (AS) Færder Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK 8,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

CIRENITA AS is registered as a limited company in Færder, Vestfold with organisation number 925876704. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende. Selskapet skal også bedrive kjøp og salg av varer.”.

Key figures · 2025

Operating profit
NOK −7,000
▼ −4 %
Equity
NOK 8,000
▼ −47 %
Est. value
NOK 7,000

Financial health · 2025

Liquidity
0.87
Weak
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-14.6%
Weak
Equity as a share of total capital

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

Who owns CIRENITA AS?

CIRENITA AS
· NOK −7,000 profit

CIRENITA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CIRENITA AS own?

CIRENITA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CIRENITA AS

Who owns CIRENITA AS?

Kjersti Caroline Lønmo-Egeland is the largest registered owner, with 100.0%.

Where is CIRENITA AS based?

CIRENITA AS has its business address in Nøtterøy.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.