BIZTRAC BETA
Wholesale of wood, construction materials and sanitary equipment

BILLAKKSPESIALISTEN TROMSØ AS

Org. no. 980394727 Limited company (AS) Tromsø Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 10.3m
Operating profit NOK 1.7m
Equity NOK 2.1m
Incorporated 1998
Share capital NOK 250,000

BILLAKKSPESIALISTEN TROMSØ AS is registered as a limited company in Tromsø, Troms with organisation number 980394727. The business is classified under wholesale of wood, construction materials and sanitary equipment (NACE 46.830). The company was incorporated in 1998. Registered share capital is NOK 250,000, divided into 100 shares. The company's stated purpose is: “Salg av billakk med tilhørende produkter.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.3m in revenue and NOK 1.7m in operating profit.

Key figures · 2024

Revenue
NOK 10.3m
Operating profit
NOK 1.7m
Equity
NOK 2.1m
Est. value
NOK 6.6m

Financial health · 2024

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

Who owns BILLAKKSPESIALISTEN TROMSØ AS?

STIG MORTENSEN
BILLAKKSPESIALISTEN TROMSØ AS
NOK 10.3m rev. · NOK 1.7m profit

BILLAKKSPESIALISTEN TROMSØ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BILLAKKSPESIALISTEN TROMSØ AS

Who owns BILLAKKSPESIALISTEN TROMSØ AS?

STIG MORTENSEN is the largest registered owner, with 50.0%.

What is the revenue of BILLAKKSPESIALISTEN TROMSØ AS?

BILLAKKSPESIALISTEN TROMSØ AS had revenue of NOK 10.3m in 2024.

Who is the general manager of BILLAKKSPESIALISTEN TROMSØ AS?

Stig Mortensen is registered as general manager of BILLAKKSPESIALISTEN TROMSØ AS.

Where is BILLAKKSPESIALISTEN TROMSØ AS based?

BILLAKKSPESIALISTEN TROMSØ AS has its business address in Tromsø.

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.