BIZTRAC BETA
COMPANY REGISTER PROFILE
933241572 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Accounting and bookkeeping

AZS AS

Org. no. 933241572 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −60,000
Equity NOK 2.6m
Incorporated 2024
Share capital NOK 100,000

Signals

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

AZS AS is registered as a limited company in Stavanger, Rogaland with organisation number 933241572. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Eie og forvalte eierandeler i andre selskaper.”.

Former names: AZELO AS

Key figures · 2025

Operating profit
NOK −60,000
Equity
NOK 2.6m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns AZS AS?

AZS AS has 6 registered shareholders:

All shareholders and roles →

Which companies does AZS AS own?

AZS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AZS AS

Who owns AZS AS?

LINEOS AS is the largest registered owner, with 38.8%.

Where is AZS AS based?

AZS AS has its business address in Stavanger.

Property

Business address Reidar Berges gate 11, 4013 Stavanger
Cadastral unit 1103-52/589/0/0
Building Butikkbygning · 2 units

15 companies are registered at this address.

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.