BIZTRAC BETA
COMPANY REGISTER PROFILE
889699442 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Painting and glazing

DYRDAL AS

Org. no. 889699442 Limited company (AS) Vinje Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 6.0m
Operating profit NOK 1.1m
Equity NOK 2.6m
Incorporated 2006
Share capital NOK 30,000

DYRDAL AS is registered as a limited company in Vinje, Telemark with organisation number 889699442. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 2006. Registered share capital is NOK 30,000, divided into 150 shares. The company's stated purpose is: “Kjøp og sal av bygningsartiklar og formidling av tenester knytt til hus- og hyttebygging, herunder torvindustri, salg av Teletorv Torvtak, jordforedling, samt kjøp og salg av bygg og tomter/eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
▲ +14 %
Operating profit
NOK 1.1m
▲ +92 %
Equity
NOK 2.6m
▲ +28 %
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
7.51
Very good
Current assets ÷ current liabilities
Profitability
12.0%
Good
Return on total assets
Solidity
27.7%
Good
Equity as a share of total capital

Who owns DYRDAL AS?

DYRDAL AS
NOK 6.0m rev. · NOK 1.1m profit

DYRDAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DYRDAL AS own?

DYRDAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DYRDAL AS

Who owns DYRDAL AS?

ASBJØRN DYRDAL is the largest registered owner, with 100.0%.

What is the revenue of DYRDAL AS?

DYRDAL AS had revenue of NOK 6.0m in 2025.

Who is the general manager of DYRDAL AS?

Asbjørn Dyrdal is registered as general manager of DYRDAL AS.

Where is DYRDAL AS based?

DYRDAL AS has its business address in Vinje.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.