BIZTRAC BETA
Computer consultancy and computer facilities management activities

SAGO AS

Org. no. 991918019 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 369,000
Operating profit NOK −1,000
Equity NOK 86,000
Incorporated 2007
Share capital NOK 100,000

Signals

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

SAGO AS is registered as a limited company in Oslo, Oslo with organisation number 991918019. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Grafisk utforming, rådgivning, konsulentvirksomhet og ideskapning innenfor informasjons- og mediebransjen, samt annen virksomhet, med spesielle fokus på tidsskrifter.”. The most recent filed accounts, for the 2025 financial year, show NOK 369,000 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 369,000
Operating profit
NOK −1,000
Equity
NOK 86,000
Est. value
NOK 662,000

Financial health · 2025

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

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

Who owns SAGO AS?

MARIANNE HOLEN
SAGO AS
NOK 369,000 rev. · NOK −1,000 profit

SAGO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAGO AS

Who owns SAGO AS?

MARIANNE HOLEN is the largest registered owner, with 100.0%.

What is the revenue of SAGO AS?

SAGO AS had revenue of NOK 369,000 in 2025.

Who is the general manager of SAGO AS?

Marianne Holen is registered as general manager of SAGO AS.

Where is SAGO AS based?

SAGO AS has its business address in Oslo.

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.