biztrac. BETA
COMPANY REGISTER PROFILE
833582852 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Legal activities

ADVOKATFIRMAET BRATLIEN AS

Org. no. 833582852 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 57.4m
Operating profit NOK 19.9m
Equity NOK 718,000
Incorporated 2024
Employees 21
Share capital NOK 30,000

ADVOKATFIRMAET BRATLIEN AS is registered as a limited company in Oslo, Oslo with organisation number 833582852. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2024 and has 21 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Advokatvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 57.4m in revenue and NOK 19.9m in operating profit.

Former names: ADVOKATFIRMAET BRATLIEN 1 AS

Key figures · 2025

Revenue
NOK 57.4m
▲ +33 %
Operating profit
NOK 19.9m
▲ +48 %
Equity
NOK 718,000
▲ +151 %
Est. value
NOK 58.0m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
70.5%
Very good
Return on total assets
Solidity
2.1%
Not satisfactory
Equity as a share of total capital

Who owns ADVOKATFIRMAET BRATLIEN AS?

ADVOKATFIRMAET BRATLIEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADVOKATFIRMAET BRATLIEN AS

Who owns ADVOKATFIRMAET BRATLIEN AS?

ADVB HOLDING AS is the largest registered owner, with 60.0%.

What is the revenue of ADVOKATFIRMAET BRATLIEN AS?

ADVOKATFIRMAET BRATLIEN AS had revenue of NOK 57.4m in 2025.

Who is the general manager of ADVOKATFIRMAET BRATLIEN AS?

Laila Afelad is registered as general manager of ADVOKATFIRMAET BRATLIEN AS.

Where is ADVOKATFIRMAET BRATLIEN AS based?

ADVOKATFIRMAET BRATLIEN AS has its business address in Oslo.

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

Report a problem

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