biztrac. BETA
COMPANY REGISTER PROFILE
921091664 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Freight transport by road

HASLEMO AS

Org. no. 921091664 Limited company (AS) Vindafjord Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 987,000
Operating profit NOK 121,000
Equity NOK −671,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−671k kr).

HASLEMO AS is registered as a limited company in Vindafjord, Rogaland with organisation number 921091664. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Lastebiltransport, utleie av arbeidskraft samt kjøp og salg av næringsutstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 987,000 in revenue and NOK 121,000 in operating profit.

Key figures · 2025

Revenue
NOK 987,000
▲ +79 %
Operating profit
NOK 121,000
▲ +143 %
Equity
NOK −671,000
▲ +12 %

Financial health · 2025

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
28.1%
Very good
Return on total assets
Solidity
-148.0%
Weak
Equity as a share of total capital

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

Who owns HASLEMO AS?

HASLEMO AS
NOK 987,000 rev. · NOK 121,000 profit

HASLEMO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HASLEMO AS

Who owns HASLEMO AS?

Jørgen Haslemo is the largest registered owner, with 100.0%.

What is the revenue of HASLEMO AS?

HASLEMO AS had revenue of NOK 987,000 in 2025.

Who is the general manager of HASLEMO AS?

Jørgen Haslemo is registered as general manager of HASLEMO AS.

Where is HASLEMO AS based?

HASLEMO AS has its business address in Øvre Vats.

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.