BIZTRAC BETA
Other postal and courier activities

HURV TRANSPORT AS

Org. no. 930574570 Limited company (AS) Froland Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −22,000
Equity NOK 36,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−22k kr).

HURV TRANSPORT AS is registered as a limited company in Froland, Agder with organisation number 930574570. The business is classified under other postal and courier activities (NACE 53.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Distribusjon, transport og konsulentvirksomhet og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −22,000
Equity
NOK 36,000
Est. value
NOK 537,000

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.8%
Weak
Equity as a share of total capital

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

Who owns HURV TRANSPORT AS?

NILS OLAF HURV
HURV TRANSPORT AS
NOK 1.1m rev. · NOK −22,000 profit

HURV TRANSPORT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HURV TRANSPORT AS

Who owns HURV TRANSPORT AS?

NILS OLAF HURV is the largest registered owner, with 75.0%.

What is the revenue of HURV TRANSPORT AS?

HURV TRANSPORT AS had revenue of NOK 1.1m in 2025.

Who is the general manager of HURV TRANSPORT AS?

Nils Olaf Hurv is registered as general manager of HURV TRANSPORT AS.

Where is HURV TRANSPORT AS based?

HURV TRANSPORT AS has its business address in Froland.

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.