BIZTRAC BETA
Uoppgitt

SAGAMO INVEST AS

Org. no. 827792012 Limited company (AS) Bjørnafjorden Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −17,000
Equity NOK 1.1m
Incorporated 2021
Share capital NOK 90,000

Signals

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

SAGAMO INVEST AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 827792012. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 90,000, divided into 1 shares. The company's stated purpose is: “Aksje- og investeringsvirksomhet i andre selskaper, og alt som har sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −17,000
Equity
NOK 1.1m
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns SAGAMO INVEST AS?

STÅLE SKAATUN
SAGAMO INVEST AS
NOK 0 rev. · NOK −17,000 profit

SAGAMO INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SAGAMO INVEST AS own?

SAGAMO INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SAGAMO INVEST AS

Who owns SAGAMO INVEST AS?

STÅLE SKAATUN is the largest registered owner, with 100.0%.

What is the revenue of SAGAMO INVEST AS?

SAGAMO INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of SAGAMO INVEST AS?

Ståle Skaatun is registered as general manager of SAGAMO INVEST AS.

Where is SAGAMO INVEST AS based?

SAGAMO INVEST AS has its business address in Os.

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.