BIZTRAC BETA
Tax consultancy activity

BRICONSULT AS

Org. no. 953682842 Limited company (AS) Oslo Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK 458,000
Incorporated 1989
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2k kr).

BRICONSULT AS is registered as a limited company in Oslo, Oslo with organisation number 953682842. The business is classified under tax consultancy activity (NACE 69.203). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Forretningsførsel, kursvirksomhet, skatte- rådgivning, edb-rådgivning og annen konsulent- virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 458,000
Est. value
NOK 377,000

Financial health · 2024

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

Who owns BRICONSULT AS?

LARS HARALD BRINCHMANN
BRICONSULT AS
NOK 0 rev. · NOK −2,000 profit

BRICONSULT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BRICONSULT AS own?

BRICONSULT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BRICONSULT AS

Who owns BRICONSULT AS?

LARS HARALD BRINCHMANN is the largest registered owner, with 100.0%.

What is the revenue of BRICONSULT AS?

BRICONSULT AS had revenue of NOK 0 in 2024.

Who is the general manager of BRICONSULT AS?

Lars Harald Brinchmann is registered as general manager of BRICONSULT AS.

Where is BRICONSULT AS based?

BRICONSULT 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.