BIZTRAC BETA
Other education activities

ASK SAFETY AS

Org. no. 813907682 Limited company (AS) Ålesund Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 40.5m
Operating profit NOK 9.6m
Equity NOK 32.7m
Incorporated 2014
Employees 38
Share capital NOK 500,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ASK SAFETY AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 813907682. The business is classified under other education activities (NACE 85.597). The company was incorporated in 2014 and has 38 registered employees. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Sikkerhets- og kompetanseopplæringsvirksomhet og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 40.5m in revenue and NOK 9.6m in operating profit.

Key figures · 2024

Revenue
NOK 40.5m
Operating profit
NOK 9.6m
Equity
NOK 32.7m
Est. value
NOK 54.2m

Financial health · 2024

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

Who owns ASK SAFETY AS?

NYE ASK SAFETY HOLDING AS
ASK SAFETY AS
NOK 40.5m rev. · NOK 9.6m profit

ASK SAFETY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASK SAFETY AS

Who owns ASK SAFETY AS?

NYE ASK SAFETY HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ASK SAFETY AS?

ASK SAFETY AS had revenue of NOK 40.5m in 2024.

Who is the general manager of ASK SAFETY AS?

Staale Arvid Brungot is registered as general manager of ASK SAFETY AS.

Where is ASK SAFETY AS based?

ASK SAFETY AS has its business address in Ålesund.

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.