BIZTRAC BETA
Repair and maintenance of motor vehicles

GLASS SPECIALISTS NORWAY AS

Org. no. 916902271 Limited company (AS) Haugesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −1.3m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,3 mill kr).

GLASS SPECIALISTS NORWAY AS is registered as a limited company in Haugesund, Rogaland with organisation number 916902271. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Reparasjon av bilglass samt annen virksomhet som naturlig hører inn under dette samt å kunne gjøre investeringer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −1.3m

Financial health · 2025

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

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

Who owns GLASS SPECIALISTS NORWAY AS?

SVEIN MORTEN HAGEN
GLASS SPECIALISTS NORWAY AS
NOK 0 rev. · NOK 0 profit

GLASS SPECIALISTS NORWAY AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about GLASS SPECIALISTS NORWAY AS

Who owns GLASS SPECIALISTS NORWAY AS?

SVEIN MORTEN HAGEN is the largest registered owner, with 33.3%.

What is the revenue of GLASS SPECIALISTS NORWAY AS?

GLASS SPECIALISTS NORWAY AS had revenue of NOK 0 in 2025.

Where is GLASS SPECIALISTS NORWAY AS based?

GLASS SPECIALISTS NORWAY AS has its business address in Haugesund.

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.