BIZTRAC BETA
Freight transport by road

DIGRE TRANSPORT AS

Org. no. 968975994 Limited company (AS) Midtre Gauldal Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 122.9m
Operating profit NOK 2.8m
Equity NOK 10.3m
Incorporated 1994
Employees 85
Share capital NOK 300,000

DIGRE TRANSPORT AS is registered as a limited company in Midtre Gauldal, Trøndelag with organisation number 968975994. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1994 and has 85 registered employees. Registered share capital is NOK 300,000, divided into 3000 shares. The company's stated purpose is: “Lastebiltransport og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 122.9m in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 122.9m
Operating profit
NOK 2.8m
Equity
NOK 10.3m
Est. value
NOK 13.3m

Financial health · 2025

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

Who owns DIGRE TRANSPORT AS?

HANS DIGRE
DIGRE TRANSPORT AS
NOK 122.9m rev. · NOK 2.8m profit

DIGRE TRANSPORT AS has 6 registered shareholders:

All shareholders and roles →

Which companies does DIGRE TRANSPORT AS own?

DIGRE TRANSPORT AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about DIGRE TRANSPORT AS

Who owns DIGRE TRANSPORT AS?

HANS DIGRE is the largest registered owner, with 38.5%.

What is the revenue of DIGRE TRANSPORT AS?

DIGRE TRANSPORT AS had revenue of NOK 122.9m in 2024.

Who is the general manager of DIGRE TRANSPORT AS?

Øystein Digre is registered as general manager of DIGRE TRANSPORT AS.

Where is DIGRE TRANSPORT AS based?

DIGRE TRANSPORT AS has its business address in Singsås.

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.