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

ADLOR AS

Org. no. 922772614 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −60,000
Equity NOK 4.2m
Incorporated 2019
Share capital NOK 30,000

Signals

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

ADLOR AS is registered as a limited company in Bergen, Vestland with organisation number 922772614. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer.”.

Key figures · 2025

Operating profit
NOK −60,000
▲ +36 %
Equity
NOK 4.2m
▲ +10 %
Est. value
NOK 4.8m

Financial health · 2025

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

Who owns ADLOR AS?

ADLOR AS
· NOK −60,000 profit

ADLOR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ADLOR AS own?

ADLOR AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about ADLOR AS

Who owns ADLOR AS?

ALEKSANDER DIMITRI LANGESET OLSBØ RYE is the largest registered owner, with 100.0%.

Where is ADLOR AS based?

ADLOR AS has its business address in Bergen.

Property

Business address c/o Aleksander Olsbø Rye Solbakken 14, 5038 Bergen
Cadastral unit 4601-168/1675/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.