BIZTRAC BETA
Rental and operating of own or leased real estate

SØRE RAMSTAD HOLDING AS

Org. no. 930621315 Limited company (AS) Sigdal Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −6,000
Equity NOK 24,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SØRE RAMSTAD HOLDING AS is registered as a limited company in Sigdal, Buskerud with organisation number 930621315. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er investering i aksjer og fast eiendom, samt det som naturlig hører til under dette.”.

Key figures · 2025

Operating profit
NOK −6,000
Equity
NOK 24,000
Est. value
NOK 22,000

Financial health · 2025

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

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

Who owns SØRE RAMSTAD HOLDING AS?

JOKSTAD HOLDING AS
SØRE RAMSTAD HOLDING AS
· NOK −6,000 profit

SØRE RAMSTAD HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SØRE RAMSTAD HOLDING AS own?

SØRE RAMSTAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SØRE RAMSTAD HOLDING AS

Who owns SØRE RAMSTAD HOLDING AS?

JOKSTAD HOLDING AS is the largest registered owner, with 50.0%.

Who is the general manager of SØRE RAMSTAD HOLDING AS?

Elling Ramstad is registered as general manager of SØRE RAMSTAD HOLDING AS.

Where is SØRE RAMSTAD HOLDING AS based?

SØRE RAMSTAD HOLDING 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.