BIZTRAC BETA
Machining of metals

STAPU SVEISEKONSTRUKSJONER AS

Org. no. 980897257 Limited company (AS) Trondheim Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 686,000
Operating profit NOK −45,000
Equity NOK 6.1m
Incorporated 1999
Share capital NOK 101,000

Signals

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

STAPU SVEISEKONSTRUKSJONER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 980897257. The business is classified under machining of metals (NACE 25.530). The company was incorporated in 1999. Registered share capital is NOK 101,000, divided into 1010 shares. The company's stated purpose is: “Handelsvirksomhet samt hva hermed står i naturlig forbindelse, herunder delta i annen virksomhet gjennom aksjer eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 686,000 in revenue and NOK −45,000 in operating profit.

Key figures · 2024

Revenue
NOK 686,000
Operating profit
NOK −45,000
Equity
NOK 6.1m
Est. value
NOK 5.7m

Financial health · 2024

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

Who owns STAPU SVEISEKONSTRUKSJONER AS?

BJØRG OLUFSEN LÜDERS
STAPU SVEISEKONSTRUKSJONER AS
NOK 686,000 rev. · NOK −45,000 profit

STAPU SVEISEKONSTRUKSJONER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAPU SVEISEKONSTRUKSJONER AS

Who owns STAPU SVEISEKONSTRUKSJONER AS?

BJØRG OLUFSEN LÜDERS is the largest registered owner, with 100.0%.

What is the revenue of STAPU SVEISEKONSTRUKSJONER AS?

STAPU SVEISEKONSTRUKSJONER AS had revenue of NOK 686,000 in 2024.

Where is STAPU SVEISEKONSTRUKSJONER AS based?

STAPU SVEISEKONSTRUKSJONER AS has its business address in Trondheim.

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.