BIZTRAC BETA
Other captive investment companies

PER SANDE AS

Org. no. 813391422 Limited company (AS) Stavanger Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 768,000
Incorporated 2014
Share capital NOK 90,000

Signals

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

PER SANDE AS is registered as a limited company in Stavanger, Rogaland with organisation number 813391422. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 90,000, divided into 90 shares. The company's stated purpose is: “Investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 768,000
Est. value
NOK 701,000

Financial health · 2025

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

Who owns PER SANDE AS?

PER SANDE
PER SANDE AS
NOK 0 rev. · NOK −10,000 profit

PER SANDE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PER SANDE AS own?

PER SANDE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PER SANDE AS

Who owns PER SANDE AS?

PER SANDE is the largest registered owner, with 100.0%.

What is the revenue of PER SANDE AS?

PER SANDE AS had revenue of NOK 0 in 2025.

Who is the general manager of PER SANDE AS?

Per Sande is registered as general manager of PER SANDE AS.

Where is PER SANDE AS based?

PER SANDE AS has its business address in Stavanger.

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.