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

SIVIG AS

Org. no. 931043390 Limited company (AS) Lindesnes Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 201,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

SIVIG AS is registered as a limited company in Lindesnes, Agder with organisation number 931043390. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i aksjer, fast eiendom og lignende.”.

Key figures · 2025

Operating profit
NOK −5,000
▲ +17 %
Equity
NOK 201,000
▼ −2 %
Est. value
NOK 237,000

Financial health · 2025

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

Who owns SIVIG AS?

SIVIG AS
· NOK −5,000 profit

SIVIG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIVIG AS own?

SIVIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIVIG AS

Who owns SIVIG AS?

SIV THERESE VIGEMYR is the largest registered owner, with 100.0%.

Where is SIVIG AS based?

SIVIG AS has its business address in Marnardal.

Property

Business address Konsmoheiveien 646, 4534 Marnardal
Cadastral unit 4205-623/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.