BIZTRAC BETA
Freight transport by road

ULVSVÅG MULTISERVICE AS

Org. no. 935538416 Limited company (AS) Hamarøy Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 270,000
Operating profit NOK 97,000
Equity NOK 73,000
Incorporated 2025
Share capital NOK 30,000

ULVSVÅG MULTISERVICE AS is registered as a limited company in Hamarøy, Nordland with organisation number 935538416. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Transport, kjøring av stein og grus, snørydding og anleggsarbeid med hjullaster og planeringsarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 270,000 in revenue and NOK 97,000 in operating profit.

Key figures · 2025

Revenue
NOK 270,000
Operating profit
NOK 97,000
Equity
NOK 73,000
Est. value
NOK 324,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ULVSVÅG MULTISERVICE AS?

OLE MARTIN SKARDING
ULVSVÅG MULTISERVICE AS
NOK 270,000 rev. · NOK 97,000 profit

ULVSVÅG MULTISERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ULVSVÅG MULTISERVICE AS

Who owns ULVSVÅG MULTISERVICE AS?

OLE MARTIN SKARDING is the largest registered owner, with 100.0%.

What is the revenue of ULVSVÅG MULTISERVICE AS?

ULVSVÅG MULTISERVICE AS had revenue of NOK 270,000 in 2025.

Who is the general manager of ULVSVÅG MULTISERVICE AS?

Ole Martin Skarding is registered as general manager of ULVSVÅG MULTISERVICE AS.

Where is ULVSVÅG MULTISERVICE AS based?

ULVSVÅG MULTISERVICE AS has its business address in Ulvsvåg.

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.