BIZTRAC BETA
Painting and glazing

TOM'S GLASS AS

Org. no. 980270408 Limited company (AS) Alstahaug Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 5.9m
Operating profit NOK 1.3m
Equity NOK 3.6m
Incorporated 1998
Share capital NOK 142,000

TOM'S GLASS AS is registered as a limited company in Alstahaug, Nordland with organisation number 980270408. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 1998. Registered share capital is NOK 142,000, divided into 142 shares. The company's stated purpose is: “Salg/montasje av glass, vinduer og bilglass. Kjøpe og selge nye og brukte biler. Utleie av egen eller leid fast eiendom. Kjøp og salg av aksjer, obligasjoner og andre finansielle instrumenter, samt annen virksomhet som naturlig faller inn under dette ved aksjekjøp eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.9m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 5.9m
Operating profit
NOK 1.3m
Equity
NOK 3.6m
Est. value
NOK 5.8m

Financial health · 2025

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

Who owns TOM'S GLASS AS?

SVEIN JOHNNY JOHANSEN
TOM'S GLASS AS
NOK 5.9m rev. · NOK 1.3m profit

TOM'S GLASS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOM'S GLASS AS

Who owns TOM'S GLASS AS?

SVEIN JOHNNY JOHANSEN is the largest registered owner, with 70.4%.

What is the revenue of TOM'S GLASS AS?

TOM'S GLASS AS had revenue of NOK 5.9m in 2025.

Who is the general manager of TOM'S GLASS AS?

Svein Johnny Johansen is registered as general manager of TOM'S GLASS AS.

Where is TOM'S GLASS AS based?

TOM'S GLASS AS has its business address in Sandnessjøen.

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.