BIZTRAC BETA
Site preparation

DYBSJORD MASKIN AS

Org. no. 998182980 Limited company (AS) Hol Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 9.4m
Operating profit NOK 1.4m
Equity NOK 3.8m
Incorporated 2012
Employees 5
Share capital NOK 30,000

DYBSJORD MASKIN AS is registered as a limited company in Hol, Buskerud with organisation number 998182980. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Graving, transport, snørydding og annen entreprenørvirksomhet. Kjøp og salg av varer innenfor bransjen, kjøp og salg av fast eiendom, konsulenttjenester, underholdning, deltagelse i andre selskaper og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.4m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 9.4m
Operating profit
NOK 1.4m
Equity
NOK 3.8m
Est. value
NOK 6.2m

Financial health · 2025

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

Who owns DYBSJORD MASKIN AS?

MORTEN DYBSJORD
DYBSJORD MASKIN AS
NOK 9.4m rev. · NOK 1.4m profit

DYBSJORD MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DYBSJORD MASKIN AS

Who owns DYBSJORD MASKIN AS?

MORTEN DYBSJORD is the largest registered owner, with 80.0%.

What is the revenue of DYBSJORD MASKIN AS?

DYBSJORD MASKIN AS had revenue of NOK 9.4m in 2025.

Who is the general manager of DYBSJORD MASKIN AS?

Morten Dybsjord is registered as general manager of DYBSJORD MASKIN AS.

Where is DYBSJORD MASKIN AS based?

DYBSJORD MASKIN AS has its business address in Geilo.

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.