BIZTRAC BETA
Site preparation

STAFSETH MASKIN AS

Org. no. 978689477 Limited company (AS) Ålesund Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 1.6m
Operating profit NOK 152,000
Equity NOK −307,000
Incorporated 1997
Share capital NOK 200,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−307k kr).

STAFSETH MASKIN AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 978689477. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1997. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Å drive maskinentreprenørvirksomhet og annet som naturlig følger av dette, samt å engasjere seg i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.6m in revenue and NOK 152,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.6m
Operating profit
NOK 152,000
Equity
NOK −307,000
Est. value
NOK 954,000

Financial health · 2025

Liquidity
0.54
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-83.8%
Weak
Equity as a share of total capital

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

Who owns STAFSETH MASKIN AS?

BJARNE STAFSETH
STAFSETH MASKIN AS
NOK 1.6m rev. · NOK 152,000 profit

STAFSETH MASKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STAFSETH MASKIN AS

Who owns STAFSETH MASKIN AS?

BJARNE STAFSETH is the largest registered owner, with 75.0%.

What is the revenue of STAFSETH MASKIN AS?

STAFSETH MASKIN AS had revenue of NOK 1.6m in 2025.

Who is the general manager of STAFSETH MASKIN AS?

Bjarne Stafseth is registered as general manager of STAFSETH MASKIN AS.

Where is STAFSETH MASKIN AS based?

STAFSETH MASKIN AS has its business address in Skodje.

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.