BIZTRAC BETA
Uoppgitt

SAMAKIFINN AS

Org. no. 920847536 Limited company (AS) Bokn Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 3.9m
Incorporated 2018
Share capital NOK 30,000

Signals

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

SAMAKIFINN AS is registered as a limited company in Bokn, Rogaland with organisation number 920847536. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Forestå investeringer i aksjer og andre verdipapirer samt alt hva hermed står i forbindelse, herunder å delta i selskaper med samme formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 3.9m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns SAMAKIFINN AS?

FINN MAGNUS ALVESTAD
SAMAKIFINN AS
NOK 0 rev. · NOK −8,000 profit

SAMAKIFINN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SAMAKIFINN AS own?

SAMAKIFINN AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SAMAKIFINN AS

Who owns SAMAKIFINN AS?

FINN MAGNUS ALVESTAD is the largest registered owner, with 100.0%.

What is the revenue of SAMAKIFINN AS?

SAMAKIFINN AS had revenue of NOK 0 in 2025.

Who is the general manager of SAMAKIFINN AS?

Finn Magnus Alvestad is registered as general manager of SAMAKIFINN AS.

Where is SAMAKIFINN AS based?

SAMAKIFINN AS has its business address in Bokn.

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.