BIZTRAC BETA
Uoppgitt

SANIAS AS

Org. no. 831717432 Limited company (AS) Ørsta Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −903
Equity NOK 22,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

SANIAS AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 831717432. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere i selskap og eigedomar og alt anna som naturleg faller saman med dette, herunder å delta i andre selskap med liknande verksemd og kjøp og sal av aksjar.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −903 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −903
Equity
NOK 22,000
Est. value
NOK 26,000

Financial health · 2024

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

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

Who owns SANIAS AS?

MORTEN OSE
SANIAS AS
NOK 0 rev. · NOK −903 profit

SANIAS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SANIAS AS own?

SANIAS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SANIAS AS

Who owns SANIAS AS?

MORTEN OSE is the largest registered owner, with 100.0%.

What is the revenue of SANIAS AS?

SANIAS AS had revenue of NOK 0 in 2024.

Who is the general manager of SANIAS AS?

Morten Ose is registered as general manager of SANIAS AS.

Where is SANIAS AS based?

SANIAS AS has its business address in Ørsta.

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.