BIZTRAC BETA
Wholesale of motor vehicle parts and accessories

HAWEKA NORGE AS

Org. no. 986405933 Limited company (AS) Oslo Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 3.7m
Operating profit NOK 352,000
Equity NOK 339,000
Incorporated 2003
Employees 6
Share capital NOK 100,000

HAWEKA NORGE AS is registered as a limited company in Oslo, Oslo with organisation number 986405933. The business is classified under wholesale of motor vehicle parts and accessories (NACE 46.720). The company was incorporated in 2003 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Import og salg av varer og tjenester til bilverksteder, bilgummiverksteder og dekkimportører samt dertil hørende virksomhet. I tillegg driver selskapet med persontransport.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.7m in revenue and NOK 352,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.7m
Operating profit
NOK 352,000
Equity
NOK 339,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns HAWEKA NORGE AS?

TROND INGE GLEMMING
HAWEKA NORGE AS
NOK 3.7m rev. · NOK 352,000 profit

HAWEKA NORGE AS has 3 registered shareholders:

All shareholders and roles →

Which companies does HAWEKA NORGE AS own?

HAWEKA NORGE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HAWEKA NORGE AS

Who owns HAWEKA NORGE AS?

TROND INGE GLEMMING is the largest registered owner, with 70.0%.

What is the revenue of HAWEKA NORGE AS?

HAWEKA NORGE AS had revenue of NOK 3.7m in 2025.

Where is HAWEKA NORGE AS based?

HAWEKA NORGE 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.