BIZTRAC BETA
Uoppgitt

SVANEM EKSAKT HOLDING AS

Org. no. 924481781 Limited company (AS) Orkland Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 7,000
Operating profit NOK −717
Equity NOK 243,000
Incorporated 2019
Share capital NOK 300,000

Signals

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

SVANEM EKSAKT HOLDING AS is registered as a limited company in Orkland, Trøndelag with organisation number 924481781. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Holdingselskap med kjøp og salg av aksjer, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 7,000 in revenue and NOK −717 in operating profit.

Key figures · 2025

Revenue
NOK 7,000
Operating profit
NOK −717
Equity
NOK 243,000
Est. value
NOK 285,000

Financial health · 2025

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

Who owns SVANEM EKSAKT HOLDING AS?

STINE SELNES SVANEM
SVANEM EKSAKT HOLDING AS
NOK 7,000 rev. · NOK −717 profit

SVANEM EKSAKT HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SVANEM EKSAKT HOLDING AS own?

SVANEM EKSAKT HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVANEM EKSAKT HOLDING AS

Who owns SVANEM EKSAKT HOLDING AS?

STINE SELNES SVANEM is the largest registered owner, with 50.0%.

What is the revenue of SVANEM EKSAKT HOLDING AS?

SVANEM EKSAKT HOLDING AS had revenue of NOK 7,000 in 2025.

Where is SVANEM EKSAKT HOLDING AS based?

SVANEM EKSAKT HOLDING AS has its business address in Lensvik.

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.