BIZTRAC BETA
Demolition

SP-MASKIN AS

Org. no. 985411522 Limited company (AS) Harstad Incorporated 2003 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK −28,000
Equity NOK 15.4m
Incorporated 2003
Share capital NOK 2.1m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−28k kr).

SP-MASKIN AS is registered as a limited company in Harstad, Troms with organisation number 985411522. The business is classified under demolition (NACE 43.110). The company was incorporated in 2003. Registered share capital is NOK 2.1m, divided into 2100 shares. The company's stated purpose is: “Behandling og disponering av ikke-farlig avfall. Miljørydding/bearbeiding og behandling av brennbart avfall fra egne riveprosjekter og andre godkjente avfallsmottak, til energiformål. Maskinentreprenørvirksomhet, samt det som naturlig hører med.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK −28,000
Equity
NOK 15.4m
Est. value
NOK 7.9m

Financial health · 2024

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

Who owns SP-MASKIN AS?

STEINAR HUGO PEDERSEN
SP-MASKIN AS
NOK 1.1m rev. · NOK −28,000 profit

SP-MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SP-MASKIN AS own?

SP-MASKIN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SP-MASKIN AS

Who owns SP-MASKIN AS?

STEINAR HUGO PEDERSEN is the largest registered owner, with 100.0%.

What is the revenue of SP-MASKIN AS?

SP-MASKIN AS had revenue of NOK 1.1m in 2024.

Where is SP-MASKIN AS based?

SP-MASKIN AS has its business address in Harstad.

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.