BIZTRAC BETA
All other professional, scientific and technical activities n.e.c.

OAS INVESTMENTS AS

Org. no. 927009137 Limited company (AS) Alver Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −10,000
Equity NOK 3,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

OAS INVESTMENTS AS is registered as a limited company in Alver, Vestland with organisation number 927009137. The business is classified under all other professional, scientific and technical activities n.e.c. (NACE 74.990). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 3,000
Est. value
NOK 5,000

Financial health · 2024

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

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

Who owns OAS INVESTMENTS AS?

OLE ANDRE SKAGE
OAS INVESTMENTS AS
NOK 0 rev. · NOK −10,000 profit

OAS INVESTMENTS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OAS INVESTMENTS AS own?

OAS INVESTMENTS AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OAS INVESTMENTS AS

Who owns OAS INVESTMENTS AS?

OLE ANDRE SKAGE is the largest registered owner, with 100.0%.

What is the revenue of OAS INVESTMENTS AS?

OAS INVESTMENTS AS had revenue of NOK 0 in 2024.

Where is OAS INVESTMENTS AS based?

OAS INVESTMENTS AS has its business address in Frekhaug.

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.