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

ALCIDES HOLDING AS

Org. no. 943873011 Limited company (AS) Oslo Incorporated 1987 Active
Revenue 2025 NOK 56.9m
Operating profit NOK 45.9m
Equity NOK 1.0bn
Incorporated 1987
Share capital NOK 190.4m

ALCIDES HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 943873011. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 190.4m, divided into 1284 shares. The company's stated purpose is: “Investering i verdipapirer, herunder deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 56.9m in revenue and NOK 45.9m in operating profit.

Former names: AS SESSEN

Key figures · 2025

Revenue
NOK 56.9m
▼ −61 %
Operating profit
NOK 45.9m
▼ −67 %
Equity
NOK 1.0bn
▲ +3 %
Est. value
NOK 883.8m

Financial health · 2025

Liquidity
14.24
Very good
Current assets ÷ current liabilities
Profitability
6.4%
Satisfactory
Return on total assets
Solidity
93.8%
Very good
Equity as a share of total capital

Who owns ALCIDES HOLDING AS?

ALCIDES HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does ALCIDES HOLDING AS own?

ALCIDES HOLDING AS holds stakes in 10 companies:

See the full ownership structure →

Group structure

ALCIDES HOLDING AS er morselskap for 5 datterselskaper:

Frequently asked questions about ALCIDES HOLDING AS

Who owns ALCIDES HOLDING AS?

INGEBORG AS is the largest registered owner, with 25.0%.

What is the revenue of ALCIDES HOLDING AS?

ALCIDES HOLDING AS had revenue of NOK 56.9m in 2025.

Where is ALCIDES HOLDING AS based?

ALCIDES HOLDING 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 03.10.2026.

Report a problem

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