BIZTRAC BETA
Other support activities for petroleum and natural gas extraction

SAFETY LEADERS AS

Org. no. 931709666 Limited company (AS) Melhus Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11,000
Equity NOK −1,000
Incorporated 2023
Employees 8
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−11k kr).

SAFETY LEADERS AS is registered as a limited company in Melhus, Trøndelag with organisation number 931709666. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2023 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Andre tjenester tilknyttet utvinning av råolje og naturgass.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK −1,000

Financial health · 2024

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

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

Who owns SAFETY LEADERS AS?

KEVIN WITH STØRSETH
SAFETY LEADERS AS
NOK 0 rev. · NOK −11,000 profit

SAFETY LEADERS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SAFETY LEADERS AS

Who owns SAFETY LEADERS AS?

KEVIN WITH STØRSETH is the largest registered owner, with 100.0%.

What is the revenue of SAFETY LEADERS AS?

SAFETY LEADERS AS had revenue of NOK 0 in 2024.

Where is SAFETY LEADERS AS based?

SAFETY LEADERS AS has its business address in Melhus.

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.