BIZTRAC BETA
COMPANY REGISTER PROFILE
928873552 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Dental practice care activities

LOA AS

Org. no. 928873552 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −71,000
Equity NOK 19.9m
Incorporated 2022
Share capital NOK 3.3m

Signals

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

LOA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928873552. The business is classified under dental practice care activities (NACE 86.230). The company was incorporated in 2022. Registered share capital is NOK 3.3m, divided into 3348 shares. The company's stated purpose is: “Investeringer og deltakelse i andre selskap.”.

Key figures · 2025

Operating profit
NOK −71,000
▼ −20 %
Equity
NOK 19.9m
▲ +693 %
Est. value
NOK 30.8m

Financial health · 2025

Liquidity
2.25
Very good
Current assets ÷ current liabilities
Profitability
0.4%
Not satisfactory
Return on total assets
Solidity
57.6%
Very good
Equity as a share of total capital

Who owns LOA AS?

LOA AS has 7 registered shareholders:

All shareholders and roles →

Which companies does LOA AS own?

LOA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LOA AS

Who owns LOA AS?

APROKSIMAL AS is the largest registered owner, with 29.9%.

Where is LOA AS based?

LOA AS has its business address in Trondheim.

Property

Business address Åsbakken 12, 7043 Trondheim
Cadastral unit 5001-11/23/0/0
Building Enebolig · 1 unit

9 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.