BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

ARENABRE AS

Org. no. 929050398 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 486,000
Equity NOK 695,000
Incorporated 2022
Share capital NOK 30,000

ARENABRE AS is registered as a limited company in Drammen, Buskerud with organisation number 929050398. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Legevirksomhet innen øyesykdommer og det som naturlig står i forbindelse med dette, samt investeringsvirksomhet og kjøp/salg av eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 486,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 486,000
Equity
NOK 695,000
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns ARENABRE AS?

ALEKSANDAR PAVLOVIC
ARENABRE AS
NOK 2.9m rev. · NOK 486,000 profit

ARENABRE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARENABRE AS own?

ARENABRE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARENABRE AS

Who owns ARENABRE AS?

ALEKSANDAR PAVLOVIC is the largest registered owner, with 100.0%.

What is the revenue of ARENABRE AS?

ARENABRE AS had revenue of NOK 2.9m in 2024.

Who is the general manager of ARENABRE AS?

Aleksandar Pavlovic is registered as general manager of ARENABRE AS.

Where is ARENABRE AS based?

ARENABRE AS has its business address in Drammen.

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

Report a problem

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