BIZTRAC BETA
Removal services

HOLFREIGHT AS

Org. no. 984989229 Limited company (AS) Ullensaker Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 11.3m
Operating profit NOK −714,000
Equity NOK 243,000
Incorporated 2002
Employees 6
Share capital NOK 450,000

Signals

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

HOLFREIGHT AS is registered as a limited company in Ullensaker, Akershus with organisation number 984989229. The business is classified under removal services (NACE 49.420). The company was incorporated in 2002 and has 6 registered employees. Registered share capital is NOK 450,000, divided into 4500 shares. The company's stated purpose is: “Utføre flyttetransport, annen transport med lastebil, drive handel med bilrekvisita og vaskemidler, eie aksjer/andeler i andre selskaper, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.3m in revenue and NOK −714,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.3m
Operating profit
NOK −714,000
Equity
NOK 243,000
Est. value
NOK 5.4m

Financial health · 2024

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

Who owns HOLFREIGHT AS?

HOLSHIP NORGE AS
HOLFREIGHT AS
NOK 11.3m rev. · NOK −714,000 profit

HOLFREIGHT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOLFREIGHT AS

Who owns HOLFREIGHT AS?

HOLSHIP NORGE AS is the largest registered owner, with 100.0%.

What is the revenue of HOLFREIGHT AS?

HOLFREIGHT AS had revenue of NOK 11.3m in 2024.

Who is the general manager of HOLFREIGHT AS?

Lars Kent Ranners is registered as general manager of HOLFREIGHT AS.

Where is HOLFREIGHT AS based?

HOLFREIGHT AS has its business address in Kløfta.

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.