BIZTRAC BETA
Other captive investment companies

SUNGAM AS

Org. no. 989036521 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 474,000
Operating profit NOK 230,000
Equity NOK 15.2m
Incorporated 2005
Share capital NOK 1.0m

SUNGAM AS is registered as a limited company in Oslo, Oslo with organisation number 989036521. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Salg av tjenester, eie aksjer i andre selskaper, å delta med eierinteresser i andre selskaper, investere i faste eiendom. Kjøp, salg av aksjer og lånefinansiere investeringer med verdipapirer og valuta, samt annen virksomhet som står i naturlig forbindelse med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 474,000 in revenue and NOK 230,000 in operating profit.

Key figures · 2025

Revenue
NOK 474,000
Operating profit
NOK 230,000
Equity
NOK 15.2m
Est. value
NOK 9.0m

Financial health · 2025

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

Who owns SUNGAM AS?

HANS MAGNUS GREPPERUD
SUNGAM AS
NOK 474,000 rev. · NOK 230,000 profit

SUNGAM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SUNGAM AS own?

SUNGAM AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about SUNGAM AS

Who owns SUNGAM AS?

HANS MAGNUS GREPPERUD is the largest registered owner, with 33.8%.

What is the revenue of SUNGAM AS?

SUNGAM AS had revenue of NOK 474,000 in 2025.

Where is SUNGAM AS based?

SUNGAM 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.