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

PYROLA AS

Org. no. 920770177 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −623,000
Equity NOK 92.6m
Incorporated 2018
Share capital NOK 250,000

Signals

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

PYROLA AS is registered as a limited company in Oslo, Oslo with organisation number 920770177. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Å eie og investere i aksjer, samt alt hva hermed står i forbindelse.”.

Key figures · 2025

Operating profit
NOK −623,000
▼ −51 %
Equity
NOK 92.6m
▼ −0 %
Est. value
NOK 106.9m

Financial health · 2025

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

Who owns PYROLA AS?

PYROLA AS
· NOK −623,000 profit

PYROLA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does PYROLA AS own?

PYROLA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PYROLA AS

Who owns PYROLA AS?

JENS PETTER VISTE KROEPELIEN is the largest registered owner, with 100.0%.

Where is PYROLA AS based?

PYROLA AS has its business address in Oslo.

Property

Business address Åmotveien 2B, 0880 Oslo
Cadastral unit 301-54/353/0/0
Building Tomannsbolig, vertikal · 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.