BIZTRAC BETA
COMPANY REGISTER PROFILE
914620945 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

STISI AS

Org. no. 914620945 Limited company (AS) Alver Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −103,000
Equity NOK 25.3m
Incorporated 2014
Share capital NOK 146,000

Signals

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

STISI AS is registered as a limited company in Alver, Vestland with organisation number 914620945. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2014. Registered share capital is NOK 146,000, divided into 145 shares. The company's stated purpose is: “Investering i aksjer og andre verdipapirer samt hva som hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −103,000
▼ −9 %
Equity
NOK 25.3m
▲ +7 %
Est. value
NOK 24.0m

Financial health · 2025

Liquidity
391.87
Very good
Current assets ÷ current liabilities
Profitability
8.5%
Satisfactory
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns STISI AS?

STISI AS
· NOK −103,000 profit

STISI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STISI AS own?

STISI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STISI AS

Who owns STISI AS?

STIAN MEDBY BOGETVEDT is the largest registered owner, with 100.0%.

Where is STISI AS based?

STISI AS has its business address in Alversund.

Property

Business address Sethaugen 4, 5911 Alversund
Cadastral unit 4631-139/18/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.