BIZTRAC BETA
Retail sale of motor vehicles

BRAGES BRUKTBIL AS

Org. no. 932613417 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 34.9m
Operating profit NOK 2.5m
Equity NOK 2.1m
Incorporated 2023
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BRAGES BRUKTBIL AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 932613417. The business is classified under retail sale of motor vehicles (NACE 47.810). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Reparasjon og salg av nye og brukte biler.”. The most recent filed accounts, for the 2024 financial year, show NOK 34.9m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 34.9m
Operating profit
NOK 2.5m
Equity
NOK 2.1m
Est. value
NOK 10.7m

Financial health · 2024

Liquidity
1.38
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.6%
Good
Equity as a share of total capital

Who owns BRAGES BRUKTBIL AS?

BRAGES HOLDING AS
BRAGES BRUKTBIL AS
NOK 34.9m rev. · NOK 2.5m profit

BRAGES BRUKTBIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRAGES BRUKTBIL AS

Who owns BRAGES BRUKTBIL AS?

BRAGES HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of BRAGES BRUKTBIL AS?

BRAGES BRUKTBIL AS had revenue of NOK 34.9m in 2024.

Who is the general manager of BRAGES BRUKTBIL AS?

Kurt Hadrich Huke is registered as general manager of BRAGES BRUKTBIL AS.

Where is BRAGES BRUKTBIL AS based?

BRAGES BRUKTBIL AS has its business address in Ålesund.

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.