BIZTRAC BETA
Repair and maintenance of motor vehicles

BRIAC AS

Org. no. 920163904 Limited company (AS) Elverum Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 382,000
Equity NOK 67,000
Incorporated 2017
Share capital NOK 30,000

BRIAC AS is registered as a limited company in Elverum, Innlandet with organisation number 920163904. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Vedlikehold og reparasjon av motorvogn samt alt som hører naturlig til dette, unntatt motorsykler, herunder skifte og reparasjon av bilglass, vask og bilpleie. Selskapet vil kunne drive budtjenester i tilknytning til hovedvirksomheten, godstransport på vei samt fremleie av næringslokaler.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 382,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 382,000
Equity
NOK 67,000
Est. value
NOK 1.3m

Financial health · 2025

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

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

Who owns BRIAC AS?

BRAATEN INVEST AS
BRIAC AS
NOK 2.3m rev. · NOK 382,000 profit

BRIAC AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRIAC AS

Who owns BRIAC AS?

BRAATEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of BRIAC AS?

BRIAC AS had revenue of NOK 2.3m in 2025.

Who is the general manager of BRIAC AS?

Øyvind Braaten is registered as general manager of BRIAC AS.

Where is BRIAC AS based?

BRIAC AS has its business address in Elverum.

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.