BIZTRAC BETA
Other captive investment companies

SINGELSTAD HOLDING AS

Org. no. 914211174 Limited company (AS) Bergen Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 974
Operating profit NOK −1,000
Equity NOK 257,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

SINGELSTAD HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 914211174. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Ha eierandeler i andre selskaper ved aksjehandel, samt drive med kjøp og salg av andre verdipapirer.”. The most recent filed accounts, for the 2024 financial year, show NOK 974 in revenue and NOK −1,000 in operating profit.

Key figures · 2024

Revenue
NOK 974
Operating profit
NOK −1,000
Equity
NOK 257,000
Est. value
NOK 473,000

Financial health · 2024

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

Who owns SINGELSTAD HOLDING AS?

SIGURD SINGELSTAD
SINGELSTAD HOLDING AS
NOK 974 rev. · NOK −1,000 profit

SINGELSTAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SINGELSTAD HOLDING AS own?

SINGELSTAD HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about SINGELSTAD HOLDING AS

Who owns SINGELSTAD HOLDING AS?

SIGURD SINGELSTAD is the largest registered owner, with 100.0%.

What is the revenue of SINGELSTAD HOLDING AS?

SINGELSTAD HOLDING AS had revenue of NOK 974 in 2024.

Where is SINGELSTAD HOLDING AS based?

SINGELSTAD HOLDING AS has its business address in Bergen.

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.