biztrac. BETA
COMPANY REGISTER PROFILE
935685486 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Uoppgitt

OLESTOLE HOLDING AS

Org. no. 935685486 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −11
Equity NOK 30,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

OLESTOLE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 935685486. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere og forvalte investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −11 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −11
Equity
NOK 30,000
Est. value
NOK 35,000

Financial health · 2025

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

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

Who owns OLESTOLE HOLDING AS?

OLESTOLE HOLDING AS
NOK 0 rev. · NOK −11 profit

OLESTOLE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLESTOLE HOLDING AS own?

OLESTOLE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLESTOLE HOLDING AS

Who owns OLESTOLE HOLDING AS?

Ole August Støle is the largest registered owner, with 100.0%.

What is the revenue of OLESTOLE HOLDING AS?

OLESTOLE HOLDING AS had revenue of NOK 0 in 2025.

Where is OLESTOLE HOLDING AS based?

OLESTOLE HOLDING AS has its business address in Oslo.

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

Report a problem

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