biztrac. BETA
COMPANY REGISTER PROFILE
917145806 ORG. NO. 2025 ACCOUNTS 10 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of civilian ships and boats

GMV SERVICE AS

Org. no. 917145806 Limited company (AS) Tjeldsund Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 28.2m
Operating profit NOK 334,000
Equity NOK 2.6m
Incorporated 2016
Employees 12
Share capital NOK 83,000

GMV SERVICE AS is registered as a limited company in Tjeldsund, Troms with organisation number 917145806. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2016 and has 12 registered employees. Registered share capital is NOK 83,000, divided into 2755 shares. The company's stated purpose is: “Reparasjon og vedlikehold av mindre skip”. The most recent filed accounts, for the 2025 financial year, show NOK 28.2m in revenue and NOK 334,000 in operating profit.

Former names: GROVFJORD SLIPP AS

Key figures · 2025

Revenue
NOK 28.2m
▲ +23 %
Operating profit
NOK 334,000
▼ −75 %
Equity
NOK 2.6m
▲ +15 %
Est. value
NOK 2.7m

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
2.9%
Weak
Return on total assets
Solidity
20.8%
Good
Equity as a share of total capital

Who owns GMV SERVICE AS?

GMV SERVICE AS
NOK 28.2m rev. · NOK 334,000 profit

GMV SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GMV SERVICE AS

Who owns GMV SERVICE AS?

GROVFJORD INDUSTRIER AS is the largest registered owner, with 100.0%.

What is the revenue of GMV SERVICE AS?

GMV SERVICE AS had revenue of NOK 28.2m in 2025.

Who is the general manager of GMV SERVICE AS?

Markus Shabani-Hansen is registered as general manager of GMV SERVICE AS.

Where is GMV SERVICE AS based?

GMV SERVICE AS has its business address in Grovfjord.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.