BIZTRAC BETA
Freight transport by road

HASKO MILJØ SUNNMØRE AS

Org. no. 974426102 Limited company (AS) Sula Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 1.3m
Operating profit NOK −181,000
Equity NOK 292,000
Incorporated 1995
Share capital NOK 460,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−181k kr).

HASKO MILJØ SUNNMØRE AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 974426102. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1995. Registered share capital is NOK 460,000, divided into 230 shares. The company's stated purpose is: “Utføring av transporttjenester, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.3m in revenue and NOK −181,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.3m
Operating profit
NOK −181,000
Equity
NOK 292,000
Est. value
NOK 526,000

Financial health · 2024

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

Who owns HASKO MILJØ SUNNMØRE AS?

JONNY ANDRE SKORPEN
HASKO MILJØ SUNNMØRE AS
NOK 1.3m rev. · NOK −181,000 profit

HASKO MILJØ SUNNMØRE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HASKO MILJØ SUNNMØRE AS

Who owns HASKO MILJØ SUNNMØRE AS?

JONNY ANDRE SKORPEN is the largest registered owner, with 100.0%.

What is the revenue of HASKO MILJØ SUNNMØRE AS?

HASKO MILJØ SUNNMØRE AS had revenue of NOK 1.3m in 2024.

Who is the general manager of HASKO MILJØ SUNNMØRE AS?

Jonny Andre Skorpen is registered as general manager of HASKO MILJØ SUNNMØRE AS.

Where is HASKO MILJØ SUNNMØRE AS based?

HASKO MILJØ SUNNMØRE AS has its business address in Langevå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.