BIZTRAC BETA
Uoppgitt

S.SØRGAARD AS

Org. no. 929311914 Limited company (AS) Overhalla Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 9,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

S.SØRGAARD AS is registered as a limited company in Overhalla, Trøndelag with organisation number 929311914. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i aksjer, andre finansielle investeringer samt eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 9,000
Est. value
NOK 10,000

Financial health · 2025

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

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

Who owns S.SØRGAARD AS?

SIMEN ØVERENG SØRGAARD
S.SØRGAARD AS
NOK 0 rev. · NOK −4,000 profit

S.SØRGAARD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does S.SØRGAARD AS own?

S.SØRGAARD AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about S.SØRGAARD AS

Who owns S.SØRGAARD AS?

SIMEN ØVERENG SØRGAARD is the largest registered owner, with 100.0%.

What is the revenue of S.SØRGAARD AS?

S.SØRGAARD AS had revenue of NOK 0 in 2025.

Who is the general manager of S.SØRGAARD AS?

Simen Øvereng Sørgaard is registered as general manager of S.SØRGAARD AS.

Where is S.SØRGAARD AS based?

S.SØRGAARD AS has its business address in Skage I Namdalen.

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.