BIZTRAC BETA
Interior design activities

SEFER HOLDING AS

Org. no. 932745887 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 14,000
Incorporated 2023
Share capital NOK 30,000

SEFER HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 932745887. The business is classified under interior design activities (NACE 74.130). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eie, kjøpe og selge aksjer og andeler. Utlån av selskapets verdier samt det som naturlig står i forbindelse med dette. Investeringsvirksomhet og deltakelse i andre selskaper og fungere som et holdingselskap og alt som står i forbindelse med det.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 14,000
Est. value
NOK 23,000

Financial health · 2025

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

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

Who owns SEFER HOLDING AS?

PAMELA SEFER
SEFER HOLDING AS
NOK 0 rev. · NOK 0 profit

SEFER HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SEFER HOLDING AS own?

SEFER HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SEFER HOLDING AS

Who owns SEFER HOLDING AS?

PAMELA SEFER is the largest registered owner, with 50.0%.

What is the revenue of SEFER HOLDING AS?

SEFER HOLDING AS had revenue of NOK 0 in 2025.

Where is SEFER HOLDING AS based?

SEFER HOLDING AS has its business address in Rykkinn.

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.