BIZTRAC BETA
Retail sale of clothing

PER SVARSTAD AS

Org. no. 943547955 Limited company (AS) Sula Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 600,000
Operating profit NOK 185,000
Equity NOK 3.5m
Incorporated 1987
Share capital NOK 100,000

PER SVARSTAD AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 943547955. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Drift av agenturer, forvaltning av fast eiendom herunder utleie, og for øvrig hva som måtte kunne stå i forbindelse med dette, også deltagelse helt eller delvis i andre selskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 600,000 in revenue and NOK 185,000 in operating profit.

Key figures · 2024

Revenue
NOK 600,000
Operating profit
NOK 185,000
Equity
NOK 3.5m
Est. value
NOK 2.2m

Financial health · 2024

Liquidity
-13.27
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
56.8%
Very good
Equity as a share of total capital

Who owns PER SVARSTAD AS?

EVA ODDNY SVARSTAD
PER SVARSTAD AS
NOK 600,000 rev. · NOK 185,000 profit

PER SVARSTAD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PER SVARSTAD AS own?

PER SVARSTAD AS holds a stake in 1 company:

See the full ownership structure →

Group structure

PER SVARSTAD AS er morselskap for 1 datterselskap:

Frequently asked questions about PER SVARSTAD AS

Who owns PER SVARSTAD AS?

EVA ODDNY SVARSTAD is the largest registered owner, with 100.0%.

What is the revenue of PER SVARSTAD AS?

PER SVARSTAD AS had revenue of NOK 600,000 in 2024.

Where is PER SVARSTAD AS based?

PER SVARSTAD AS has its business address in Langevåg.

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.