BIZTRAC BETA
Retail sale of motor vehicles

BRUKTBILHALLEN AS

Org. no. 926324527 Limited company (AS) Voss Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 13.3m
Operating profit NOK −65,000
Equity NOK 803,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−65k kr).
  • Nylig endring 2026-02-27 Adresseendring registrert 2026-02-27.

BRUKTBILHALLEN AS is registered as a limited company in Voss, Vestland with organisation number 926324527. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp og salg av bruktbiler”. The most recent filed accounts, for the 2024 financial year, show NOK 13.3m in revenue and NOK −65,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.3m
Operating profit
NOK −65,000
Equity
NOK 803,000
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns BRUKTBILHALLEN AS?

SIMB INVEST AS
BRUKTBILHALLEN AS
NOK 13.3m rev. · NOK −65,000 profit

BRUKTBILHALLEN AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BRUKTBILHALLEN AS er morselskap for 1 datterselskap:

Frequently asked questions about BRUKTBILHALLEN AS

Who owns BRUKTBILHALLEN AS?

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

What is the revenue of BRUKTBILHALLEN AS?

BRUKTBILHALLEN AS had revenue of NOK 13.3m in 2024.

Who is the general manager of BRUKTBILHALLEN AS?

Stig Arne Brekkhus is registered as general manager of BRUKTBILHALLEN AS.

Where is BRUKTBILHALLEN AS based?

BRUKTBILHALLEN AS has its business address in Voss.

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.