BIZTRAC BETA
Repair and maintenance of motor vehicles

GLASSPESIALISTEN AS

Org. no. 985231761 Limited company (AS) Asker Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK 758,000
Equity NOK 1.5m
Incorporated 2002
Share capital NOK 100,000

GLASSPESIALISTEN AS is registered as a limited company in Asker, Akershus with organisation number 985231761. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2002. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Arbeide med skifting og reparasjon av glass på biler og bygning, legging av mørk film på glass, gjøre investeringer, samt drive virksomhet innen beslektede områder.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK 758,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK 758,000
Equity
NOK 1.5m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns GLASSPESIALISTEN AS?

MORTEN LARNTVET LUNDSBAKKEN
GLASSPESIALISTEN AS
NOK 6.9m rev. · NOK 758,000 profit

GLASSPESIALISTEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GLASSPESIALISTEN AS

Who owns GLASSPESIALISTEN AS?

MORTEN LARNTVET LUNDSBAKKEN is the largest registered owner, with 55.0%.

What is the revenue of GLASSPESIALISTEN AS?

GLASSPESIALISTEN AS had revenue of NOK 6.9m in 2024.

Who is the general manager of GLASSPESIALISTEN AS?

Morten Larntvet Lundsbakken is registered as general manager of GLASSPESIALISTEN AS.

Where is GLASSPESIALISTEN AS based?

GLASSPESIALISTEN AS has its business address in Vollen.

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.