BIZTRAC BETA
Other education activities

SARABY-SCHIAGER INVEST AS

Org. no. 930188352 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −66
Equity NOK 333,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

SARABY-SCHIAGER INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 930188352. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Salg av produkter og tjenester, samt rådgivning og opplæring innen økonomi og administrasjon, samt investeringer i fast eiendom, aksjer eller andeler i andre selskaper av enhver art.”.

Key figures · 2024

Operating profit
NOK −66
Equity
NOK 333,000
Est. value
NOK 4.5m

Financial health · 2024

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

Who owns SARABY-SCHIAGER INVEST AS?

KNUT-ALEXANDER SCHIAGER
SARABY-SCHIAGER INVEST AS
· NOK −66 profit

SARABY-SCHIAGER INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SARABY-SCHIAGER INVEST AS own?

SARABY-SCHIAGER INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SARABY-SCHIAGER INVEST AS

Who owns SARABY-SCHIAGER INVEST AS?

KNUT-ALEXANDER SCHIAGER is the largest registered owner, with 100.0%.

Who is the general manager of SARABY-SCHIAGER INVEST AS?

Knut-Alexander Schiager is registered as general manager of SARABY-SCHIAGER INVEST AS.

Where is SARABY-SCHIAGER INVEST AS based?

SARABY-SCHIAGER INVEST AS has its business address in Lommedalen.

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.