BIZTRAC BETA
Uoppgitt

SKIRI INVEST AS

Org. no. 923128166 Limited company (AS) Ålesund Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 215,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

SKIRI INVEST AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 923128166. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i eiendom, aksjer og verdipapirer, samt annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 215,000
Est. value
NOK 672,000

Financial health · 2025

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

Who owns SKIRI INVEST AS?

LINN CHRISTIN OSNES SKIRI
SKIRI INVEST AS
NOK 0 rev. · NOK −5,000 profit

SKIRI INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SKIRI INVEST AS own?

SKIRI INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SKIRI INVEST AS

Who owns SKIRI INVEST AS?

LINN CHRISTIN OSNES SKIRI is the largest registered owner, with 100.0%.

What is the revenue of SKIRI INVEST AS?

SKIRI INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of SKIRI INVEST AS?

Linn Christin Osnes Skiri is registered as general manager of SKIRI INVEST AS.

Where is SKIRI INVEST AS based?

SKIRI INVEST AS has its business address in Ålesund.

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.