BIZTRAC BETA
Legal activities

ADVOKATFIRMAET BRULAND OG FARSTAD AS

Org. no. 826867302 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 308,000
Equity NOK 301,000
Incorporated 2021
Share capital NOK 50,000

ADVOKATFIRMAET BRULAND OG FARSTAD AS is registered as a limited company in Oslo, Oslo with organisation number 826867302. The business is classified under legal activities (NACE 69.100). The company was incorporated in 2021. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Advokatvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 308,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 308,000
Equity
NOK 301,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns ADVOKATFIRMAET BRULAND OG FARSTAD AS?

THORLEIF GUNNAR BRULAND
ADVOKATFIRMAET BRULAND OG FARSTAD AS
NOK 1.4m rev. · NOK 308,000 profit

ADVOKATFIRMAET BRULAND OG FARSTAD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ADVOKATFIRMAET BRULAND OG FARSTAD AS

Who owns ADVOKATFIRMAET BRULAND OG FARSTAD AS?

THORLEIF GUNNAR BRULAND is the largest registered owner, with 50.0%.

What is the revenue of ADVOKATFIRMAET BRULAND OG FARSTAD AS?

ADVOKATFIRMAET BRULAND OG FARSTAD AS had revenue of NOK 1.4m in 2025.

Who is the general manager of ADVOKATFIRMAET BRULAND OG FARSTAD AS?

Thorleif Gunnar Bruland is registered as general manager of ADVOKATFIRMAET BRULAND OG FARSTAD AS.

Where is ADVOKATFIRMAET BRULAND OG FARSTAD AS based?

ADVOKATFIRMAET BRULAND OG FARSTAD 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.