BIZTRAC BETA
Freight transport by road

HENRY DAMSGÅRD TRANSPORT AS

Org. no. 889746262 Limited company (AS) Klepp Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 21.7m
Operating profit NOK 2.7m
Equity NOK 12.8m
Incorporated 2006
Employees 9
Share capital NOK 100,000

HENRY DAMSGÅRD TRANSPORT AS is registered as a limited company in Klepp, Rogaland with organisation number 889746262. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2006 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Transportvirksomhet samt hva hermed står i forbindelse samt å delta i andre selskaper med lignende formål. ”. The most recent filed accounts, for the 2025 financial year, show NOK 21.7m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 21.7m
Operating profit
NOK 2.7m
Equity
NOK 12.8m
Est. value
NOK 16.4m

Financial health · 2025

Liquidity
4.05
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
77.0%
Very good
Equity as a share of total capital

Who owns HENRY DAMSGÅRD TRANSPORT AS?

HENRY DAMSGÅRD
HENRY DAMSGÅRD TRANSPORT AS
NOK 21.7m rev. · NOK 2.7m profit

HENRY DAMSGÅRD TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HENRY DAMSGÅRD TRANSPORT AS

Who owns HENRY DAMSGÅRD TRANSPORT AS?

HENRY DAMSGÅRD is the largest registered owner, with 100.0%.

What is the revenue of HENRY DAMSGÅRD TRANSPORT AS?

HENRY DAMSGÅRD TRANSPORT AS had revenue of NOK 21.7m in 2025.

Who is the general manager of HENRY DAMSGÅRD TRANSPORT AS?

Henry Damsgård is registered as general manager of HENRY DAMSGÅRD TRANSPORT AS.

Where is HENRY DAMSGÅRD TRANSPORT AS based?

HENRY DAMSGÅRD TRANSPORT AS has its business address in Kleppe.

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.