BIZTRAC BETA
Freight transport by road

JOHAN DYBVAD AS

Org. no. 931712322 Limited company (AS) Malvik Incorporated 1981 Active
Ownership graph ↗
Revenue 2024 NOK 7.5m
Operating profit NOK 483,000
Equity NOK 29.3m
Incorporated 1981
Share capital NOK 100,000

JOHAN DYBVAD AS is registered as a limited company in Malvik, Trøndelag with organisation number 931712322. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 1981. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Transportvirksomhet, samt deltakelse i andre sel- skaper gjennom aksjetegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.5m in revenue and NOK 483,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.5m
Operating profit
NOK 483,000
Equity
NOK 29.3m
Est. value
NOK 17.5m

Financial health · 2024

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

Who owns JOHAN DYBVAD AS?

JO BØRGE DYBVAD
JOHAN DYBVAD AS
NOK 7.5m rev. · NOK 483,000 profit

JOHAN DYBVAD AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JOHAN DYBVAD AS own?

JOHAN DYBVAD AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

JOHAN DYBVAD AS er morselskap for 1 datterselskap:

Frequently asked questions about JOHAN DYBVAD AS

Who owns JOHAN DYBVAD AS?

JO BØRGE DYBVAD is the largest registered owner, with 50.0%.

What is the revenue of JOHAN DYBVAD AS?

JOHAN DYBVAD AS had revenue of NOK 7.5m in 2024.

Who is the general manager of JOHAN DYBVAD AS?

Sture Dybvad is registered as general manager of JOHAN DYBVAD AS.

Where is JOHAN DYBVAD AS based?

JOHAN DYBVAD AS has its business address in Hommelvik.

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.