BIZTRAC BETA
COMPANY REGISTER PROFILE
916225962 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SVEMAR AS

Org. no. 916225962 Limited company (AS) Strand Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 163,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

SVEMAR AS is registered as a limited company in Strand, Rogaland with organisation number 916225962. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å eie aksjer og andeler i andre selskap, samt beslektet virksomhet.”.

Key figures · 2025

Operating profit
NOK −16,000
▲ +13 %
Equity
NOK 163,000
▲ +35 %
Est. value
NOK 364,000

Financial health · 2025

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

Who owns SVEMAR AS?

SVEMAR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SVEMAR AS own?

SVEMAR AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SVEMAR AS

Who owns SVEMAR AS?

SVEINUNG ANDRE IDSAL is the largest registered owner, with 50.0%.

Where is SVEMAR AS based?

SVEMAR AS has its business address in Idse.

Property

Business address Idsalvegen 49, 4102 Idse
Cadastral unit 1130-62/2/0/0
Building Våningshus · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

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