BIZTRAC BETA
Site preparation

SØRE SUND AS

Org. no. 924297891 Limited company (AS) Sigdal Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −70,000
Equity NOK −261,000
Incorporated 2019
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−261k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−70k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SØRE SUND AS is registered as a limited company in Sigdal, Buskerud with organisation number 924297891. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer og eiendom og andre produkter/tjenester som naturlig hører sammen med dette, herunder delta i andre selskap med lignende virksomhet, kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2024

Operating profit
NOK −70,000
Equity
NOK −261,000

Financial health · 2024

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

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

Who owns SØRE SUND AS?

VEGARD TRØSENG GJELLUM
SØRE SUND AS
· NOK −70,000 profit

SØRE SUND AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SØRE SUND AS own?

SØRE SUND AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SØRE SUND AS

Who owns SØRE SUND AS?

VEGARD TRØSENG GJELLUM is the largest registered owner, with 100.0%.

Where is SØRE SUND AS based?

SØRE SUND AS has its business address in Prestfoss.

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.