biztrac. BETA
COMPANY REGISTER PROFILE
915911250 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Legal activities

SICI AS

Org. no. 915911250 Limited company (AS) Bergen Incorporated 2015 Active
Revenue 2025 NOK 478,000
Operating profit NOK −37,000
Equity NOK 89,000
Incorporated 2015
Share capital NOK 100,000

Signals

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

SICI AS is registered as a limited company in Bergen, Vestland with organisation number 915911250. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Spesialutreder, konsulentvirksomhet, rådgivning i sivil rettsige og strafferettslige saker, og alt som naturlig hører med, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 478,000 in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 478,000
▼ −28 %
Operating profit
NOK −37,000
▲ +70 %
Equity
NOK 89,000
▼ −29 %
Est. value
NOK 545,000

Financial health · 2025

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
-11.9%
Not satisfactory
Return on total assets
Solidity
49.0%
Weak
Equity as a share of total capital

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

Who owns SICI AS?

SICI AS
NOK 478,000 rev. · NOK −37,000 profit

SICI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SICI AS

Who owns SICI AS?

Sverre Stenersen is the largest registered owner, with 100.0%.

What is the revenue of SICI AS?

SICI AS had revenue of NOK 478,000 in 2025.

Who is the general manager of SICI AS?

Sverre Stenersen is registered as general manager of SICI AS.

Where is SICI AS based?

SICI AS has its business address in Bergen.

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.