BIZTRAC BETA
Other specialised construction activities n.e.c.

NORDISK STILLAS AS

Org. no. 922539332 Limited company (AS) Ringsaker Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 5.9m
Operating profit NOK −179,000
Equity NOK 755,000
Incorporated 2019
Employees 6
Share capital NOK 30,000

Signals

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

NORDISK STILLAS AS is registered as a limited company in Ringsaker, Innlandet with organisation number 922539332. The business is classified under other specialised construction activities n.e.c. (NACE 43.990). The company was incorporated in 2019 and has 6 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Stillasmontering/demontering. Salg av stillastjenester. Stillasservice.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.9m in revenue and NOK −179,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.9m
Operating profit
NOK −179,000
Equity
NOK 755,000
Est. value
NOK 1.9m

Financial health · 2025

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
27.6%
Good
Equity as a share of total capital

Who owns NORDISK STILLAS AS?

DAVID PETERSEN
NORDISK STILLAS AS
NOK 5.9m rev. · NOK −179,000 profit

NORDISK STILLAS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NORDISK STILLAS AS

Who owns NORDISK STILLAS AS?

DAVID PETERSEN is the largest registered owner, with 100.0%.

What is the revenue of NORDISK STILLAS AS?

NORDISK STILLAS AS had revenue of NOK 5.9m in 2025.

Who is the general manager of NORDISK STILLAS AS?

David Petersen is registered as general manager of NORDISK STILLAS AS.

Where is NORDISK STILLAS AS based?

NORDISK STILLAS AS has its business address in Moelv.

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.