BIZTRAC BETA
Repair and maintenance of civilian ships and boats

TROMSØ MOTORSERVICE AS

Org. no. 992227923 Limited company (AS) Tromsø Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 7.2m
Operating profit NOK 339,000
Equity NOK 8.3m
Incorporated 2008
Employees 6
Share capital NOK 100,000

TROMSØ MOTORSERVICE AS is registered as a limited company in Tromsø, Troms with organisation number 992227923. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2008 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Service og reparasjon av dieselmotorer, skipsmotorer samt annet som hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.2m in revenue and NOK 339,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.2m
Operating profit
NOK 339,000
Equity
NOK 8.3m
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns TROMSØ MOTORSERVICE AS?

ODD IVAR OLSEN
TROMSØ MOTORSERVICE AS
NOK 7.2m rev. · NOK 339,000 profit

TROMSØ MOTORSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TROMSØ MOTORSERVICE AS

Who owns TROMSØ MOTORSERVICE AS?

ODD IVAR OLSEN is the largest registered owner, with 100.0%.

What is the revenue of TROMSØ MOTORSERVICE AS?

TROMSØ MOTORSERVICE AS had revenue of NOK 7.2m in 2024.

Who is the general manager of TROMSØ MOTORSERVICE AS?

Odd Ivar Olsen is registered as general manager of TROMSØ MOTORSERVICE AS.

Where is TROMSØ MOTORSERVICE AS based?

TROMSØ MOTORSERVICE AS has its business address in Tomasjord.

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.