biztrac. BETA
COMPANY REGISTER PROFILE
926592408 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

SEUMROF HOLDING AS

Org. no. 926592408 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −64,000
Equity NOK 843.2m
Incorporated 2021
Share capital NOK 1.0m

Signals

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

SEUMROF HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 926592408. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 1.0m, divided into 346632 shares. The company's stated purpose is: “Virksomhet innenfor utvikling og investering i andre selskaper og alt som står i forbindelse med de forannevnte virksomheter.”.

Former names: INCEPTUM 1315 AS

Key figures · 2025

Operating profit
NOK −64,000
▼ −14 %
Equity
NOK 843.2m
▲ +0 %
Est. value
NOK 448.0m

Financial health · 2025

Liquidity
114.08
Very good
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
98.7%
Very good
Equity as a share of total capital

Who owns SEUMROF HOLDING AS?

IK PF LUXCO 10 S.A.R.L. LU
STYVIKEN INVEST AS NO
TTS PASS AB V/ MIKAEL WALTHER SE
SEUMROF HOLDING AS
· NOK −64,000 profit

SEUMROF HOLDING AS has 3 registered shareholders:

  • IK PF LUXCO 10 S.A.R.L. 86.5%
  • STYVIKEN INVEST AS 6.7%
  • TTS PASS AB V/ MIKAEL WALTHER 6.7%
All shareholders and roles →

Which companies does SEUMROF HOLDING AS own?

SEUMROF HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SEUMROF HOLDING AS

Who owns SEUMROF HOLDING AS?

IK PF LUXCO 10 S.A.R.L. is the largest registered owner, with 86.5%.

Where is SEUMROF HOLDING AS based?

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