BIZTRAC BETA
Uoppgitt

SØRENG HOLDING AS

Org. no. 889068612 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −17
Equity NOK −77,000
Incorporated 2005
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−77k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−17 kr).

SØRENG HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 889068612. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 500 shares. The company's stated purpose is: “Eierskap i andre selskaper samt investeringer i aksje- og valutamarkedet og det som direkte og indirekte har forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −17 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −17
Equity
NOK −77,000

Financial health · 2024

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

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

Who owns SØRENG HOLDING AS?

RIKARD CELIUS SØRENG
SØRENG HOLDING AS
NOK 0 rev. · NOK −17 profit

SØRENG HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SØRENG HOLDING AS own?

SØRENG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SØRENG HOLDING AS

Who owns SØRENG HOLDING AS?

RIKARD CELIUS SØRENG is the largest registered owner, with 50.0%.

What is the revenue of SØRENG HOLDING AS?

SØRENG HOLDING AS had revenue of NOK 0 in 2024.

Where is SØRENG HOLDING AS based?

SØRENG 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.