biztrac. BETA
COMPANY REGISTER PROFILE
936127614 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

SAMAKI INVEST AS

Org. no. 936127614 Limited company (AS) Lindesnes Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 21,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

SAMAKI INVEST AS is registered as a limited company in Lindesnes, Agder with organisation number 936127614. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen eiendomssalg og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2025

Operating profit
NOK −2,000
Equity
NOK 21,000
Est. value
NOK 19,000

Financial health · 2025

Liquidity
0.05
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
2.4%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SAMAKI INVEST AS?

SAMAKI INVEST AS
· NOK −2,000 profit

SAMAKI INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SAMAKI INVEST AS own?

SAMAKI INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SAMAKI INVEST AS

Who owns SAMAKI INVEST AS?

Vegard Aanensen is the largest registered owner, with 100.0%.

Who is the general manager of SAMAKI INVEST AS?

Vegard Aanensen is registered as general manager of SAMAKI INVEST AS.

Where is SAMAKI INVEST AS based?

SAMAKI INVEST AS has its business address in Mandal.

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

Report a problem

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