BIZTRAC BETA
Office administrative and support activities

SAFE-STILLAS AS

Org. no. 916800363 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 400,000
Operating profit NOK −2,000
Equity NOK 121,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

SAFE-STILLAS AS is registered as a limited company in Stavanger, Rogaland with organisation number 916800363. The business is classified under office administrative and support activities (NACE 82.100). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kontor tjenester og forefallende arbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 400,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2025

Revenue
NOK 400,000
Operating profit
NOK −2,000
Equity
NOK 121,000
Est. value
NOK 314,000

Financial health · 2025

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

Who owns SAFE-STILLAS AS?

ONUR ZORLU
SAFE-STILLAS AS
NOK 400,000 rev. · NOK −2,000 profit

SAFE-STILLAS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SAFE-STILLAS AS own?

SAFE-STILLAS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SAFE-STILLAS AS

Who owns SAFE-STILLAS AS?

ONUR ZORLU is the largest registered owner, with 100.0%.

What is the revenue of SAFE-STILLAS AS?

SAFE-STILLAS AS had revenue of NOK 400,000 in 2025.

Who is the general manager of SAFE-STILLAS AS?

Onur Zorlu is registered as general manager of SAFE-STILLAS AS.

Where is SAFE-STILLAS AS based?

SAFE-STILLAS AS has its business address in Stavanger.

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.