BIZTRAC BETA
Rental and operating of own or leased real estate

SINGSAKER HOLDING AS

Org. no. 994239228 Limited company (AS) Trondheim Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −28,000
Equity NOK 1.1m
Incorporated 2009
Share capital NOK 2.1m

Signals

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

SINGSAKER HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 994239228. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2009. Registered share capital is NOK 2.1m, divided into 2100000 shares. The company's stated purpose is: “Investeringer i andre selskaper og eiendom, samt hva herved står i sammenheng.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 1.1m
Est. value
NOK 969,000

Financial health · 2025

Liquidity
0.02
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.6%
Good
Equity as a share of total capital

Who owns SINGSAKER HOLDING AS?

HEGE CHRISTIN FOSSUM
SINGSAKER HOLDING AS
NOK 0 rev. · NOK −28,000 profit

SINGSAKER HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SINGSAKER HOLDING AS own?

SINGSAKER HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SINGSAKER HOLDING AS

Who owns SINGSAKER HOLDING AS?

HEGE CHRISTIN FOSSUM is the largest registered owner, with 50.0%.

What is the revenue of SINGSAKER HOLDING AS?

SINGSAKER HOLDING AS had revenue of NOK 0 in 2025.

Where is SINGSAKER HOLDING AS based?

SINGSAKER HOLDING AS has its business address in Trondheim.

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.