BIZTRAC BETA
Uoppgitt

SEMELHOLSTIND AS

Org. no. 934388321 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 169,000
Incorporated 2024
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).
  • Nylig endring 2026-03-04 Aksjekapital registrert 2026-03-04.

SEMELHOLSTIND AS is registered as a limited company in Oslo, Oslo with organisation number 934388321. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 60,000, divided into 60000 shares. The company's stated purpose is: “Investering i aksjer og verdipapirer, inkludert, men ikke begrenset til, kjøp, salg og forvaltning av aksjer, obligasjoner, derivater og andre finansielle instrumenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 169,000
Est. value
NOK 199,000

Financial health · 2025

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

Who owns SEMELHOLSTIND AS?

THERESE SOLBERG
SEMELHOLSTIND AS
NOK 0 rev. · NOK −5,000 profit

SEMELHOLSTIND AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SEMELHOLSTIND AS own?

SEMELHOLSTIND AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SEMELHOLSTIND AS

Who owns SEMELHOLSTIND AS?

THERESE SOLBERG is the largest registered owner, with 50.0%.

What is the revenue of SEMELHOLSTIND AS?

SEMELHOLSTIND AS had revenue of NOK 0 in 2025.

Where is SEMELHOLSTIND AS based?

SEMELHOLSTIND 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 15.06.2026.

Report a problem

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