BIZTRAC BETA
Other captive investment companies

SAASTAD INVEST AS

Org. no. 912482081 Limited company (AS) Moss Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK 35,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

SAASTAD INVEST AS is registered as a limited company in Moss, Østfold with organisation number 912482081. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i verdipapir, aksjer og andeler i annen virksomhet, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 35,000
Est. value
NOK 2.9m

Financial health · 2024

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

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

Who owns SAASTAD INVEST AS?

PER CHRISTIAN SAASTAD
SAASTAD INVEST AS
NOK 0 rev. · NOK −5,000 profit

SAASTAD INVEST AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SAASTAD INVEST AS own?

SAASTAD INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SAASTAD INVEST AS

Who owns SAASTAD INVEST AS?

PER CHRISTIAN SAASTAD is the largest registered owner, with 51.0%.

What is the revenue of SAASTAD INVEST AS?

SAASTAD INVEST AS had revenue of NOK 0 in 2024.

Where is SAASTAD INVEST AS based?

SAASTAD INVEST AS has its business address in Dilling.

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.