BIZTRAC BETA
Repair and maintenance of motor vehicles

AS INSIGNIA

Org. no. 979474075 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 372.4m
Operating profit NOK 10.6m
Equity NOK 17.1m
Incorporated 1997
Employees 87
Share capital NOK 3.7m

AS INSIGNIA is registered as a limited company in Oslo, Oslo with organisation number 979474075. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 1997 and has 87 registered employees. Registered share capital is NOK 3.7m, divided into 133000 shares. The company's stated purpose is: “Handel, produksjon og annen økonomisk virksomhet, herunder deltagelse i norske og utenlandske selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 372.4m in revenue and NOK 10.6m in operating profit.

Key figures · 2024

Revenue
NOK 372.4m
Operating profit
NOK 10.6m
Equity
NOK 17.1m
Est. value
NOK 36.4m

Financial health · 2024

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

Who owns AS INSIGNIA?

BILIA NORGE AS
AS INSIGNIA
NOK 372.4m rev. · NOK 10.6m profit

AS INSIGNIA has 1 registered shareholder:

All shareholders and roles →

Which companies does AS INSIGNIA own?

AS INSIGNIA holds stakes in 2 companies:

See the full ownership structure →

Group structure

AS INSIGNIA er morselskap for 2 datterselskaper:

Frequently asked questions about AS INSIGNIA

Who owns AS INSIGNIA?

BILIA NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of AS INSIGNIA?

AS INSIGNIA had revenue of NOK 372.4m in 2024.

Who is the general manager of AS INSIGNIA?

Hans Ole Bakken is registered as general manager of AS INSIGNIA.

Where is AS INSIGNIA based?

AS INSIGNIA 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.