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

STØLANE HOLDING AS

Org. no. 918495231 Limited company (AS) Bømlo Incorporated 2017 Active
Ownership graph ↗
Equity NOK 7,000
Incorporated 2017
Share capital NOK 30,000

STØLANE HOLDING AS is registered as a limited company in Bømlo, Vestland with organisation number 918495231. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper, samt markedsbaserte obligasjoner og spareprodukter av ulike slag.”.

Key figures · 2025

Equity
NOK 7,000
▲ +0 %
Est. value
NOK 8,000

Financial health · 2025

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

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

Who owns STØLANE HOLDING AS?

STØLANE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STØLANE HOLDING AS own?

STØLANE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STØLANE HOLDING AS

Who owns STØLANE HOLDING AS?

ANDERS MARTIN HELLE is the largest registered owner, with 100.0%.

Where is STØLANE HOLDING AS based?

STØLANE HOLDING AS has its business address in Bremnes.

Property

Business address Stølane 34, 5430 Bremnes
Cadastral unit 4613-109/396/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.