BIZTRAC BETA
Uoppgitt

SEPIO HOLDING AS

Org. no. 920050255 Limited company (AS) Stavanger Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 294,000
Operating profit NOK 211,000
Equity NOK 847,000
Incorporated 2017
Share capital NOK 50,000

SEPIO HOLDING AS is registered as a limited company in Stavanger, Rogaland with organisation number 920050255. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 10000 shares. The company's stated purpose is: “Deltakelse i andre selskaper og generell investeringsvirksomhet, samt aktiviteter som hører naturlig inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 294,000 in revenue and NOK 211,000 in operating profit.

Key figures · 2025

Revenue
NOK 294,000
Operating profit
NOK 211,000
Equity
NOK 847,000
Est. value
NOK 963,000

Financial health · 2025

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

Who owns SEPIO HOLDING AS?

SVEN DAVID LAUSTEN KNUDSEN
SEPIO HOLDING AS
NOK 294,000 rev. · NOK 211,000 profit

SEPIO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SEPIO HOLDING AS own?

SEPIO HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SEPIO HOLDING AS

Who owns SEPIO HOLDING AS?

SVEN DAVID LAUSTEN KNUDSEN is the largest registered owner, with 100.0%.

What is the revenue of SEPIO HOLDING AS?

SEPIO HOLDING AS had revenue of NOK 294,000 in 2025.

Who is the general manager of SEPIO HOLDING AS?

Sven David Lausten Knudsen is registered as general manager of SEPIO HOLDING AS.

Where is SEPIO HOLDING AS based?

SEPIO HOLDING AS has its business address in Stavanger.

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.