biztrac. BETA
COMPANY REGISTER PROFILE
833666762 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

DS MINING AS

Org. no. 833666762 Limited company (AS) Storfjord Incorporated 2024 Active
Revenue 2025 NOK 12.5m
Operating profit NOK 1.3m
Equity NOK 87,000
Incorporated 2024
Employees 9
Share capital NOK 30,000

DS MINING AS is registered as a limited company in Storfjord, Troms with organisation number 833666762. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2024 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Utleie av spesial kompetanse, bemanning og maskiner i anleggsbransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 12.5m
▲ +155 %
Operating profit
NOK 1.3m
▲ +1428 %
Equity
NOK 87,000
▼ −0 %
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
39.0%
Very good
Return on total assets
Solidity
2.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DS MINING AS?

DS MINING AS
NOK 12.5m rev. · NOK 1.3m profit

DS MINING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

DS MINING AS er morselskap for 5 datterselskaper:

Frequently asked questions about DS MINING AS

Who owns DS MINING AS?

DAM OG SJØPLASTRING AS is the largest registered owner, with 100.0%.

What is the revenue of DS MINING AS?

DS MINING AS had revenue of NOK 12.5m in 2025.

Who is the general manager of DS MINING AS?

Ståle Koht Hansen is registered as general manager of DS MINING AS.

Where is DS MINING AS based?

DS MINING AS has its business address in Skibotn.

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.