BIZTRAC BETA
Painting and glazing

GLASSPESIALISTEN BODØ AS

Org. no. 914004144 Limited company (AS) Bodø Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK −75,000
Equity NOK 280,000
Incorporated 2014
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−75k kr).

GLASSPESIALISTEN BODØ AS is registered as a limited company in Bodø, Nordland with organisation number 914004144. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2014. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Salg og montasje av glass, vinduer, innglassing, solavskjerming og annen tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −75,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK −75,000
Equity
NOK 280,000
Est. value
NOK 953,000

Financial health · 2025

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

Who owns GLASSPESIALISTEN BODØ AS?

MORTEN LANGNES
GLASSPESIALISTEN BODØ AS
NOK 2.4m rev. · NOK −75,000 profit

GLASSPESIALISTEN BODØ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GLASSPESIALISTEN BODØ AS

Who owns GLASSPESIALISTEN BODØ AS?

MORTEN LANGNES is the largest registered owner, with 100.0%.

What is the revenue of GLASSPESIALISTEN BODØ AS?

GLASSPESIALISTEN BODØ AS had revenue of NOK 2.4m in 2025.

Who is the general manager of GLASSPESIALISTEN BODØ AS?

Morten Langnes is registered as general manager of GLASSPESIALISTEN BODØ AS.

Where is GLASSPESIALISTEN BODØ AS based?

GLASSPESIALISTEN BODØ AS has its business address in Bodø.

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.