biztrac. BETA
COMPANY REGISTER PROFILE
958068484 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of machinery

DAG NORDSKOG AS

Org. no. 958068484 Limited company (AS) Tokke Incorporated 1990 Active
Revenue 2025 NOK 133,000
Operating profit NOK −15,000
Equity NOK 478,000
Incorporated 1990
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−15k kr).

DAG NORDSKOG AS is registered as a limited company in Tokke, Telemark with organisation number 958068484. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 1990. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Reparasjonsverkstad og det som naturleg høyrer til slik verksemd.”. The most recent filed accounts, for the 2025 financial year, show NOK 133,000 in revenue and NOK −15,000 in operating profit.

Key figures · 2025

Revenue
NOK 133,000
▼ −29 %
Operating profit
NOK −15,000
▲ +81 %
Equity
NOK 478,000
▼ −0 %
Est. value
NOK 324,000

Financial health · 2025

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

Who owns DAG NORDSKOG AS?

DAG NORDSKOG AS
NOK 133,000 rev. · NOK −15,000 profit

DAG NORDSKOG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAG NORDSKOG AS

Who owns DAG NORDSKOG AS?

Dag Torfinn Nordskog is the largest registered owner, with 100.0%.

What is the revenue of DAG NORDSKOG AS?

DAG NORDSKOG AS had revenue of NOK 133,000 in 2025.

Who is the general manager of DAG NORDSKOG AS?

Dag Torfinn Nordskog is registered as general manager of DAG NORDSKOG AS.

Where is DAG NORDSKOG AS based?

DAG NORDSKOG AS has its business address in Dalen.

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

Report a problem

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