BIZTRAC BETA
Uoppgitt

SEILMAKEREN INVEST 2 AS

Org. no. 928291944 Limited company (AS) Alver Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −15,000
Equity NOK 1.6m
Incorporated 2021
Share capital NOK 41,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).

SEILMAKEREN INVEST 2 AS is registered as a limited company in Alver, Vestland with organisation number 928291944. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 41,000, divided into 41300 shares. The company's stated purpose is: “Å eie aksjer i andre selskaper samt forvalte eierinteressene av disse. Selskapet skal også kunne forestå administrative tjenester for andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK 1.6m
Est. value
NOK 1.5m

Financial health · 2024

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

Who owns SEILMAKEREN INVEST 2 AS?

MAGNE IVERSEN
SEILMAKEREN INVEST 2 AS
NOK 0 rev. · NOK −15,000 profit

SEILMAKEREN INVEST 2 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SEILMAKEREN INVEST 2 AS own?

SEILMAKEREN INVEST 2 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SEILMAKEREN INVEST 2 AS

Who owns SEILMAKEREN INVEST 2 AS?

MAGNE IVERSEN is the largest registered owner, with 100.0%.

What is the revenue of SEILMAKEREN INVEST 2 AS?

SEILMAKEREN INVEST 2 AS had revenue of NOK 0 in 2024.

Where is SEILMAKEREN INVEST 2 AS based?

SEILMAKEREN INVEST 2 AS has its business address in Frekhaug.

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.