BIZTRAC BETA
Legal activities

BRESTO ADVOKATFIRMA AS

Org. no. 933733637 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 151,000
Equity NOK 106,000
Incorporated 2024
Employees 8
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-07-28 Adresseendring registrert 2026-07-28.

BRESTO ADVOKATFIRMA AS is registered as a limited company in Bærum, Akershus with organisation number 933733637. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2024 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Advokatvirksomhet - juridisk og kommersiell rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 151,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 151,000
Equity
NOK 106,000
Est. value
NOK 793,000

Financial health · 2025

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
10.1%
Satisfactory
Equity as a share of total capital

Who owns BRESTO ADVOKATFIRMA AS?

BRESTO AS
BRESTO ADVOKATFIRMA AS
NOK 1.4m rev. · NOK 151,000 profit

BRESTO ADVOKATFIRMA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRESTO ADVOKATFIRMA AS

Who owns BRESTO ADVOKATFIRMA AS?

BRESTO AS is the largest registered owner, with 100.0%.

What is the revenue of BRESTO ADVOKATFIRMA AS?

BRESTO ADVOKATFIRMA AS had revenue of NOK 1.4m in 2025.

Who is the general manager of BRESTO ADVOKATFIRMA AS?

Ida Kristine Bakken Hjorteset is registered as general manager of BRESTO ADVOKATFIRMA AS.

Where is BRESTO ADVOKATFIRMA AS based?

BRESTO ADVOKATFIRMA AS has its business address in Lysaker.

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.