BIZTRAC BETA
COMPANY REGISTER PROFILE
989231278 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

SVARSTAD BRUK AS

Org. no. 989231278 Limited company (AS) Stryn Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 49,000
Operating profit NOK −113,000
Equity NOK 42.5m
Incorporated 2005
Share capital NOK 2.9m

Signals

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

SVARSTAD BRUK AS is registered as a limited company in Stryn, Vestland with organisation number 989231278. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 2.9m, divided into 100 shares. The company's stated purpose is: “Kjøp, og salg av verdipapirer og fast eiendom, og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 49,000 in revenue and NOK −113,000 in operating profit.

Key figures · 2025

Revenue
NOK 49,000
▼ −60 %
Operating profit
NOK −113,000
▲ +61 %
Equity
NOK 42.5m
▲ +3 %
Est. value
NOK 36.5m

Financial health · 2025

Liquidity
15.08
Very good
Current assets ÷ current liabilities
Profitability
9.4%
Satisfactory
Return on total assets
Solidity
93.9%
Very good
Equity as a share of total capital

Who owns SVARSTAD BRUK AS?

SVARSTAD BRUK AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SVARSTAD BRUK AS own?

SVARSTAD BRUK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SVARSTAD BRUK AS

Who owns SVARSTAD BRUK AS?

GUNNAR SVARSTAD is the largest registered owner, with 42.0%.

What is the revenue of SVARSTAD BRUK AS?

SVARSTAD BRUK AS had revenue of NOK 49,000 in 2025.

Where is SVARSTAD BRUK AS based?

SVARSTAD BRUK AS has its business address in Stryn.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.