BIZTRAC BETA
Legal activities

ADVOKATFIRMAET ØYVIND BERRE AS

Org. no. 817785522 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 4.6m
Operating profit NOK 2.8m
Equity NOK 36,000
Incorporated 2016
Share capital NOK 30,000

ADVOKATFIRMAET ØYVIND BERRE AS is registered as a limited company in Oslo, Oslo with organisation number 817785522. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Advokatvirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.6m in revenue and NOK 2.8m in operating profit.

Key figures · 2025

Revenue
NOK 4.6m
Operating profit
NOK 2.8m
Equity
NOK 36,000
Est. value
NOK 8.4m

Financial health · 2025

Liquidity
0.99
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ADVOKATFIRMAET ØYVIND BERRE AS?

ØYVIND GLADHAUG BERRE
ADVOKATFIRMAET ØYVIND BERRE AS
NOK 4.6m rev. · NOK 2.8m profit

ADVOKATFIRMAET ØYVIND BERRE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ADVOKATFIRMAET ØYVIND BERRE AS own?

ADVOKATFIRMAET ØYVIND BERRE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ADVOKATFIRMAET ØYVIND BERRE AS

Who owns ADVOKATFIRMAET ØYVIND BERRE AS?

ØYVIND GLADHAUG BERRE is the largest registered owner, with 100.0%.

What is the revenue of ADVOKATFIRMAET ØYVIND BERRE AS?

ADVOKATFIRMAET ØYVIND BERRE AS had revenue of NOK 4.6m in 2025.

Where is ADVOKATFIRMAET ØYVIND BERRE AS based?

ADVOKATFIRMAET ØYVIND BERRE 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 15.06.2026.

Report a problem

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